mediummultiple choiceObjective-mapped

A web app running in Azure App Service must read blobs from a storage account. The app must authenticate without storing secrets or SAS tokens, and administrators should grant only blob data permissions, not storage management permissions. What should you configure?

Question 1mediummultiple choice
Full question →

A web app running in Azure App Service must read blobs from a storage account. The app must authenticate without storing secrets or SAS tokens, and administrators should grant only blob data permissions, not storage management permissions. 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

The storage account access key in an application setting, because it works with any blob operation.

An access key is a secret and grants broad control over the storage account, which violates the requirement to avoid stored credentials and limit permissions.

B

Best answer

A system-assigned managed identity for the app with Storage Blob Data Reader assigned at the storage scope.

A managed identity lets the app authenticate to Azure Storage without storing credentials, and the Storage Blob Data Reader role grants only blob data read access. Assigning the role at the storage account scope keeps the permission focused on the intended resource while avoiding management-plane rights. This is the most secure operational pattern for an Azure-hosted app that only needs to read blobs.

C

Distractor review

The Contributor role on the storage account, because it includes both management and data permissions.

Contributor is a management-plane role and does not provide the specific blob data authorization pattern required here. It is also broader than needed.

D

Distractor review

A service endpoint on the subnet, because service endpoints are used for application authentication.

Service endpoints affect network reachability, not identity-based authentication. They do not replace the need for a managed identity or other credential mechanism.

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 system-assigned managed identity for the app with Storage Blob Data Reader assigned at the storage scope. — For an Azure-hosted application, a system-assigned managed identity is the cleanest way to authenticate to Storage without secrets. By assigning Storage Blob Data Reader, you grant only the data-plane permission needed to read blobs. This avoids account keys and SAS tokens, keeps credentials out of configuration, and follows least privilege. It is also easy to manage because the identity is tied to the app resource itself. Why others are wrong: A storage account key is a secret and is much broader than needed. Contributor is a management role and does not provide the right least-privilege data access model. Service endpoints only influence network pathing; they do not authenticate the application to Storage. The scenario explicitly asks for secretless authentication with only blob data permissions.

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.