Question 630
A Microsoft Azure administrator receives this requirement: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. What observation is the strongest validation evidence?
Explanation
Correct Answer
This validates the specific control for acr administrator account disablement: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The associated corrective action is: Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles. Testing a different component would not establish this result.
Incorrect Answers
The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” would address that alternative cause, not the condition in this question: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.
“Enable appropriate APIM subscription requirements and validate product/API associations” responds to this separate finding: the API or product does not require the intended APIM subscription key or equivalent authentication control. This question instead needs “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles”, so the alternative does not meet the stated condition.
Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” applies to that separate problem. The observed case is a shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; choosing this alternative would address the wrong failure mode.