mediummultiple choiceObjective-mapped

A contractor needs temporary access to upload and download files in only one blob container for 8 hours. You do not want to share the storage account key, and you want to revoke access later without affecting other containers. What should you create?

Question 1mediummultiple choice
Full question →

A contractor needs temporary access to upload and download files in only one blob container for 8 hours. You do not want to share the storage account key, and you want to revoke access later without affecting other containers. What should you create?

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 storage account access key, because it can be limited to one container by policy.

An account key grants broad access to the storage account and cannot be scoped safely to a single container in the way the scenario requires.

B

Best answer

A container-level SAS token backed by a stored access policy, so you can limit and revoke access.

A container-level SAS with a stored access policy is ideal for temporary access to one container. It avoids sharing the account key, limits permissions and lifetime to exactly what is needed, and gives you a revocation point through the stored access policy. That combination is safer than broad key-based access and more operationally flexible than changing account-wide settings.

C

Distractor review

Anonymous public access on the container, because it is the easiest way to time-limit access.

Anonymous public access does not provide controlled temporary access and cannot be limited or revoked as precisely as a SAS with a stored access policy.

D

Distractor review

Azure RBAC on the storage account only, because RBAC automatically expires after a few hours.

RBAC assignments do not automatically expire after a few hours unless managed through separate governance processes. RBAC is useful for authenticated users and apps, but not for a short-lived external access token.

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 container-level SAS token backed by a stored access policy, so you can limit and revoke access. — A SAS token scoped to the container is the safest choice for short-term external access when you do not want to share the storage account key. Adding a stored access policy gives you a central place to revoke or adjust that access later without changing unrelated containers. This approach is widely used for time-limited collaboration because it balances least privilege, flexibility, and easy revocation. Why others are wrong: A storage account key is too broad and exposes far more access than needed. Anonymous public access is insecure and does not meet the requirement for controlled temporary access. RBAC is better for authenticated users, apps, or managed identities, but it is not the best fit for a short-lived external access grant that must be easy to revoke.

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.