Case Study 5 - Contoso, Ltd Overview General Overview Contoso, Ltd. is a consulting company that has a main office in Montreal and branch offices in Seattle and New York. Environment Existing…

To meet the requirements of supporting both blob containers with Cool access tier and Azure file shares, the StorageV2 (general purpose v2) account kind is the correct choice, and 'Storage2' is indicated as the selected destination based on the provided image, likely due to…

Submitted by joshua94· Mar 4, 2026Manage identities and governance

Question

Case Study 5 - Contoso, Ltd Overview General Overview Contoso, Ltd. is a consulting company that has a main office in Montreal and branch offices in Seattle and New York. Environment Existing Environment Contoso has an Azure subscription named Sub1 that is linked to an Azure Active Directory (Azure AD) tenant. The network contains an on-premises Active Directory domain that syncs to the Azure AD tenant. The Azure AD tenant contains the users shown in the following table. Sub1 contains two resource groups named RG1 and RG2 and the virtual networks shown in the following table. User1 manages the resources in RG1. User4 manages the resources in RG2. Sub1 contains virtual machines that run Windows Server 2019 as shown in the following table No network security groups (NSGs) are associated to the network interfaces or the subnets. Sub1 contains the storage accounts shown in the following table. Requirements Planned Changes Contoso plans to implement the following changes: Create a blob container named container1 and a file share named share1 that will use the Cool storage tier. Create a storage account named storage5 and configure storage replication for the Blob service. Create an NSG named NSG1 that will have the custom inbound security rules shown in the following table. Associate NSG1 to the network interface of VM1. Create an NSG named NSG2 that will have the custom outbound security rules shown in the following table. Associate NSG2 to VNET1/Subnet2. Technical Requirements Contoso must meet the following technical requirements: Create container1 and share1. Use the principle of least privilege. Create an Azure AD security group named Group4. Back up the Azure file shares and virtual machines by using Azure Backup. Trigger an alert if VM1 or VM2 has less than 20 GB of free space on volume C. Enable User1 to create Azure policy definitions and User2 to assign Azure policies to RG1. Create an internal Basic Azure Load Balancer named LB1 and connect the load balancer to VNET1/Subnet1 Enable flow logging for IP traffic from VM5 and retain the flow logs for a period of eight months. Whenever possible, grant Group4 Azure role-based access control (Azure RBAC) read-only permissions to the Azure file shares. Hotspot Question You need to create storage5. The solution must support the planned changes. Which type of storage account should you use, and which account should you configure as the destination storage account? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

Account kind:
BlobStorageBlockBlobStorageStorage (general purpose v1)StorageV2 (general purpose v2)
Destination:
Storage1Storage2Storage3Storage4

Explanation

Approach. Based on the case study's 'Planned Changes' requirements:

Account kind: StorageV2 (general purpose v2)
- The requirement states to 'Create a blob container named container1 and a file share named share1 that will use the Cool storage tier.'
- General-purpose v2 (GPv2) storage accounts are the most comprehensive and recommended type for most scenarios. They support all Azure Storage services (blobs, files, queues, tables).
- Crucially, GPv2 accounts support blob access tiers (Hot, Cool, Archive), which is necessary to use the 'Cool storage tier' for the blob container.
- GPv2 also fully supports Azure Files, meeting the 'create a file share' requirement.
- Furthermore, GPv2 accounts support all replication options for the Blob service, aligning with the requirement to 'configure storage replication for the Blob service' for storage5.
Destination: Storage2
- Without further context from the case study (specifically, the table describing existing storage accounts Storage1-Storage4 or explicit instructions for a migration/configuration task for an existing account), the logical reason for selecting 'Storage2' cannot be definitively determined from the provided text alone.
- However, since the image highlights 'Storage2' as the selected answer, it implies that within the full exam context (e.g., a preceding question, a detailed existing environment table, or a specific task asking to operate on 'Storage2'), this would be the correct choice. For instance, 'Storage2' might be the designated existing storage account for an upgrade to GPv2, or the target for migrating data, or the only existing account configured to fulfill some specific criteria (e.g., located in a specific region, empty, or currently GPv1 needing an upgrade). Given the constraint to explain the correct approach based on the image's selection, we assume 'Storage2' is the correct target as pre-selected.

Common mistakes.

common_mistake. 1. Incorrect Account Kind selections:
- BlobStorage / BlockBlobStorage: These are incorrect because they are specialized for blobs and do not support Azure file shares, which is a key requirement.
- Storage (general purpose v1): While GPv1 accounts support both blobs and file shares, they do not support blob access tiers (Hot, Cool, Archive). The requirement explicitly states using the 'Cool storage tier', making GPv1 an unsuitable choice. GPv1 is also generally less cost-effective and feature-rich than GPv2.

Incorrect Destination selections (Storage1, Storage3, Storage4):
- Without additional context from the full case study, any of 'Storage1', 'Storage3', or 'Storage4' would be equally plausible or implausible as 'Storage2'. A common mistake would be to arbitrarily pick one of these without a clear directive, whereas the highlighted answer (Storage2) in the provided solution implies a specific, unstated reason within the broader case study context.

Concept tested. The core technical concept being tested is the understanding of different Azure Storage Account kinds (General-purpose v1, General-purpose v2, BlobStorage, BlockBlobStorage), their respective capabilities, supported services (blobs, files, queues, tables), and features like blob access tiers (Hot, Cool, Archive) and replication options. It assesses the ability to select the appropriate storage account type based on specific functional and cost optimization requirements.

Topics

#Azure AD Hybrid Identity#Azure RBAC#Network Security Groups#Azure Blob Storage

Community Discussion

No community discussion yet for this question.

Full AZ-104 Practice