- A
The SAS was generated at the storage account level, granting write access that applies to multiple containers rather than being scoped to the 'images' container only
An account SAS with sr=c (container) permission and no container restriction grants access to all containers. A container SAS is generated with a specific container name in the signed resource URI (e.g., https://account.blob.core.windows.net/images?sig=...), making it impossible for the holder to use the SAS against any other container.
- B
The SAS expiry time is too long, giving partners time to discover and access other containers
Why wrong: SAS expiry controls the time window during which the SAS is valid but does not affect which containers the SAS can access. Even an expired SAS has a defined resource scope — changing the expiry does not change the scope.
- C
The partner used a storage account key instead of the provided SAS token
Why wrong: An account key grants unrestricted access to the entire storage account, which would be a far more severe security incident. The scenario describes a partner using a SAS — the SAS is the control that needs to be scoped correctly.
- D
The SAS was signed with a stored access policy that did not name the correct container
Why wrong: Stored access policies are attached to a specific container. If a SAS references a stored access policy, it inherits the policy's permissions — but the SAS's signed resource URI still determines which container it grants access to, not the policy name.
AZ-204 Practice Question: SAS token scope misconfiguration allowing upload…
This AZ-204 practice question tests your understanding of implement azure security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: shared Access Signature. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
External partners are given Shared Access Signatures to upload product images to a specific Blob Storage container named 'images'. A partner reports accidentally uploading files to the 'contracts' container, which should not be accessible. What is the most likely configuration mistake?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The SAS was generated at the storage account level, granting write access that applies to multiple containers rather than being scoped to the 'images' container only
A SAS generated at the storage account level grants permissions across all containers within that account. When the SAS URI includes only the account endpoint (e.g., https://<account>.blob.core.windows.net/) and a set of permissions (like write), the token can be used to access any container, including 'contracts'. To restrict access to a single container, the SAS must be scoped to the container resource URI (e.g., https://<account>.blob.core.windows.net/images) and the signed resource type must be 'c' (container) or 'b' (blob), not 's' (service).
Key principle: Shared Access Signature
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The SAS was generated at the storage account level, granting write access that applies to multiple containers rather than being scoped to the 'images' container only
Why this is correct
An account SAS with sr=c (container) permission and no container restriction grants access to all containers. A container SAS is generated with a specific container name in the signed resource URI (e.g., https://account.blob.core.windows.net/images?sig=...), making it impossible for the holder to use the SAS against any other container.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Shared Access Signature
- ✗
The SAS expiry time is too long, giving partners time to discover and access other containers
Why it's wrong here
SAS expiry controls the time window during which the SAS is valid but does not affect which containers the SAS can access. Even an expired SAS has a defined resource scope — changing the expiry does not change the scope.
- ✗
The partner used a storage account key instead of the provided SAS token
Why it's wrong here
An account key grants unrestricted access to the entire storage account, which would be a far more severe security incident. The scenario describes a partner using a SAS — the SAS is the control that needs to be scoped correctly.
- ✗
The SAS was signed with a stored access policy that did not name the correct container
Why it's wrong here
Stored access policies are attached to a specific container. If a SAS references a stored access policy, it inherits the policy's permissions — but the SAS's signed resource URI still determines which container it grants access to, not the policy name.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the scope of a SAS (account-level vs. resource-level) with other SAS properties like expiry time or stored access policies, leading them to incorrectly attribute the security breach to token lifetime or policy misconfiguration rather than the fundamental lack of resource-level scoping.
Trap categories for this question
Scenario analysis trap
An account key grants unrestricted access to the entire storage account, which would be a far more severe security incident. The scenario describes a partner using a SAS — the SAS is the control that needs to be scoped correctly.
Detailed technical explanation
How to think about this question
When generating a SAS at the storage account level, the signed resource (sr) parameter is set to 's' (service), meaning the token applies to the entire Blob service endpoint. To scope to a container, the signed resource must be 'c' (container) and the URI must include the container name. Additionally, the signed permissions (sp) parameter must be set to 'w' for write, but without container-level scoping, the token can write to any container. In practice, using a container-level SAS with a stored access policy allows centralized management of permissions and revocation without regenerating tokens.
KKey Concepts to Remember
- Shared Access Signature
- SAS scope
- container-level SAS
- storage account SAS
- least privilege
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Shared Access Signature
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review shared Access Signature, then practise related AZ-204 questions on the same topic to reinforce the concept.
- →
Implement Azure security — study guide chapter
Learn the concepts, then practise the questions
- →
Implement Azure security practice questions
Targeted practice on this topic area only
- →
All AZ-204 questions
997 questions across all exam domains
- →
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
- →
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-204 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Develop Azure compute solutions practice questions
Practise AZ-204 questions linked to Develop Azure compute solutions.
Develop for Azure storage practice questions
Practise AZ-204 questions linked to Develop for Azure storage.
Implement Azure security practice questions
Practise AZ-204 questions linked to Implement Azure security.
Connect to and consume Azure services and third-party services practice questions
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Monitor, troubleshoot, and optimize Azure solutions practice questions
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
AZ-204 fundamentals practice questions
Practise AZ-204 questions linked to AZ-204 fundamentals.
AZ-204 scenario practice questions
Practise AZ-204 questions linked to AZ-204 scenario.
AZ-204 troubleshooting practice questions
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Start a free AZ-204 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-204 question test?
Implement Azure security — This question tests Implement Azure security — Shared Access Signature.
What is the correct answer to this question?
The correct answer is: The SAS was generated at the storage account level, granting write access that applies to multiple containers rather than being scoped to the 'images' container only — A SAS generated at the storage account level grants permissions across all containers within that account. When the SAS URI includes only the account endpoint (e.g., https://<account>.blob.core.windows.net/) and a set of permissions (like write), the token can be used to access any container, including 'contracts'. To restrict access to a single container, the SAS must be scoped to the container resource URI (e.g., https://<account>.blob.core.windows.net/images) and the signed resource type must be 'c' (container) or 'b' (blob), not 's' (service).
What should I do if I get this AZ-204 question wrong?
Review shared Access Signature, then practise related AZ-204 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Shared Access Signature
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More AZ-204 practice questions
- An app must store relational state and perform transactions across multiple tables with T-SQL support. Which Azure data…
- You are monitoring an Azure App Service using Application Insights. You notice that the server response time is high for…
- Which TWO services can be used to implement a publish-subscribe messaging pattern in Azure?
- You need to monitor the CPU utilization of an Azure VM in real-time and set up an alert when it exceeds 90%. Which Azure…
- You are monitoring an Azure web application with Application Insights. You notice a sudden increase in the number of fai…
- You are monitoring an Azure web app using Application Insights. You need to create a query that returns the average dura…
Last reviewed: Jun 11, 2026
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.