The answer is to disable shared key access on the storage account. This setting, found under the storage account’s Configuration blade as “Allow storage account key access,” forces all incoming requests to authenticate exclusively via Microsoft Entra ID (formerly Azure AD), effectively blocking any new requests that use the account key while leaving the storage account itself and existing Entra-based access completely untouched. On the AZ-104 exam, this scenario tests your understanding of the difference between disabling shared key authorization and deleting the account keys—a common trap where candidates mistakenly think they must regenerate or remove keys, which could break legacy dependencies. The key insight is that disabling access is a policy toggle, not a destructive action. Memory tip: think of it as a “gate” that closes to key-based traffic while keeping the Entra ID door wide open.
AZ-104 Implement and Manage Storage Practice Question
This AZ-104 practice question tests your understanding of implement and manage storage. 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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.
A legacy application still authenticates to Azure Blob Storage by using the account key. Security now requires preventing any new requests that use shared key authorization, while leaving the storage account itself and Microsoft Entra-based access unchanged. Which setting should the administrator enable?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Disable shared key access on the storage account
Option B is correct because disabling shared key access on the storage account enforces that all incoming requests must use Microsoft Entra ID (formerly Azure AD) authorization instead of the account key. This directly meets the security requirement to block new requests using shared key authorization while leaving the storage account itself and Entra-based access unchanged. The setting is available under the storage account's Configuration blade as 'Allow storage account key access'.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Rotate the storage account keys every 24 hours
Why it's wrong here
Frequent rotation does not stop shared key authorization; it only changes the secrets in use.
✓
Disable shared key access on the storage account
Why this is correct
This blocks requests authenticated with account keys while still allowing identity-based access paths.
Related concept
Read the scenario before looking for a memorised answer.
✗
Require secure transfer for the storage account
Why it's wrong here
HTTPS-only improves transport security, but it does not disable account-key authentication.
✗
Create a private endpoint for the storage account
Why it's wrong here
Private networking changes the path to storage, but it does not stop shared key authentication.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse disabling shared key access with rotating keys or enabling secure transfer, not realizing that only disabling shared key access actually blocks the authorization method itself, while the other options address key freshness or transport encryption, not authorization.
Detailed technical explanation
How to think about this question
When shared key access is disabled, Azure Blob Storage rejects any request that does not include an OAuth 2.0 token from Microsoft Entra ID, even if the request is signed with a valid account key. This is enforced at the storage account level by setting the 'AllowSharedKeyAccess' property to false via the Azure Resource Manager API or Azure Policy. In real-world scenarios, this setting is critical for organizations migrating to passwordless authentication to meet compliance standards like PCI DSS or SOC 2, as it eliminates the risk of leaked account keys being used for unauthorized access.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Implement and Manage Storage — This question tests Implement and Manage Storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Disable shared key access on the storage account — Option B is correct because disabling shared key access on the storage account enforces that all incoming requests must use Microsoft Entra ID (formerly Azure AD) authorization instead of the account key. This directly meets the security requirement to block new requests using shared key authorization while leaving the storage account itself and Entra-based access unchanged. The setting is available under the storage account's Configuration blade as 'Allow storage account key access'.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
This AZ-104 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-104 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.