Which governance feature provides the rationale behind a specific data checkpoint?

Which governance feature provides the rationale behind a specific data checkpoint?

• A. Data masking
• B. Checkpoint justifications
• C. Performance tuning
• D. Access control lists

Answer: (B)

Checkpoint justifications capture the reason for creating a specific data checkpoint—stating what data is included, what policy or regulatory need it satisfies, and the criteria that triggered the checkpoint. This makes the checkpoint auditable and reproducible, because others can see the exact rationale behind preserving that snapshot. Data masking focuses on protecting sensitive data, performance tuning aims to improve speed, and access control lists govern who can view or modify data; none of these provide the explicit rationale for why a checkpoint exists.

Checkpoint justifications capture the reason for creating a specific data checkpoint—stating what data is included, what policy or regulatory need it satisfies, and the criteria that triggered the checkpoint. This makes the checkpoint auditable and reproducible, because others can see the exact rationale behind preserving that snapshot. Data masking focuses on protecting sensitive data, performance tuning aims to improve speed, and access control lists govern who can view or modify data; none of these provide the explicit rationale for why a checkpoint exists.