Does a Dedicated Data Endpoint Fix ACI Deployment from Registry1?
Short answer
B A dedicated data endpoint for Registry1 does not grant ACI access; enable the registry admin user (or use a service principal) so image1 can be pulled.
Question
Key Takeaways
The question tests whether you can separate ACR authentication from ACR network/data-plane features — the trap is assuming a Premium registry data endpoint toggle grants ACI the credentials it needs to pull image1.
When an Azure Container Instance fails to pull image1 from Registry1, the fix is registry authentication, not the ACR 'Use dedicated data endpoint' setting. This page confirms that selecting the dedicated data endpoint does not meet the goal, so the correct answer is No (B).
Common mistake: Choosing Yes, because learners assume the dedicated data endpoint improves or unblocks image pulls. In reality it only changes the registry's data endpoint for network-restricted or private-endpoint scenarios and provides no credentials to Azure Container Instances.
Expert Analysis
Why the Answer Is Correct
"Use dedicated data endpoint" is a Premium-tier Azure Container Registry capability that gives the registry a stable, dedicated data endpoint used with firewall rules, private endpoints, or restricted networks. It does not create or expose any credential that an Azure Container Instance can use to authenticate against Registry1, so the image pull still fails with an unauthorized or image-not-found style error. To deploy a container instance from a private ACR image, ACI must authenticate — typically by enabling the registry admin user and passing username/password, or by using a service principal or managed identity with the AcrPull role. Because the proposed solution leaves the authentication failure untouched, it does not meet the goal, making No (B) the correct choice.Why the Other Options Are Wrong
Answer A (Yes) would only be valid if the dedicated data endpoint addressed the root cause of the deployment error, but the error is about accessibility/authentication of image1 rather than the registry's data-plane endpoint. Changing the data endpoint does not enable the admin user, does not issue credentials, and does not assign an identity to the container instance. ACI also needs the correct registry login server reference when pulling image1, and the dedicated data endpoint setting neither supplies nor corrects that. In short, the option is a networking/endpoint feature being mistaken for an authentication fix.Community Comment Notes
Community consensus matches the analysis: one learner states "You set Admin user to Enable for Registry1." and un4exa summarizes it as "Set Admin user enabled for ACR". Another commenter quoted Bing Copilot noting the image is likely inaccessible because of incorrect credentials or firewall rules — the credentials half of that answer is exactly the missing piece, while firewall handling would require network configuration rather than the dedicated data endpoint switch alone. No commenter argued that the dedicated data endpoint resolves the deployment error, which reinforces answer B.Official Reference
- https://learn.microsoft.com/en-us/azure/container-instances/container-instances-using-azure-container-registry
- 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 AZ-104 container questions, first classify the failure as authentication (unauthorized image pull, admin user, service principal, managed identity) or networking (firewall, private endpoint, dedicated data endpoint), then match the solution to that category. In this 'Does this meet the goal?' series, a feature that belongs to the wrong category is always a No.
Frequently Asked Questions
Why doesn't the dedicated data endpoint fix the ACI image1 deployment error?
It only changes the registry's data-plane endpoint for restricted or private network scenarios. It supplies no credentials, so Azure Container Instances still fails to authenticate and pull image1 from Registry1.
How do you let an Azure Container Instance pull image1 from Registry1?
Enable the Registry1 admin user and pass the username/password to the container instance, or assign a service principal or managed identity the AcrPull role so ACI can authenticate.
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 3 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 3
-
[Removed] 👍 2 Answered BB is correct You set Admin user to Enable for Registry1.
-
cb3f703 👍 1 Answered BBing Copilot: No, selecting “Use dedicated data endpoint” for Registry1 does not directly address the issue of deploying a container instance using image1. The error message you received likely indicates that the image is inaccessible. This can happen due to several reasons, such as incorrect credentials or firewall rules blocking access12. To resolve this issue, you should ensure that: The credentials used to access the Azure Container Registry are correct. The Azure Container Registry allows access from the Azure Container Instances service. You can achieve this by enabling the “Allow trusted services” option or using a managed identity12.
-
un4exa 👍 1 Answered BSet Admin user enabled for ACR
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 →