Does Assigning AcrPull to ACR-Tasks-Network Meet the Goal?
Short answer
B Assigning AcrPull to ACR-Tasks-Network does not meet the goal; the role must be granted to the identity that pulls image1 from Registry1.
Question
Key Takeaways
This question tests whether you can identify the correct principal for the AcrPull role in an ACR-to-container-instance deployment; the trap is assuming any AcrPull assignment fixes the image pull error.
Deploying an Azure container instance from Registry1 requires AcrPull on the identity that pulls image1. Assigning AcrPull to ACR-Tasks-Network instead does not meet the goal, so the correct answer is B.
Common mistake: Choosing Yes because AcrPull is the required role, without checking that it must be assigned to the deployment identity rather than to ACR-Tasks-Network.
Expert Analysis
Why the Answer Is Correct
Assigning AcrPull to ACR-Tasks-Network does not grant the container deployment identity permission to pull image1 from Registry1. Azure Container Registry authorizes image pulls based on the identity presenting the request, such as a managed identity, service principal, or user. Because ACR-Tasks-Network is not the principal deploying the container instance, the original authorization error would persist. As efla noted, "This role should be assigned to the identity that is performing the container deployment." Therefore option B, No, is correct.Why the Other Options Are Wrong
Option A, Yes, is wrong because it assumes the role assignment to ACR-Tasks-Network resolves the pull failure. The question specifically says the error occurs when deploying a container instance, so the identity used by that deployment must have AcrPull on Registry1. Pcservices pointed out that ACR-Tasks-Network "might not be the correct identity involved in deploying the container instance." Without granting AcrPull to the actual deployment principal, the image pull remains unauthorized.Community Comment Notes
Community responses unanimously select B, with comments emphasizing that AcrPull belongs to the deployment identity. efla and rklai both state that the role "should be assigned to the identity that is performing the container deployment." Another commenter adds that the role is assigned to a principal that may not be involved in the container instance deployment. This consensus aligns with Azure RBAC scoping and the requirement that the image-pulling identity be authorized on the registry.Official Reference
- https://learn.microsoft.com/en-us/azure/container-registry/container-registry-roles
- https://learn.microsoft.com/en-us/azure/container-registry/container-registry-authentication
These links open the official vendor documentation in a new tab.
Exam Strategy
For ACR image-pull errors, identify who is pulling the image before evaluating a role assignment. The presence of the correct role name, AcrPull, is not enough; the role must be assigned to the principal that the container deployment uses.
Frequently Asked Questions
Why doesn't assigning AcrPull to ACR-Tasks-Network meet the goal?
ACR-Tasks-Network is not the identity deploying the container instance; AcrPull must be granted to the principal that actually pulls image1 from Registry1.
Which identity needs AcrPull to deploy a container instance from Registry1?
The identity used by the container instance or deployment process, such as its managed identity or service principal, must have AcrPull on Registry1.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors, not of islever. The comments shown first are the most substantive of the thread — ranked by depth, community endorsement and relevance; expand the list below to read the rest.
From public community threads 4
-
efla 👍 8 Answered BAns: No AcrPull role assigned to ACR-Tasks-Network does not meet the goal. This role should be assigned to the identity that is performing the container deployment.
-
rklai 👍 3AcrPull role assigned to ACR-Tasks-Network does not meet the goal. This role should be assigned to the identity that is performing the container deployment.
-
Pcservices 👍 2 Answered BAnswer: B. No Explanation: Assigning the AcrPull role to a service principal or identity is a necessary step to allow pulling container images from an Azure Container Registry (ACR). However, in the scenario described, the role is assigned to ACR-Tasks-Network, which might not be the correct identity involved in deploying the container instance. To deploy a container instance using an image from ACR, the identity or resource attempting the deployment (such as an Azure Container Instance or a user) needs the AcrPull role on the registry (in this case, Registry1). If the correct identity doesn't have this role, you would still encounter a permission issue.
-
[Removed] 👍 1 Answered Bit´s B You assign the AcrPull role to the identity
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →