Microsoft - AZ-140: Configuring and Operating Microsoft Azure Virtual Desktop

Sample Questions

Explanation:

The Security Requirements section contains the following.

The client version and operating system used to connect to the session hosts must be logged.

Azure Virtual Desktop Insights is a dashboard built on Azure Monitor Workbooks that helps IT professionals understand their Azure Virtual Desktop environments.

Azure Virtual Desktop Insights is specifically designed to monitor Azure Virtual Desktop environments. It provides detailed telemetry including:

• Client version
• Operating system used by the client
• Connection diagnostics
• Session performance metrics
• Host pool and workspace diagnostics

References:

Enable Insights to monitor Azure Virtual Desktop

Monitoring considerations for Azure Virtual Desktop workloads

Explanation:

The Disaster Recovery Requirements section contains the following.

• Minimize outages if an Azure region fails.
• Minimize the recovery time objective (RTO).
• Minimize administrative effort in the event of a failover.

To minimize outages if an Azure region fails, we need to deploy two host pools in different Azure regions. A single Azure Virtual Desktop host pool cannot span multiple Azure regions. All session hosts within a single host pool must reside in the same Azure region.

Azure Front Door should be used to distribute traffic across the host pools located in different Azure regions. It acts as a global load balancer, allowing you to configure routing rules that direct traffic to backends such as host pools in multiple regions. Azure Front Door is a fully managed service, so you don't have to worry about scaling or maintenance.

References:

Azure Virtual Desktop business continuity and disaster recovery concepts

Multiregion Business Continuity and Disaster Recovery (BCDR) for Azure Virtual Desktop

Azure Front Door frequently asked questions (FAQ)

Explanation:

The Performance Requirements section contains the following.

• Each Azure Virtual Desktop session host must support 15 user sessions.
• Each new user session must be assigned to a single session host until the maximum session limit is reached for that host.

A host pool is a collection of Azure virtual machines that are registered to Azure Virtual Desktop as session hosts. All session host virtual machines in a host pool should be sourced from the same image for a consistent user experience. You control the resources published to users through application groups.

A host pool can be one of two types:

• Personal, where each session host is assigned to an individual user. Personal host pools provide dedicated desktops to end-users that optimize environments for performance and data separation.

• Pooled, where user sessions can be load balanced to any session host in the host pool. There can be multiple different users on a single session host at the same time. Pooled host pools provide a shared remote experience to end-users, which ensures lower costs and greater efficiency.

Azure Virtual Desktop supports two load balancing algorithms for pooled host pools. Each algorithm determines which session host is used when a user starts a remote session. Load balancing doesn't apply to personal host pools because users always have a 1:1 mapping to a session host within the host pool.

The following load balancing algorithms are available for pooled host pools:

• Breadth-first, which aims to evenly distribute new user sessions across the session hosts in a host pool. You don't have to specify a maximum session limit for the number of sessions.

• Depth-first, which keeps starting new user sessions on one session host until the maximum session limit is reached. Once the session limit is reached, any new user connections are directed to the next session host in the host pool until it reaches its session limit, and so on.

References:

Azure Virtual Desktop terminology

Configure host pool load balancing in Azure Virtual Desktop

Explanation:

FSLogix provides Group Policy administrative template files in the form of .admx and language-specific .adml files. These files can be used within the Local Group Policy Editor and the Group Policy Management Editor. The Local Group Policy Editor is used to edit Local Group Policy Objects (LGPOs). The Group Policy Management Editor, which is available from within the Group Policy Management Console (GPMC), can be used to edit domain-based policy objects.

When local Group Policy Objects (LGPOs) are used, the template files must be copied to the following locations:

Reference: Using FSLogix Group Policy Template Files

Explanation:

FSLogix works with SMB storage systems to store Profile or ODFC containers. SMB storage is used in standard configurations where VHDLocations holds the UNC path to the storage locations. SMB storage providers can also be used in Cloud Cache configurations where CCDLocations is used instead of VHDLocations.

SMB storage permissions rely on traditional NTFS Access Control Lists (ACL) applied at file or folder levels to ensure the proper security of the data that is stored.

Windows ACL(s) are important to configure correctly so that only the user (CREATOR OWNER) has access to their profile directory or VHD(x) file. Additionally, you need to ensure any other administrative groups have 'Full Control' from an operational perspective. This concept is known as user-based access and is the recommended configuration.

The table outlines the recommended ACL(s) to be configured.

Reference: Configure SMB Storage Permissions