A Compliance node represents an execution resource used to run masking operations. Compliance nodes provide the compute capacity required to execute compliance jobs and other operations that require access to connected data sources.
Each compliance node is associated with a Job Orchestrator and becomes part of that orchestrator’s execution pool.
When an operation requires access to a data source or execution of a masking job, the Job Orchestrator selects an available compliance node and assigns the operation to that node.
Compliance nodes operate as stateless execution resources. Configuration required for an operation is synchronized from DCT to the node at runtime and removed after the operation completes.
Multiple compliance nodes can be registered with a Job Orchestrator to increase execution capacity and support parallel execution of masking jobs and other compliance operations.
You can perform the following operations: