Question 740
During an approved configuration change involving the retail payment infrastructure, the cloud security team observes: A DR provider guarantees zero data loss without verifying replication limits. The decision must preserve authorized security and availability requirements. Which repeatable governance control BEST prevents a recurrence?
Explanation
Correct Answer
Repeatable verification of the specific remediation prevents the same control gap from silently reappearing after deployments or changes.
Incorrect Answers
“Periodically verify, document, and enforce this requirement: increase backup or replication cadence to satisfy measured RPO” is a recurring check for another risk: Backups run daily despite a recovery point objective of one hour. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate achievable recovery objectives against the replication architecture”.
“Periodically verify, document, and enforce this requirement: restrict tenant management ingress with authenticated network access” is a recurring check for another risk: Cloud VM managers expose customer administration ports through public network rules. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate achievable recovery objectives against the replication architecture”.
“Periodically verify, document, and enforce this requirement: move sensitive key operations into an authorized protected HSM service” is a recurring check for another risk: A workload uses ordinary VM memory for high-assurance cryptographic keys. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate achievable recovery objectives against the replication architecture”.