Question 400
During an architecture review involving the municipal computing service, the cloud security team observes: Feature tests pass while high-volume malicious traffic overwhelms the application. 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: conduct dynamic negative authentication and abuse tests” is a recurring check for another risk: Static code scanning passes but a live service has an authentication bypass. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: add rate-limit and load-abuse criteria to release testing”.
“Periodically verify, document, and enforce this requirement: expand sanctioned and unsanctioned cloud application visibility” is a recurring check for another risk: CASB monitoring misses sensitive uploads through unsanctioned SaaS. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: add rate-limit and load-abuse criteria to release testing”.
“Periodically verify, document, and enforce this requirement: require version-controlled approved infrastructure promotion” is a recurring check for another risk: Production infrastructure code can be changed without peer review. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: add rate-limit and load-abuse criteria to release testing”.