mediummultiple choiceObjective-mapped

A container group in Azure Container Instances must pull a private image from Azure Container Registry without embedding registry credentials in the template. What should you configure?

Question 1mediummultiple choice
Full question →

A container group in Azure Container Instances must pull a private image from Azure Container Registry without embedding registry credentials in the template. What should you configure?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

A managed identity for the container group and the AcrPull role on the registry

A managed identity lets the container group authenticate to ACR without secrets, and AcrPull grants pull permission.

B

Distractor review

An admin user account on the Azure Container Registry

Registry admin credentials are secrets and do not meet the requirement to avoid embedding credentials.

C

Distractor review

A shared access signature in a container environment variable

A SAS token is still a credential and is not the recommended way for ACI to authenticate to ACR.

D

Distractor review

A public network access rule that allows all Azure services

Network access alone does not provide authentication to a private container registry.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related AZ-104 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: A managed identity for the container group and the AcrPull role on the registry — The secure pattern is to assign a managed identity to the container group and grant that identity the AcrPull role on the Azure Container Registry. This lets ACI authenticate without storing passwords, service principal secrets, or tokens in the template. It is the right approach for identity-based image pull access and fits Azure’s secretless design for managed workloads. Why others are wrong: Using registry admin credentials or a SAS still means handling secrets, which the scenario explicitly wants to avoid. A public network access rule only changes connectivity and does not provide authentication or authorization for image pulls. The identity plus AcrPull combination is what enables secure, credential-free access.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.