hardmultiple choiceObjective-mapped

A scale set of application VMs uploads JSON files to one blob container. The identity must not use secrets, must keep working if an instance is reimaged or replaced, and the same identity should be reusable across all instances. What should the administrator configure?

Question 1hardmultiple choice
Full question →

A scale set of application VMs uploads JSON files to one blob container. The identity must not use secrets, must keep working if an instance is reimaged or replaced, and the same identity should be reusable across all instances. What should the administrator 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

Distractor review

A system-assigned managed identity on each VM instance, with account-wide storage permissions.

System-assigned identities are tied to each resource lifecycle and do not provide one reusable identity that survives instance replacement.

B

Best answer

A user-assigned managed identity, attached to the scale set, with Storage Blob Data Contributor scoped to the container.

A user-assigned managed identity persists independently of any single VM instance, so it remains usable after reimaging or replacement. Scoping Storage Blob Data Contributor to the container follows least privilege while still allowing the workload to upload the JSON files.

C

Distractor review

A shared access signature stored in the VM image and renewed annually.

A SAS token is still a secret, and storing it in the image violates the requirement to avoid secrets and to keep access resilient through replacements.

D

Distractor review

The storage account access key, because it allows the most reliable upload path.

Access keys are long-lived secrets, provide broader access than needed, and are not appropriate when the requirement explicitly forbids secrets.

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 user-assigned managed identity, attached to the scale set, with Storage Blob Data Contributor scoped to the container. — A user-assigned managed identity is the best fit when multiple VMs or scale set instances need the same identity and the identity must survive instance replacement. Because it is independent of any single VM, it continues to work when an instance is reimaged or recreated. Assigning Storage Blob Data Contributor at the container scope keeps the permission narrow and aligned with least privilege, while avoiding secrets entirely. Why others are wrong: System-assigned identities are lifecycle-bound to the individual resource, so they do not satisfy the requirement for one reusable identity across instances. SAS tokens and access keys are both secrets and are explicitly disallowed. The question is testing persistence and scoping together, so the correct answer must address both identity durability and least privilege.

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.