Organizing Azure Storage Content with Hierarchical Namespaces
Short answer
D You can use cont1, share1, and share2 to organize the content as they are the existing storage entities supporting directory structures.
Question
-
-
-
-
-
-
- 
Key Takeaways
The core concept is that while hierarchical namespaces enable efficient folder structures in blobs, standard containers and file shares also serve as organizational units (containers/folders) themselves.
This question tests the ability to identify which Azure storage entities support directory-like organization. The correct answer is D because cont1, share1, and share2 are all valid containers or file shares used for organizing content.
Common mistake: Candidates often select E, believing that the newly planned container 'cont2' should be included in the list of available resources. However, exam questions typically ask about the current environment's capabilities or exclude future state unless explicitly asked.
Expert Analysis
Why the Answer Is Correct
Option D is correct because it includes the three existing storage entities capable of holding organized content: cont1, share1, and share2. cont1 resides in a storage account with a hierarchical namespace enabled (likely Data Lake Storage Gen2), which allows for native directory structures. share1 and share2 are Azure Files shares, which inherently support a directory structure (folders) accessible via SMB/NFS protocols.
Why the Other Options Are Wrong
Option E is incorrect because it includes cont2. The case study states under "Planned Changes" that ADatum plans to create cont2. In certification exams, unless specified otherwise, you must base your answers on the "Existing Environment" provided in the scenario. Since cont2 does not yet exist, it cannot be selected as an available resource for organizing content currently. Option A and B are incomplete, excluding valid file shares or containers.
Community Comment Notes
Community consensus heavily favors D. Users like Megabyte10 and arunyadav09 highlight that cont1 uses hierarchical namespace for organization, while shares naturally support folders. Some users like swk1_az104 debated including cont2, but the prevailing view is that planned changes should not be counted as existing resources. As certainly noted, the key is distinguishing between what exists now versus what is planned.
Exam Strategy
Always carefully distinguish between the "Existing Environment" section and "Planned Changes" sections in case studies. Resources listed in planned changes do not exist yet and should generally not be selected as part of the current solution or inventory unless the question specifically asks for the post-implementation state.
Frequently Asked Questions
Why is cont2 not included in the answer?
Can file shares organize content?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
Megabyte10 👍 7 Answered Dcont1: The container in storage1 with a hierarchical namespace is specifically designed to organize content efficiently. share1 and share2: Both are file shares in storage2 and are not restricted by the hierarchical namespace feature. They can still be used to organize content effectively. Using all three (cont1, share1, and share2) allows for a comprehensive organization strategy across different storage types, adhering to the planned changes and technical requirements.
-
arunyadav09 👍 4 Answered Dfile shares are good to organizing content, Cont1 is with a hierarchical namespace used for organizing content.
-
swk1_az104 👍 2 Answered EIn my mind this is correct, but what MS thinks, you'll never know...so please @all give feedbacks, discuss...on this: Given the ability to use directories in Storage1 and simulate directories in Storage2, the containers and file shares that can be used to organize the content are: E. cont1, cont2, share1, and share2 Explanation cont1: Supports hierarchical namespaces, allowing directory organization. cont2: Although it does not support hierarchical namespaces, you can use prefixes in blob names to simulate a directory structure. share1: Supports directories and subdirectories for organizing content. share2: Supports directories and subdirectories for organizing content. This option includes all the containers and file shares that can be used to organize the content based on the existing environment and the planned changes, while adhering to the technical requirements and the principle of least privilege.
-
certainly 👍 2I go with D. Here’s why: • cont1 is in a storage account with a hierarchical namespace, which is suitable for organizing content. • share1 and share2 are file shares, and organizing content within file shares is not restricted by the hierarchical namespace feature, so both can be used for organization.
-
esyan 👍 1is there any reason doesn't mention about cont2? i think cont2 is possible too, because planned changes. "Planned Changes - ADatum plans to implement the following changes: • Configure a data collection rule (DCR) named DCR1 to collect only system events that have an event ID of 4648 from VM2 and VM4. "• In storage1, create a new container named cont2 that has the following access policies: o Three stored access policies named Stored1, Stored2, and Stored3 o A legal hold for immutable blob storage"
Show 1 more comment
-
lubas 👍 1 Answered DCont1, Share1 e Share2
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →