Question 640
While validating an Azure workload, the security team finds: A build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities. Which remediation best addresses the specific issue?
Explanation
Correct Answer
The cause is: Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The appropriate change is: Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings. Verify it with this outcome: Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.
Incorrect Answers
This action concerns defender for cloud devops iac misconfiguration, where Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The reported incident instead involves Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.
This action concerns defender for cloud alert investigation evidence, where A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The corrective response here is “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings”; this alternative does not provide that response.
This action concerns microsoft defender for servers plan 2 eligibility, where Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The stem reports a build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities; this control addresses a different failure condition.