Question 900
While validating an Azure workload, the security team finds: A cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved. Which safeguard would best prevent this issue from recurring?
Explanation
Correct Answer
This guardrail addresses defender for cloud secure score priority: Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The prevention measure is: Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. “Version and retest custom standards whenever baseline policy definitions or service configurations change” would address that alternative cause, not the condition in this question: secure score is based on security-control recommendations and affected resources, not just a raw count of findings.
“Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks” responds to this separate finding: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects. This question instead needs “Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts”, so the alternative does not meet the stated condition.
Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Require attribution evidence and review of discovered assets before initiating high-impact external remediation” applies to that separate problem. The observed case is a cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved; choosing this alternative would address the wrong failure mode.