Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

You need to configure the device redirection settings. The solution must meet the technical requirements.

Where should you configure the settings?

Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

You need to configure the virtual machines that have the Pool1 prefix. The solution must meet the technical requirements.

What should you use?

Case Study

Overview -

Litware, Inc. is a pharmaceutical company that has a main office in Boston, United States, and a remote office in Chennai, India.

Existing Environment. Identity Environment

The network contains an on-premises Active Directory domain named litware.com that syncs to an Azure Active Directory (Azure AD) tenant named litware.com.

The Azure AD tenant contains the users shown in the following table.

All users are registered for Azure Multi-Factor Authentication (MFA).

Existing Environment. Cloud Services

Litware has a Microsoft 365 E5 subscription associated to the Azure AD tenant. All users are assigned Microsoft 365 Enterprise E5 licenses.

Litware has an Azure subscription associated to the Azure AD tenant. The subscription contains the resources shown in the following table.

Litware uses custom virtual machine images and custom scripts to automatically provision Azure virtual machines and join the virtual machines to the on-premises Active Directory domain.

Existing Environment. Network and DNS

The offices connect to each other by using a WAN link. Each office connects directly to the internet.

All DNS queries for internet hosts are resolved by using DNS servers in the Boston office, which point to root servers on the internet. The Chennai office has caching-only DNS servers that forward queries to the DNS servers in the Boston office.

Requirements. Planned Changes -

Litware plans to implement the following changes:

Deploy Azure Virtual Desktop environments to the East US Azure region for the users in the Boston office and to the South India Azure region for the users in the Chennai office.

Implement FSLogix profile containers.

Optimize the custom virtual machine images for the Azure Virtual Desktop session hosts.

Use PowerShell to automate the addition of virtual machines to the Azure Virtual Desktop host pools.

Requirements. Performance Requirements

Litware identifies the following performance requirements:

Minimize network latency of the Windows Virtual Desktop connections from the Boston and Chennai offices.

Minimize latency of the Windows Virtual Desktop host authentication in each Azure region.

Minimize how long it takes to sign in to the Windows Virtual Desktop session hosts.

Requirements. Authentication Requirements

Litware identifies the following authentication requirements:

Enforce Azure MFA when accessing Azure Virtual Desktop apps.

Force users to reauthenticate if their Azure Virtual Desktop session lasts more than eight hours.

Requirements. Security Requirements

Litware identifies the following security requirements:

Explicitly allow traffic between the Azure Virtual Desktop session hosts and Microsoft 365.

Explicitly allow traffic between the Azure Virtual Desktop session hosts and the Azure Virtual Desktop infrastructure.

Use built-in groups for delegation.

Delegate the management of app groups to Admin2, including the ability to publish app groups to users and user groups.

Grant Admin1 permissions to manage workspaces, including listing which apps are assigned to the app groups.

Minimize administrative effort to manage network security.

Use the principle of least privilege.

Requirements. Deployment Requirements

Litware identifies the following deployment requirements:

Use PowerShell to generate the token used to add the virtual machines as session hosts to an Azure Virtual Desktop host pool.

Minimize how long it takes to provision the Azure Virtual Desktop session hosts based on the custom virtual machine images.

Whenever possible, preinstall agents and apps in the custom virtual machine images.

User Profile Requirements -

Litware identifies the following user profile requirements:

In storage1, store user profiles for the Boston office users.

Ensure that the user profiles for the Boston office users replicate synchronously between two Azure regions.

Ensure that Admin1 uses a local profile only when signing in to the Azure Virtual Desktop session hosts.

Question

You need to ensure the resiliency of the user profiles for the Boston office users. The solution must meet the user performance requirements.

What should you do?

Case Study

Overview -

Litware, Inc. is a pharmaceutical company that has a main office in Boston, United States, and a remote office in Chennai, India.

Existing Environment. Identity Environment

The network contains an on-premises Active Directory domain named litware.com that syncs to an Azure Active Directory (Azure AD) tenant named litware.com.

The Azure AD tenant contains the users shown in the following table.

All users are registered for Azure Multi-Factor Authentication (MFA).

Existing Environment. Cloud Services

Litware has a Microsoft 365 E5 subscription associated to the Azure AD tenant. All users are assigned Microsoft 365 Enterprise E5 licenses.

Litware has an Azure subscription associated to the Azure AD tenant. The subscription contains the resources shown in the following table.

Litware uses custom virtual machine images and custom scripts to automatically provision Azure virtual machines and join the virtual machines to the on-premises Active Directory domain.

Existing Environment. Network and DNS

The offices connect to each other by using a WAN link. Each office connects directly to the internet.

All DNS queries for internet hosts are resolved by using DNS servers in the Boston office, which point to root servers on the internet. The Chennai office has caching-only DNS servers that forward queries to the DNS servers in the Boston office.

Requirements. Planned Changes -

Litware plans to implement the following changes:

Deploy Azure Virtual Desktop environments to the East US Azure region for the users in the Boston office and to the South India Azure region for the users in the Chennai office.

Implement FSLogix profile containers.

Optimize the custom virtual machine images for the Azure Virtual Desktop session hosts.

Use PowerShell to automate the addition of virtual machines to the Azure Virtual Desktop host pools.

Requirements. Performance Requirements

Litware identifies the following performance requirements:

Minimize network latency of the Windows Virtual Desktop connections from the Boston and Chennai offices.

Minimize latency of the Windows Virtual Desktop host authentication in each Azure region.

Minimize how long it takes to sign in to the Windows Virtual Desktop session hosts.

Requirements. Authentication Requirements

Litware identifies the following authentication requirements:

Enforce Azure MFA when accessing Azure Virtual Desktop apps.

Force users to reauthenticate if their Azure Virtual Desktop session lasts more than eight hours.

Requirements. Security Requirements

Litware identifies the following security requirements:

Explicitly allow traffic between the Azure Virtual Desktop session hosts and Microsoft 365.

Explicitly allow traffic between the Azure Virtual Desktop session hosts and the Azure Virtual Desktop infrastructure.

Use built-in groups for delegation.

Delegate the management of app groups to Admin2, including the ability to publish app groups to users and user groups.

Grant Admin1 permissions to manage workspaces, including listing which apps are assigned to the app groups.

Minimize administrative effort to manage network security.

Use the principle of least privilege.

Requirements. Deployment Requirements

Litware identifies the following deployment requirements:

Use PowerShell to generate the token used to add the virtual machines as session hosts to an Azure Virtual Desktop host pool.

Minimize how long it takes to provision the Azure Virtual Desktop session hosts based on the custom virtual machine images.

Whenever possible, preinstall agents and apps in the custom virtual machine images.

User Profile Requirements -

Litware identifies the following user profile requirements:

In storage1, store user profiles for the Boston office users.

Ensure that the user profiles for the Boston office users replicate synchronously between two Azure regions.

Ensure that Admin1 uses a local profile only when signing in to the Azure Virtual Desktop session hosts.

Question

You need to implement network security to meet the security requirements and the performance requirements.

Which two actions should you perform? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

Which role should you assign to Operator2 to meet the technical requirements?

Case Study -

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

DRAG DROP -

You need to evaluate the RDS deployment in the Seattle office. The solution must meet the technical requirements.

Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Select and Place:

Case Study

Overview -

Litware, Inc. is a pharmaceutical company that has a main office in Boston, United States, and a remote office in Chennai, India.

Existing Environment. Identity Environment

The network contains an on-premises Active Directory domain named litware.com that syncs to an Azure Active Directory (Azure AD) tenant named litware.com.

The Azure AD tenant contains the users shown in the following table.

All users are registered for Azure Multi-Factor Authentication (MFA).

Existing Environment. Cloud Services

Litware has a Microsoft 365 E5 subscription associated to the Azure AD tenant. All users are assigned Microsoft 365 Enterprise E5 licenses.

Litware has an Azure subscription associated to the Azure AD tenant. The subscription contains the resources shown in the following table.

Litware uses custom virtual machine images and custom scripts to automatically provision Azure virtual machines and join the virtual machines to the on-premises Active Directory domain.

Existing Environment. Network and DNS

The offices connect to each other by using a WAN link. Each office connects directly to the internet.

All DNS queries for internet hosts are resolved by using DNS servers in the Boston office, which point to root servers on the internet. The Chennai office has caching-only DNS servers that forward queries to the DNS servers in the Boston office.

Requirements. Planned Changes -

Litware plans to implement the following changes:

Deploy Azure Virtual Desktop environments to the East US Azure region for the users in the Boston office and to the South India Azure region for the users in the Chennai office.

Implement FSLogix profile containers.

Optimize the custom virtual machine images for the Azure Virtual Desktop session hosts.

Use PowerShell to automate the addition of virtual machines to the Azure Virtual Desktop host pools.

Requirements. Performance Requirements

Litware identifies the following performance requirements:

Minimize network latency of the Windows Virtual Desktop connections from the Boston and Chennai offices.

Minimize latency of the Windows Virtual Desktop host authentication in each Azure region.

Minimize how long it takes to sign in to the Windows Virtual Desktop session hosts.

Requirements. Authentication Requirements

Litware identifies the following authentication requirements:

Enforce Azure MFA when accessing Azure Virtual Desktop apps.

Force users to reauthenticate if their Azure Virtual Desktop session lasts more than eight hours.

Requirements. Security Requirements

Litware identifies the following security requirements:

Explicitly allow traffic between the Azure Virtual Desktop session hosts and Microsoft 365.

Explicitly allow traffic between the Azure Virtual Desktop session hosts and the Azure Virtual Desktop infrastructure.

Use built-in groups for delegation.

Delegate the management of app groups to Admin2, including the ability to publish app groups to users and user groups.

Grant Admin1 permissions to manage workspaces, including listing which apps are assigned to the app groups.

Minimize administrative effort to manage network security.

Use the principle of least privilege.

Requirements. Deployment Requirements

Litware identifies the following deployment requirements:

Use PowerShell to generate the token used to add the virtual machines as session hosts to an Azure Virtual Desktop host pool.

Minimize how long it takes to provision the Azure Virtual Desktop session hosts based on the custom virtual machine images.

Whenever possible, preinstall agents and apps in the custom virtual machine images.

User Profile Requirements -

Litware identifies the following user profile requirements:

In storage1, store user profiles for the Boston office users.

Ensure that the user profiles for the Boston office users replicate synchronously between two Azure regions.

Ensure that Admin1 uses a local profile only when signing in to the Azure Virtual Desktop session hosts.

Question

You need to modify the custom virtual machine images to meet the deployment requirements.

What should you install?

Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

You plan to implement the FSLogix profile containers for the Seattle office.

Which storage account should you use?

Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

HOTSPOT -

You are planning the deployment of Pool4.

What will be the maximum number of users that can connect to Pool4, and how many session hosts are needed to support five concurrent user

sessions? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Hot Area:

Case Study

Overview -

Contoso, Ltd. is a law firm that has a main office in Montreal and branch offices in Paris and Seattle. The Seattle branch office opened recently.

Contoso has an Azure subscription and uses Microsoft 365.

Existing Infrastructure. Active Directory

The network contains an on-premises Active Directory domain named contoso.com and an Azure Active Directory (Azure AD) tenant. One of the domain controllers runs as an Azure virtual machine and connects to a virtual network named VNET1. All internal name resolution is provided by DNS server that run on the domain controllers.

The on-premises Active Directory domain contains the organizational units (OUs) shown in the following table.

Existing Infrastructure. Network Infrastructure

All the Azure virtual networks are peered. The on-premises network connects to the virtual networks.

A virtual network named VNET4 was recently created are peered to the other virtual networks. VNET4 does NOT contain any AVD virtual machines.

All servers run Windows Server 2019. All laptops and desktop computers run Windows 10 Enterprise.

Since users often work on confidential documents, all the users use their computer as a client for connecting to Remote Desktop Services (RDS).

In the West US Azure region, you have the storage accounts shown in the following table.

Existing Infrastructure. Remote Desktop Infrastructure

Contoso has a Remote Desktop infrastructure shown in the following table.

Requirements. Planned Changes -

Contoso plans to implement the following changes:

Implement FSLogix profile containers for the Paris offices.

Deploy an Azure Virtual Desktop host pool named Pool4.

Migrate the RDS deployment in the Seattle office to Azure Virtual Desktop in the West US Azure region.

Requirements. Pool4 Configuration

Pool4 will have the following settings:

Host pool type: Pooled

Max session limit: 7

Load balancing algorithm: Depth-first

Images: Windows 10 Enterprise multi-session

Virtual machine size: Standard D2s v3

Name prefix: Pool4

Number of VMs: 5

Virtual network: VNET4

Requirements. Technical Requirements

Contoso identifies the following technical requirements:

Before migrating the RDS deployment in the Seattle office, obtain the recommended deployment configuration based on the current RDS utilization.

For the Azure Virtual Desktop deployment in the Montreal office, disable audio output in the device redirection settings.

For the Azure Virtual Desktop deployment in the Seattle office, store the FSLogix profile containers in Azure Storage.

Enable Operator2 to modify the RDP Properties of the Azure Virtual Desktop deployment in the Montreal office.

From a server named Server1, convert the user profile clicks to the FSLogix profile containers.

Ensure that the Pool1 virtual machines only run during business hours.

Use the principle of least privilege.

Question

Which setting should you modify for VNET4 before you can deploy Pool4?