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

Sample Questions

Explanation:

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

To start using Azure Virtual Desktop Insights, you need at least one Log Analytics workspace. Use a designated Log Analytics workspace for your Azure Virtual Desktop session hosts to ensure that performance counters and events are only collected from session hosts in your Azure Virtual Desktop deployment.

You use the Azure Monitor Agent to collect information on your Azure Virtual Desktop session hosts.

Reference: Enable Insights to monitor Azure Virtual Desktop

Explanation:

Azure Virtual Desktop uses Azure Monitor for monitoring and alerts like many other Azure services. This lets admins identify issues through a single interface. The service creates activity logs for both user and administrative actions.

Connections that don't reach Azure Virtual Desktop won't show up in diagnostics results because the diagnostics role service itself is part of Azure Virtual Desktop. Azure Virtual Desktop connection issues can happen when the user is experiencing network connectivity issues.

The following query list lets you review connection information or issues for a single user. You can run these queries in the Log Analytics query editor. For each query, replace userupn with the UPN of the user you want to look up.

To find all connections for a single user:

WVDConnections
|where UserName == "userupn"
|take 100
|sort by TimeGenerated asc, CorrelationId

To find the number of times a user connected per day:

WVDConnections
|where UserName == "userupn"
|take 100
|sort by TimeGenerated asc, CorrelationId
|summarize dcount(CorrelationId) by bin(TimeGenerated, 1d)

To find session duration by user:

let Events = WVDConnections | where UserName == "userupn";
Events
| where State == "Connected"
| project CorrelationId , UserName, ResourceAlias , StartTime=TimeGenerated
| join (Events
| where State == "Completed"
| project EndTime=TimeGenerated, CorrelationId)
on CorrelationId
| project Duration = EndTime - StartTime, ResourceAlias
| sort by Duration asc

Reference: Send diagnostic data to Log Analytics for Azure Virtual Desktop

• Generation: 2
• Virtual disk name: ImageC.vhdx
• Virtual disk type: Dynamically expanding

Explanation:

Before you upload a Windows virtual machine (VM) from on-premises to Azure, you must prepare the virtual hard disk (VHD or VHDX). Azure supports both generation 1 and generation 2 VMs that are in VHD file format and that have a fixed-size disk. The maximum size allowed for the OS VHD on a generation 1 VM is 2 TB.

You can convert a VHDX file to VHD, convert a dynamically expanding disk to a fixed-size disk, but you can't change a VM's generation.

You can run the following PowerShell command to change the disk to a fixed disk.

Convert-VHD –Path c:\test\MY-VM.vhdx –DestinationPath c:\test\MY-NEW-VM.vhd -VHDType Fixed

Upload the VHD to a blob container in your storage account and use the Create an image page from the Azure Portal to create a managed image that can be used to deploy virtual machines and virtual machine scale sets.

References:

Prepare a Windows VHD or VHDX to upload to Azure

Prepare and customize a VHD image for Azure Virtual Desktop

• Virtual machine generation: Generation 2
• Disk type: Dynamically expanding
• Disk format: VHDX
• Disk size: 2 TB

Explanation:

Before you upload a Windows virtual machine (VM) from on-premises to Azure, you must prepare the virtual hard disk (VHD or VHDX). Azure supports both generation 1 and generation 2 VMs that are in VHD file format and that have a fixed-size disk. The maximum size allowed for the OS VHD on a generation 1 VM is 2 TB.

You can convert a VHDX file to VHD, convert a dynamically expanding disk to a fixed-size disk, but you can't change a VM's generation.

You can run the following PowerShell command to change the disk to a fixed disk.

Convert-VHD –Path c:\test\MY-VM.vhdx –DestinationPath c:\test\MY-NEW-VM.vhd -VHDType Fixed

Upload the VHD to a blob container in your storage account and use the Create an image page from the Azure Portal to create a managed image that can be used to deploy virtual machines and virtual machine scale sets.

References:

Prepare a Windows VHD or VHDX to upload to Azure

Prepare and customize a VHD image for Azure Virtual Desktop

Explanation:

We should add either a private endpoint to storage1 or a service endpoint to VNet1.

A private endpoint is a network interface that uses a private IP address from your virtual network. This network interface connects you privately and securely to a service that's powered by Azure Private Link. By enabling a private endpoint, you're bringing the service into your virtual network.

Azure virtual network service endpoints provide secure and direct connectivity to Azure services over an optimized route through the Azure backbone network. These endpoints allow you to secure critical Azure service resources exclusively to your virtual networks, enabling private IP addresses to reach Azure services without requiring public IP addresses.

References:

Azure virtual network service endpoints

What is a private endpoint?

Service Endpoints vs Private Endpoints