nerdexam
Microsoft

AZ-104 · Question #456

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 create a Cool tier blob container, General-purpose v2 (GPv2) storage accounts are required, while for a 'Cool' (standard) file share, a GPv2 account is typically best.

Submitted by renata2k· Mar 4, 2026Implement and manage storage

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 container1 and share1. Which storage accounts should you use for each resource? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibit

AZ-104 question #456 exhibit

Answer Area

  • container1:
    storage2 onlystorage2 and storage3 onlystorage1, storage2, and storage3 onlystorage2, storage3, and storage4 onlystorage1, storage2, storage3, and storage4
  • share1:
    storage2 onlystorage4 onlystorage2 and storage4 onlystorage1, storage2, and storage4 onlystorage1, storage2, storage3, and storage4

Explanation

To create a Cool tier blob container, General-purpose v2 (GPv2) storage accounts are required, while for a 'Cool' (standard) file share, a GPv2 account is typically best.

Approach. To answer correctly, we must consider the requirements for creating a 'blob container named container1' and a 'file share named share1' that 'will use the Cool storage tier'.

  1. For 'container1' (blob container with Cool tier):

    • Azure Blob storage supports Hot, Cool, and Archive access tiers. To use the Cool tier for a blob container, the underlying storage account must be a General-purpose v2 (GPv2) account. Older General-purpose v1 (GPv1) accounts only support the Hot tier for blobs, and specialized BlockBlobStorage accounts are also typically optimized for Hot tier block blobs.
    • Therefore, the selection 'storage2 and storage3 only' implies that storage2 and storage3 are the GPv2 accounts in the existing environment that can host Cool tier blobs. This means storage1 and storage4 are either GPv1, BlockBlobStorage, or FileStorage accounts, which do not support Cool tier for blobs.

  2. For 'share1' (file share with Cool tier):

    • Azure Files itself doesn't have direct Hot/Cool/Archive tiers in the same way blobs do. The 'Cool storage tier' requirement for a file share typically implies a standard, cost-effective file share. Standard file shares are best hosted on General-purpose v2 (GPv2) accounts (or GPv1 accounts, though GPv2 is generally recommended for new deployments). Premium file shares require FileStorage accounts, which would not align with a 'Cool' (cost-effective) tier requirement.
    • From the container1 deduction, we know storage2 is a GPv2 account, which is capable of hosting standard file shares. The selection 'storage2 only' indicates that among the available options, only storage2 is considered suitable for this requirement.
    • This implies that storage3 (which we deduced as GPv2 for blobs) is, for an unstated reason within the context of this specific question, not considered suitable for file shares. This could be due to a specific configuration not provided in the case study's missing 'storage accounts' table, or it might be a subtle nuance the question intends to test. It also implies that storage1 and storage4 are not suitable for standard/Cool tier file shares (e.g., storage1 is GPv1, storage4 is a FileStorage account for premium files or a BlockBlobStorage account that cannot host files at all).

Common mistakes.

  • common_mistake. A common mistake is selecting storage account types that do not support the specified storage tier or service. For 'container1', choosing any account other than GPv2 (e.g., GPv1 or BlockBlobStorage) would be incorrect because they do not support the Cool tier for blobs. For 'share1', selecting a FileStorage account (if storage4 were one) would be wrong because FileStorage accounts are for Premium file shares, not 'Cool' (standard/cost-effective) ones. Another mistake for share1 would be assuming all GPv2 accounts (like storage3, which is suitable for Cool blobs) are always suitable for file shares, without considering potential unstated limitations or specific configurations that the question implies through its chosen correct answer. Selecting storage1 for share1 would also be incorrect if storage1 is a GPv1 account, which, while capable of hosting standard file shares, might be deemed less optimal or not align with the 'Cool tier' implication compared to a GPv2 account, or be explicitly unsuitable for other unstated reasons within the case study.

Concept tested. Understanding Azure Storage account types (General-purpose v1, General-purpose v2, BlockBlobStorage, FileStorage) and their specific capabilities regarding supported services (blobs, files) and access tiers (Hot, Cool, Archive, Standard, Premium). This includes knowing which account types support the Cool tier for blob storage and what 'Cool tier' implies for Azure file shares.

Topics

#Azure AD Connect#Azure RBAC#Azure NSG rules#Azure Blob Storage

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-104 Practice