Question 890
In this retired AZ-500 educational case, Microsoft Defender for Cloud reports a low Secure Score, but a team wants to close every recommendation by simply excluding resources. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Secure Score aggregates recommendations and does not certify safety when findings are hidden or exempted. That is why the action is: Prioritize actual risk-reduction remediation and document legitimate exceptions separately. The directly relevant confirmation is: An implemented corrective control improves the corresponding recommendation state with evidence.
Incorrect Answers
“Security governance depends on knowing the resources that exist within the organization's scope” reflects the mechanism: Security governance depends on knowing the resources that exist within the organization's scope. The actual reported symptoms are better explained by: Secure Score aggregates recommendations and does not certify safety when findings are hidden or exempted.
The offered principle describes: Entity mapping enriches findings by linking raw event fields to recognizable investigation entities. The situation in this question instead depends on: Secure Score aggregates recommendations and does not certify safety when findings are hidden or exempted. These are different technical conditions.
This alternative is valid when patch currency does not guarantee absence of credential theft or suspicious runtime behavior. The facts here establish a different controlling reason: Secure Score aggregates recommendations and does not certify safety when findings are hidden or exempted.