Case Study 2 - Contoso, Ltd Overview Contoso, Ltd. is a manufacturing company that has offices worldwide. Contoso works with partner organizations to bring products to market. Contoso products are…

The scenario explicitly requires Azure Blob storage for blueprint files, with no stated requirement for Table or File storage.

Submitted by akirajp· Mar 4, 2026Deploy and manage Azure compute resources

Question

Case Study 2 - Contoso, Ltd Overview Contoso, Ltd. is a manufacturing company that has offices worldwide. Contoso works with partner organizations to bring products to market. Contoso products are manufactured by using blueprint files that the company authors and maintains. Existing Environment Currently, Contoso uses multiple types of servers for business operations, including the following: - File servers - Domain controllers - Microsoft SQL Server servers Your network contains an Active Directory forest named contoso.com. All servers and client computers are joined to Active Directory. You have a public-facing application named App1. App1 is comprised of the following three tiers: - A SQL database - A web front end - A processing middle tier Each tier is comprised of five virtual machines. Users access the web front end by using HTTPS only. Requirements Planned Changes Contoso plans to implement the following changes to the infrastructure: - Move all the tiers of App1 to Azure. - Move the existing product blueprint files to Azure Blob storage. - Create a hybrid directory to support an upcoming Microsoft Office 365 migration project. Technical Requirements Contoso must meet the following technical requirements: - Move all the virtual machines for App1 to Azure. - Minimize the number of open ports between the App1 tiers. - Ensure that all the virtual machines for App1 are protected by backups. - Copy the blueprint files to Azure over the Internet. - Ensure that the blueprint files are stored in the archive storage tier. - Ensure that partner access to the blueprint files is secured and temporary. - Prevent user passwords or hashes of passwords from being stored in Azure. - Use unmanaged standard storage for the hard disks of the virtualmachines. - Ensure that when users join devices to Azure Active Directory (Azure AD), the users use a mobile phone to verify their identity. - Minimize administrative effort whenever possible. User Requirements Contoso identifies the following requirements for users: - Ensure that only users who are part of a group named Pilot can join devices to Azure AD. - Designate a new user named Admin1 as the service administrator of the Azure subscription. - Ensure that a new user named User3 can create network objects for the Azure subscription. Hotspot Question You need to identify the storage requirements for Contoso. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

Contoso requires a storage account that supports Blob storage.
Contoso requires a storage account that supports Azure Table storage.
Contoso requires a storage account that supports Azure File Storage.

Explanation

The scenario explicitly requires Azure Blob storage for blueprint files, with no stated requirement for Table or File storage.

Approach. 1. For 'Contoso requires a storage account that supports Blob storage', select Yes. The 'Planned Changes' section explicitly states the requirement to 'Move the existing product blueprint files to Azure Blob storage.' 2. For 'Contoso requires a storage account that supports Azure Table storage', select No. There is no mention in the case study of a need for NoSQL key/value data storage. 3. For 'Contoso requires a storage account that supports Azure File Storage', select No. While the company currently has on-premises file servers, the planned migration specifically targets Blob storage for the blueprint files, and no requirement for SMB/NFS file shares in Azure is listed.

Common mistakes.

common_mistake. A common mistake is selecting 'Yes' for Azure File Storage because the 'Existing Environment' lists 'File servers'. However, test-takers must follow the explicitly stated 'Planned Changes', which dictate moving those files specifically to Blob storage, not Azure Files.

Concept tested. Mapping business and technical requirements to appropriate Azure Storage services (Blob, Table, File).

Reference. https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction

Topics

#Azure App Migration#3-tier Architecture#Azure Virtual Machines#On-premises Active Directory

Community Discussion

No community discussion yet for this question.

Full AZ-104 Practice