Question 810
At the Redhaven analytics division, after a recently completed production incident, security operations cannot correlate build repository vulnerabilities with the cloud resources that consume them. What is the primary reason this approach is unreliable?
Explanation
Correct Answer
This explanation matches the reported facts: separated development and runtime risk views obscure which vulnerable code affects production services. A corrective test should establish that a critical repository finding is visible with useful ownership and cloud-risk context. This directly addresses the reported issue at the Redhaven analytics division.
Incorrect Answers
That statement concerns codeql pipeline gate; here the reported facts point to a different issue: separated development and runtime risk views obscure which vulnerable code affects production services. For the Redhaven analytics division, the priority is to connect eligible DevOps repositories to Microsoft Defender for Cloud DevOps Security capabilities.
Excessive access levels expose source, configuration and administrative actions beyond the review task. This can occur in other projects, but it is not the primary explanation at the Redhaven analytics division.
Although overly broad job tokens expand the impact of untrusted actions or script defects, the situation does not describe that specific cause; it instead indicates that separated development and runtime risk views obscure which vulnerable code affects production services. For the Redhaven analytics division, the priority is to connect eligible DevOps repositories to Microsoft Defender for Cloud DevOps Security capabilities.