Question 390
The cloud operations team reviews the following risk: A GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments. Which configuration change most directly resolves this problem?
Explanation
Correct Answer
The cause is: DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The appropriate change is: Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories. Verify it with this outcome: The previously omitted repositories appear in DevOps Security findings and receive appropriate code scanning coverage.
Incorrect Answers
This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The reported incident instead involves DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
This action concerns defender for resource manager suspicious activity, where Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The corrective response here is “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories”; this alternative does not provide that response.
This action concerns defender for containers container registry vulnerabilities, where Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The stem reports a GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments; this control addresses a different failure condition.