Case Study 3 - Contoso, Ltd Overview Contoso, Ltd. is a consulting company that has a main office in Montreal and two branch offices in Seattle and New York. The Montreal office has 2,000 employees. T

To set up Azure Site Recovery for on-premises Hyper-V VMs, you must first create a Recovery Services vault in the Azure portal and then install the Azure Site Recovery Provider on the on-premises Hyper-V host server.

Submitted by anjalisingh· Mar 4, 2026Manage Azure identities and governance

Question

Case Study 3 - Contoso, Ltd Overview Contoso, Ltd. is a consulting company that has a main office in Montreal and two branch offices in Seattle and New York. The Montreal office has 2,000 employees. The Seattle office has 1,000 employees. The New York office has 200 employees. All the resources used by Contoso are hosted on-premises. Contoso creates a new Azure subscription. The Azure Active Directory (Azure AD) tenant uses adomain named contoso.onmicrosoft.com. The tenant uses the P1 pricing tier. Existing Environment The network contains an Active Directory forest named contoso.com. All domain controllers are configured as DNS servers and host the contoso.com DNS zone. Contoso has finance, human resources, sales, research, and information technology departments. Each department has an organizational unit (OU) that contains all the accounts of that respective department. All the user accounts have the department attribute set to their respective department. New users are added frequently. Contoso.com contains a user named User1. All the offices connect by using private links. Contoso has data centers in the Montreal and Seattle offices. Each data center has a firewall that can be configured as a VPN device. All infrastructure servers are virtualized. The virtualization environment contains the servers in the following table. Contoso uses two web applications named App1 and App2. Each instance on each web application requires 1GB of memory. The Azure subscription contains the resources in the following table. The network security team implements several network security groups (NSGs). Planned Changes Contoso plans to implement the following changes: - Deploy Azure ExpressRoute to the Montreal office. - Migrate the virtual machines hosted on Server1 and Server2 to Azure. - Synchronize on-premises Active Directory to Azure Active Directory (Azure AD). - Migrate App1 and App2 to two Azure web apps named WebApp1 and WebApp2. Technical requirements Contoso must meet the following technical requirements: - Ensure that WebApp1 can adjust the number of instances automatically based on the load and can scale up to five instances. - Ensure that VM3 can establish outbound connections over TCP port 8080 to the applications servers in the Montreal office. - Ensure that routing information is exchanged automatically between Azure and the routers in the Montreal office. - Ensure Azure Multi-Factor Authentication (MFA) for the users in the finance department only. - Ensure that webapp2.azurewebsites.net can be accessed by using the name app2.contoso.com - Connect the New York office to VNet1 over the Internet by using an encrypted connection. - Create a workflow to send an email message when the settings of VM4 are modified. - Create a custom Azure role named Role1 that is based on the Reader role. - Minimize costs whenever possible. Hotspot Question You need to prepare the environment to implement the planned changes for Server2. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

From the Azure portal:
Create an Azure Migrate project.Create a Recovery Services vault.Upload a management certificate.Create an Azure Import/Export job.
On Server2:
Enable Hyper-V Replica.Install the Azure File Sync agent.Create a collector virtual machine.Configure Hyper-V storage migration.Install the Azure Site Recovery Provider.

Explanation

Approach. Based on the case study stating 'All infrastructure servers are virtualized' and the options provided, the most fitting scenario is setting up Azure Site Recovery (ASR) for disaster recovery or migration of on-premises Hyper-V virtual machines to Azure.

From the Azure portal: The initial step for any Azure Site Recovery deployment is to create a Recovery Services vault. This vault acts as a central repository for replication settings and recovery plans.
On Server2: Since Server2 is an on-premises server in a Hyper-V environment, and the goal is to replicate Hyper-V VMs to Azure using ASR, the necessary component to install on the Hyper-V host (Server2) is the Azure Site Recovery Provider. This agent facilitates communication between the on-premises Hyper-V host and Azure, enabling replication of VMs.

Common mistakes.

common_mistake. Other options are incorrect because they address different functionalities or outdated methods:

Azure portal - Create an Azure Migrate project: While Azure Migrate can orchestrate ASR for migration, the direct container for ASR operations is the Recovery Services vault. An Azure Migrate project is for broader discovery and assessment.
Azure portal - Upload a management certificate: This method is deprecated and was primarily used for classic Azure deployments, not for modern Azure Site Recovery setups.
Azure portal - Create an Azure Import/Export job: This service is for large-scale data transfer of files and blobs using physical drives, not for continuous replication of virtual machines.
On Server2 - Enable Hyper-V Replica: This is an on-premises disaster recovery feature for replicating VMs between Hyper-V hosts locally, not to Azure.
On Server2 - Install the Azure File Sync agent: This agent is used to synchronize file shares with Azure Files, unrelated to VM replication.
On Server2 - Create a collector virtual machine: This is typically associated with Azure Migrate for discovery and assessment of on-premises environments, not the agent for actual VM replication.
On Server2 - Configure Hyper-V storage migration: This is an on-premises Hyper-V operation to move VM storage within or between Hyper-V hosts, not related to Azure replication.

Concept tested. Initial setup and architectural components of Azure Site Recovery (ASR) for on-premises Hyper-V virtual machines, specifically understanding the roles of the Recovery Services vault in Azure and the Azure Site Recovery Provider on Hyper-V hosts.

Topics

#Azure AD tenants#Hybrid identity#On-premises Active Directory#Azure AD P1 features

Community Discussion

No community discussion yet for this question.

Full AZ-104 Practice