mediummultiple choiceObjective-mapped

A VM-based app must upload invoices to a blob container every hour. Security prohibits storing account keys or SAS tokens on the VM. The app should authenticate with Microsoft Entra ID and be allowed only to write blobs in one container. What should you configure?

Question 1mediummultiple choice
Full question →

A VM-based app must upload invoices to a blob container every hour. Security prohibits storing account keys or SAS tokens on the VM. The app should authenticate with Microsoft Entra ID and be allowed only to write blobs in one container. 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

Distractor review

Create an account SAS token and store it in the VM's application settings.

An account SAS relies on a shared secret and violates the requirement to avoid storing keys or long-lived tokens on the VM.

B

Best answer

Enable a managed identity on the VM and assign Storage Blob Data Contributor at the container scope.

A managed identity lets the VM authenticate to Azure Storage through Microsoft Entra ID without storing credentials on the server. Assigning Storage Blob Data Contributor at the container scope gives the app the ability to upload and modify blob data only where needed. This is the least-privilege approach and aligns with secure operational practice for Azure administrators.

C

Distractor review

Assign Reader on the storage account so the VM can reach the container securely.

Reader is a management-plane role and does not grant permission to upload blob data. It cannot satisfy the write requirement.

D

Distractor review

Grant Storage Account Contributor at the subscription scope so the app can manage all storage resources.

Storage Account Contributor is far broader than needed and grants management-plane control, not just blob data access. It also violates least privilege.

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: Enable a managed identity on the VM and assign Storage Blob Data Contributor at the container scope. — A managed identity is the right choice because it eliminates stored secrets on the VM while still allowing the application to authenticate with Microsoft Entra ID. The Storage Blob Data Contributor role is a data-plane role, so it authorizes blob upload operations without granting unnecessary management rights. Scoping the role to the container keeps access tightly limited to the specific data set the app needs. Why others are wrong: An account SAS would require distributing a secret and is specifically what the requirement forbids. Reader is only for viewing Azure resource metadata and cannot write blobs. Storage Account Contributor is excessive because it grants control over storage resources rather than just the container's blob data, which breaks least-privilege design.

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.