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

Sample Questions

Explanation:

App Attach enables you to dynamically attach applications from an application package to a user session in Azure Virtual Desktop. Applications aren't installed locally on session hosts or images, making it easier to create custom images for your session hosts, and reducing operational overhead and costs for your organization. Applications run within containers, which separate user data, the operating system, and other applications, increasing security and making them easier to troubleshoot.

To use MSIX packages with App Attach in Azure Virtual Desktop, you need to expand an MSIX package application into an MSIX image using the MSIXMGR tool.

Application images

Disk image types

For MSIX and Appx disk images, you can use Composite Image File System (CimFS), VHDX, or VHD, but we don't recommend using VHD. Mounting and unmounting CimFS images is faster than VHD and VHDX images and also consumes less CPU and memory. We only recommend using CimFS for your application images if your session hosts are running Windows 11.

A CimFS image is a combination of several files: one file has the .cim file extension and contains metadata, together with at least two other files, one starting with objectid_ and the other starting with region_ that contain the actual application data. The files accompanying the .cim file don't have a file extension.

References:

App Attach in Azure Virtual Desktop

Create an MSIX image to use with App Attach in Azure Virtual Desktop

Explanation:

You can connect to remote desktops and apps running in Remote Desktop Services using Windows App or the Remote Desktop client.

Windows App and the Remote Desktop client are available on many different types of devices on different platforms and form factors, such as desktops and laptops, tablets, smartphones, through a web browser, and virtual reality headsets. This choice provides flexibility and convenience to access desktops and apps from anywhere.

Here's what platforms you can use to connect to Remote Desktop Services from Windows App and the Remote Desktop client:

The Remote Desktop web client lets you use a compatible web browser to access your organization's remote resources (apps and desktops) published to you by your admin. You'll be able to interact with the remote apps and desktops like you would with a local PC no matter where you are, without having to switch to a different desktop PC. Once your admin sets up your remote resources, all you need are your domain, user name, password, the URL your admin sent you, and a supported web browser, and you're good to go.

What you'll need to use the web client

• For the web client, you'll need a PC running Windows, macOS, ChromeOS, or Linux. Mobile devices aren't supported at this time.
• A modern browser like Microsoft Edge, Google Chrome, Apple Safari, or Mozilla Firefox (v55.0 and later).
• The URL your admin sent you.

References:

Connect to Remote Desktop Services in Windows Server

Get started with the web client

Explanation:

App Attach enables you to dynamically attach applications from an application package (MSIX or Appx) to a user session in Azure Virtual Desktop.

The MSIX Packaging Tool enables you to repackage your existing desktop applications to the MSIX format. It offers both an interactive UI and a command line for conversions, and gives you the ability to convert an application without having the source code. 

You can use the MSIX Packaging Tool to create an MSIX application package from any of the following options:

• MSI
• EXE
• ClickOnce
• App-V
• Script
• Manual installation

The tool captures registry and file system changes during installation.

References:

App Attach in Azure Virtual Desktop

MSIX Packaging Tool

Create an MSIX package from any desktop installer (MSI, EXE, ClickOnce, or App-V)

Explanation:

We should recreate share1 as an Azure Files Premium share. Azure Files Premium shares can improve performance by using SMB Multichannel and metadata caching.

SMB Multichannel enables an SMB client to establish multiple network connections to an SMB file share, improving throughput and resiliency. Azure Files supports SMB Multichannel on SSD file shares for both Windows and Linux SMB clients.

Reference: Improve performance for SMB Azure file shares

• Support FSLogix Profile containers.
• Minimize costs.

Explanation:

FSLogix profile containers are a complete roaming user profile solution for Windows desktop scenarios, such as Azure Virtual Desktop. Users can sign in to different devices and want their customization and personalization data roam to whichever device or session they connect to.

FSLogix is designed to roam profiles in remote computing environments, such as Azure Virtual Desktop. At sign-in, this container is dynamically attached to the computing environment using a natively supported Virtual Hard Disk (VHD) and a Hyper-V Virtual Hard Disk (VHDX). The user profile is immediately available and appears in the system exactly like a native user profile. All FSLogix containers can be stored on file shares that support the SMB protocol.

Azure Files offers two different tiers of storage: premium and standard. These tiers let you tailor the performance and cost of your file shares to meet your scenario's requirements.

• Premium file shares are backed by solid-state drives (SSDs) and are deployed in the FileStorage storage account type. Premium file shares provide consistent high performance and low latency for input and output (IO) intensive workloads. Premium file shares use a provisioned billing model, where you pay for the amount of storage you would like your file share to have, regardless of how much you use.

• Standard file shares are backed by hard disk drives (HDDs) and are deployed in the general purpose version 2 (GPv2) storage account type. Standard file shares provide reliable performance for IO workloads that are less sensitive to performance variability, such as general-purpose file shares and dev/test environments. Standard file shares use a pay-as-you-go billing model, where you pay based on storage usage, including data stored and transactions.

An Azure Files standard file share hosted on HDD provide is the most cost-effective storage option.

References:

Configure profile containers using FSLogix

Storage options for FSLogix profile containers in Azure Virtual Desktop

Understand Azure Files billing models