Question 380
A Microsoft Azure administrator receives this requirement: A team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM. What observation is the strongest validation evidence?
Explanation
Correct Answer
This validates the specific control for vulnerability risk prioritization by exposure: Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. The associated corrective action is: Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw. Testing a different component would not establish this result.
Incorrect Answers
A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” would address that alternative cause, not the condition in this question: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue.
“Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” responds to this separate finding: defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. This question instead needs “Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw”, so the alternative does not meet the stated condition.
Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. “Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access” applies to that separate problem. The observed case is a team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM; choosing this alternative would address the wrong failure mode.