hardmultiple choiceObjective-mapped

A container group must run an image from a private Azure Container Registry without embedding registry credentials in the deployment. The same authentication method should be reusable by future container groups, and the application must continue to work if the container group is recreated. Which identity approach should the administrator use?

Question 1hardmultiple choice
Full question →

A container group must run an image from a private Azure Container Registry without embedding registry credentials in the deployment. The same authentication method should be reusable by future container groups, and the application must continue to work if the container group is recreated. Which identity approach should the administrator use?

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

Distractor review

A system-assigned managed identity for the container group.

A system-assigned identity works for one container group, but it is bound to that specific resource lifecycle. It is not the best choice when the same identity must be reused by future deployments.

B

Best answer

A user-assigned managed identity assigned to the container group.

A user-assigned managed identity can be reused across container groups and survives recreation of the workload resource. After granting the identity AcrPull on the registry, the container group can authenticate without stored usernames, passwords, or registry secrets.

C

Distractor review

An ACR admin username and password stored in the container image.

Embedding registry credentials in the image is insecure and difficult to rotate. It also violates the requirement to avoid credentials and does not provide reusable Azure identity-based access.

D

Distractor review

A shared access signature token passed as an environment variable.

A SAS token is still a secret and is time-bound, which creates management overhead. It is not the preferred identity-based pattern for pulling images from ACR.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: A user-assigned managed identity assigned to the container group. — A user-assigned managed identity is the best fit when the same authentication identity must be reused across multiple container group deployments. It avoids registry passwords entirely and can be granted the AcrPull role on Azure Container Registry. Because the identity is independent of the specific container group lifecycle, it remains usable if the workload is deleted and recreated. Why others are wrong: A system-assigned identity is tied to one resource instance, so it does not meet the reuse requirement as well as a user-assigned identity. Storing credentials in the image is insecure and hard to rotate. A SAS token is still a secret and adds expiration and distribution overhead, which is not the desired design for identity-based registry 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.