hardmultiple choiceObjective-mapped

A Windows VM runs an application that uploads files to a blob container every hour. Security forbids storing storage account keys or long-lived SAS tokens on the VM. The application must be able to write only to that container and nothing else. What should the administrator configure?

Question 1hardmultiple choice
Full question →

A Windows VM runs an application that uploads files to a blob container every hour. Security forbids storing storage account keys or long-lived SAS tokens on the VM. The application must be able to write only to that container and nothing else. 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

Store the storage account key in an environment variable on the VM

This still exposes a long-lived secret on the VM and gives access far broader than the single container.

B

Distractor review

Create a service SAS with write permission on the storage account

A SAS is still a shared secret, and using the account scope is broader than the single container requirement.

C

Best answer

Assign Storage Blob Data Contributor to the VM's managed identity at the container scope

A managed identity avoids stored credentials, and the Storage Blob Data Contributor role grants blob read/write permissions without exposing account keys. Assigning it at the container scope keeps access limited to one container instead of the whole storage account. This is the least-privilege, Azure-native approach for an app that needs ongoing upload access.

D

Distractor review

Assign Contributor on the storage account to the VM's system-assigned identity

Contributor is an Azure Resource Manager role, not a data-plane blob access role, so it does not grant the needed container upload permissions.

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 Storage Blob Data Contributor to the VM's managed identity at the container scope — The best solution is to use the VM's managed identity with a data-plane RBAC role scoped to the specific container. That removes the need for keys or SAS tokens and enforces least privilege. Storage Blob Data Contributor allows the application to upload and overwrite blobs in that container without granting access to other containers or management-plane actions on the account. This is the most secure and operationally durable option for recurring uploads. Why others are wrong: An environment variable or SAS token still places a long-lived credential on the VM, which violates the security requirement. Assigning Contributor at the storage account scope is wrong because it is an ARM role and does not grant blob data access. It would also be broader than necessary. The correct pattern is identity-based access at the narrowest possible scope.

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.