mediummultiple choiceObjective-mapped

Exhibit

Template excerpt:
```
resources:
- type: Microsoft.ContainerInstance/containerGroups
  name: cg-transform
  properties:
    containers:
    - name: transform
      properties:
        image: contoso.azurecr.io/transform:3.0
    imageRegistryCredentials: []
```
Requirement: the image is stored in Azure Container Registry and no username, password, or connection string may be embedded in the deployment

Based on the exhibit, what should the administrator configure so the container group can pull the private image without storing registry credentials?

Question 1mediummultiple choice
Full question →

Based on the exhibit, what should the administrator configure so the container group can pull the private image without storing registry credentials?

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

Assign a managed identity to the container group and grant it AcrPull on the registry.

Managed identity-based access is the correct secret-free method for Azure Container Instances to authenticate to Azure Container Registry. By assigning an identity to the container group and granting that identity the AcrPull role on the registry, the group can pull the private image without storing credentials in the template. This satisfies both security and operational requirements.

B

Distractor review

Store the ACR admin account password in a container environment variable.

Embedding a password in configuration violates the requirement to avoid stored credentials.

C

Distractor review

Use a SAS token for the container image reference.

SAS tokens are not the normal authentication method for pulling private container images from ACR.

D

Distractor review

Place the registry in the same resource group as the container group.

Resource group placement does not authorize access to a private 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: Assign a managed identity to the container group and grant it AcrPull on the registry. — The container group should use a managed identity and receive the AcrPull role on the Azure Container Registry. That is the Azure-native way to let ACI pull private images without hardcoding usernames, passwords, or tokens into the deployment. The exhibit specifically says the image is private and credentials must not be embedded, so identity-based authorization is the correct design. This also simplifies rotation and reduces secret management overhead. Why others are wrong: Environment variables and passwords still create a secret management problem. SAS tokens are not the standard registry-authentication mechanism for ACR image pulls. Resource group placement has no effect on authorization to a private registry.

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.