Microsoft AZ-140 Practice Test Questions, Exam Dumps

Practice Exams:

View All

AZ-140 Microsoft Practice Test Questions and Exam Dumps

Question No 1:

You have an Azure Active Directory (Azure AD) tenant called contoso.com and an Azure Virtual Network (VNET1).
You deploy an Azure Active Directory Domain Services (Azure AD DS) managed domain called into VNET1.Additionally, you plan to deploy an Azure Virtual Desktop host pool named Pool1 into VNET1.You need to ensure that you can successfully deploy Windows 10 Enterprise session hosts to Pool1.

What should you do first?

A. Modify the settings of the litwareinc.com DNS zone
B. Modify the DNS settings of VNET1
C. Add a custom domain name to
D. Implement Azure AD Connect cloud sync

Answer: B. Modify the DNS settings of VNET1

Explanation:

In this scenario, you're setting up Azure Active Directory Domain Services (Azure AD DS) and Azure Virtual Desktop (AVD) on the same Virtual Network (VNET1). The task is to ensure that Windows 10 Enterprise session hosts can be successfully deployed into the AVD host pool, Pool1.

When you deploy Azure AD DS (in this case, litwareinc.com) into your Azure Virtual Network, a managed domain is created that supports Active Directory capabilities like domain join, group policy, and LDAP/kerberos-based authentication. However, for Azure Virtual Desktop (AVD) to be able to deploy session hosts such as Windows 10 Enterprise, these session hosts need to be able to join the domain created by Azure AD DS.

To achieve this, the DNS settings of your Azure Virtual Network (VNET1) must point to the Azure AD DS DNS servers. This allows the virtual machines (VMs), including the session hosts in Pool1, to resolve the domain name of litwareinc.com correctly. Specifically, the VMs must be able to resolve the DNS records for the domain controllers within Azure AD DS to enable proper domain joining.

Why is B the correct answer?

Modifying the DNS settings of VNET1 ensures that the VMs deployed in Pool1 can correctly communicate with the Azure AD DS domain (litwareinc.com) for domain joining. Without proper DNS resolution, the session hosts won't be able to join the managed domain, and the deployment will fail.

Why the other options are incorrect:

A. Modify the settings of the litwareinc.com DNS zone: This is not necessary because Azure AD DS already provides the DNS zone for the managed domain (litwareinc.com). You don't need to manually modify this DNS zone.
C. Add a custom domain name to contoso.com: Adding a custom domain to contoso.com is unnecessary in this scenario because contoso.com is already your Azure AD tenant, and you have deployed Azure AD DS with litwareinc.com as the managed domain. No changes to the Azure AD domain are needed for the deployment.
D. Implement Azure AD Connect cloud sync: Azure AD Connect is used for syncing on-premises Active Directory with Azure AD. This is not required for the scenario where you're using Azure AD DS to manage domain services within Azure. The cloud sync is unnecessary as you're already working within a fully Azure-based environment.

In summary, to enable Windows 10 Enterprise session hosts to be deployed in your AVD host pool, you must configure the DNS settings of the virtual network (VNET1) to point to the Azure AD DS DNS servers. This will ensure the VMs can successfully join the litwareinc.com domain, allowing the deployment to proceed smoothly.

Question No 2:

You are planning to deploy Azure Virtual Desktop for client access to virtualized applications. Your organization has a set of devices that will be used by employees to access these applications remotely. You need to determine which of the devices listed below are compatible with the Remote Desktop Client for this deployment.

Based on the device specifications, which of the following devices will support the Remote Desktop client to connect to Azure Virtual Desktop?

A. Device1 and Device2 only
B. Device1 and Device3 only
C. Device1, Device2, and Device3
D. Device1 only

Correct Answer: C. Device1, Device2, and Device3

Explanation:

Azure Virtual Desktop (AVD) enables users to access virtualized applications and desktops from various types of devices, including Windows, macOS, Android, and iOS devices. To access these virtualized environments, users must use the Remote Desktop client, which is supported across a variety of platforms. Let’s break down each device to see whether it supports the Remote Desktop client for AVD.

Device1 (Windows 10 Pro laptop):

Operating System: Windows 10 Pro, Version 20H2

Remote Desktop Client Compatibility: The Remote Desktop client is natively supported on Windows 10 and newer versions. Users can directly use the built-in Remote Desktop Connection (RDP) client or download the Microsoft Remote Desktop app from the Microsoft Store for improved features and security.

Conclusion: Device1 supports the Remote Desktop client and can easily connect to Azure Virtual Desktop.

Device2 (macOS desktop):

Operating System: macOS Big Sur

Remote Desktop Client Compatibility: The Remote Desktop client is available for macOS through the Microsoft Remote Desktop app, which is available for download from the Mac App Store. Once installed, users can connect to Azure Virtual Desktop and use virtualized applications.

Conclusion: Device2 supports the Remote Desktop client and can connect to Azure Virtual Desktop.

Device3 (Android mobile phone):

Operating System: Android 10

Remote Desktop Client Compatibility: The Microsoft Remote Desktop app is available for Android devices through the Google Play Store. With this app, users can access Azure Virtual Desktop and virtualized applications on their Android devices.

Conclusion: Device3 supports the Remote Desktop client and is compatible with Azure Virtual Desktop.

Summary of Compatibility:

Windows 10 Pro (Device1) has native support for Remote Desktop.
macOS Big Sur (Device2) supports Remote Desktop through the Microsoft Remote Desktop app.
Android 10 (Device3) also supports Remote Desktop via the Microsoft Remote Desktop app.

Given that all three devices (Device1, Device2, and Device3) are capable of running the Remote Desktop client and connecting to Azure Virtual Desktop, the correct answer is:

Answer: C. Device1, Device2, and Device3

This explanation clarifies how Azure Virtual Desktop and the Remote Desktop client work across different operating systems and devices. By understanding the compatibility of the client app for each device type, businesses can ensure seamless access to virtualized apps across various platforms.

Question No 3:

You are planning to deploy Azure Virtual Desktop (AVD) and will be using existing virtual machines for this deployment. You’ve already created an Azure Virtual Desktop host pool.
To ensure that you can successfully add the virtual machines to the host pool, what is the first step you need to take?

A. Register the Microsoft.DesktopVirtualization provider
B. Generate a registration key
C. Run the Invoke-AzVMRunCommand cmdlet
D. Create a role assignment

Answer: B. Generate a registration key

Explanation:

When deploying Azure Virtual Desktop (AVD), the goal is to create a seamless experience by adding virtual machines (VMs) to a host pool. The process of integrating virtual machines into the host pool involves several steps, each of which prepares the environment for AVD's virtual desktop and session host management.

In this case, the virtual machines have already been created, and an Azure Virtual Desktop host pool is set up. The next critical step is to register the virtual machines to the host pool to ensure they can be used as session hosts for AVD. The first step in this registration process is to generate a registration key.

Why is B. Generate a registration key the correct answer?

To add virtual machines to an Azure Virtual Desktop host pool, you need a registration key. This key is essential for the registration process that connects the virtual machines (VMs) to the host pool. The registration key is generated within the Azure Virtual Desktop (AVD) portal and is used to register the VMs to the host pool securely.

Once the registration key is generated, you can use it to execute the registration process from within the virtual machine. This key facilitates the registration process by authenticating the machine to the Azure Virtual Desktop infrastructure.

Why the other options are incorrect:

A. Register the Microsoft.DesktopVirtualization provider:
This is an important step for setting up Azure Virtual Desktop for the first time, but it is typically done during the initial setup of the Azure Virtual Desktop environment. In this scenario, the provider has likely already been registered as part of the overall AVD setup process, so this is not the first action needed once the host pool is created.
C. Run the Invoke-AzVMRunCommand cmdlet:
The Invoke-AzVMRunCommand cmdlet is used to run commands remotely on virtual machines in Azure. While you might use this to execute certain tasks or scripts on the VMs, it is not required to add VMs to the host pool directly. This cmdlet would be more applicable after the registration key is generated to automate steps on the VMs.
D. Create a role assignment:
Role assignments (e.g., assigning roles to users or service principals) are part of managing access and permissions within Azure. However, for the specific task of adding a virtual machine to a host pool, the first step is generating the registration key. Role assignments would come into play after the registration process if you need to assign access to specific users for managing the host pool.

In summary:

To add existing virtual machines to an Azure Virtual Desktop host pool, the first action required is to generate a registration key. This key is necessary to initiate the process of registering the VMs into the host pool, enabling them to act as session hosts in the Azure Virtual Desktop environment.

Question No 4:

You are in the process of designing an Azure Virtual Desktop (AVD) deployment for your organization. During the planning phase, you identify that there may be network latency between the geographic locations where users are located and the planned Azure region for deploying the host pool.

To optimize performance and reduce latency, what tool should you use to help determine the best Azure region for deploying the host pool based on the user locations?

A. Azure Traffic Manager
B. Azure Virtual Desktop Experience Estimator
C. Azure Monitor for Azure Virtual Desktop
D. Azure Advisor

Correct Answer: B. Azure Virtual Desktop Experience Estimator

Explanation:

When deploying Azure Virtual Desktop (AVD), it's crucial to optimize the deployment by selecting the best Azure region. The choice of region impacts network performance, application responsiveness, and overall user experience. In particular, network latency between users' physical locations and the Azure region hosting the AVD session hosts is a key factor in determining where to deploy the host pool.

Let’s explore each option to see which one would be most useful for this task:

Azure Traffic Manager:

What it does: Azure Traffic Manager is a DNS-based load balancing service that directs traffic to the nearest available endpoint based on various routing methods (geographic, priority, performance, etc.). It can be used to route traffic to different regions for high availability and performance.

Why it’s not the best choice: While Azure Traffic Manager helps distribute traffic to different endpoints, it doesn’t specifically focus on helping you select the optimal Azure region for an AVD deployment based on user location and latency. It’s more focused on directing traffic to the right endpoints after you’ve already chosen your region.

Azure Virtual Desktop Experience Estimator:

What it does: The Azure Virtual Desktop Experience Estimator is a tool specifically designed to assess the network performance between different geographic locations (user locations) and potential Azure regions for deploying Azure Virtual Desktop. This tool helps you identify which region offers the best performance, lowest latency, and overall optimal experience for your users.

Why it’s the best choice: This tool provides precise data on latency and network performance to help you choose the best region for deploying your Azure Virtual Desktop host pool, making it the ideal solution for addressing network latency concerns and ensuring a smooth user experience.

Azure Monitor for Azure Virtual Desktop:

What it does: Azure Monitor for Azure Virtual Desktop is a monitoring tool that helps track the performance of your deployed AVD environment, such as session host performance, user sessions, and overall system health. It collects metrics and logs to help diagnose issues.

Why it’s not the best choice: While Azure Monitor is invaluable for ongoing management and troubleshooting, it does not help with choosing the best region for deploying the host pool. It focuses more on post-deployment monitoring

Azure Advisor:

What it does: Azure Advisor provides personalized best practice recommendations across a range of Azure services, including performance, security, cost, and reliability. It suggests optimizations and improvements based on your environment’s configuration.

Why it’s not the best choice: Although Azure Advisor offers useful recommendations, it doesn’t specifically help with identifying the optimal region for Azure Virtual Desktop deployments based on network latency. It’s more general-purpose and doesn’t focus on the network performance needed for AVD.

To optimize the performance of Azure Virtual Desktop based on user location and minimize network latency, the Azure Virtual Desktop Experience Estimator is the most suitable tool. It specifically evaluates network performance and helps you select the best Azure region for hosting the AVD deployment, ensuring a better experience for users across various locations.

Thus, the correct answer is:B. Azure Virtual Desktop Experience Estimator

Question No 5:

You currently have an Azure Virtual Desktop (AVD) host pool named Pool1 in the East US region. The storage1 storage account contains FSLogix profile containers. Additionally, in the East US region, you have a shared image gallery (SIG) named SIG1, which holds a virtual machine image called Image1. Image1 is used to create new session hosts for Pool1.

Now, you plan to deploy a new Azure Virtual Desktop host pool, named Pool2, in the South India region. You need to implement a session host deployment solution for Pool2 that satisfies the following requirements:

Image1 must be replicated in the South India region.
The session hosts in Pool2 must be based on Image1.
Any changes made to Image1 must be available in both the South India and East US regions.

Which solution should you implement to meet these requirements?

A. Create a new shared image gallery named SIG2 in the South India region and upload a copy of Image1 to SIG2.
B. Create a new Azure Storage account named storage2 in the South India region and copy Image1 to a shared folder in storage2.
C. From SIG1, update the replication settings for the latest version of Image1.
D. Configure geo-redundant storage (GRS) replication for storage1 and copy the VHD file of Image1 to the FSLogix profile container.

Answer: C. From SIG1, update the replication for the latest image version of Image1.

Explanation:

To meet the requirements for deploying Pool2 in the South India region while ensuring that Image1 can be used as the base image for session hosts in Pool2, and that updates to Image1 are reflected in both regions, the most efficient solution is to update the replication settings for the shared image gallery (SIG1).

Here’s why each option either works or doesn't meet the requirements:

Option A: Create a new shared image gallery named SIG2 in the South India region and upload a copy of Image1 to SIG2.

While this option might seem viable at first, it's not the most efficient solution. Creating a new image gallery in the South India region and uploading a copy of Image1 would require maintaining separate copies of the image in both regions. This solution does not fully meet the requirement to ensure that any changes made to Image1 are reflected in both regions automatically. Instead, the more optimal approach is to manage the image centrally and leverage replication for automatic updates, which is precisely what Option C provides.

Option B: Create a new Azure Storage account named storage2 in the South India region and copy Image1 to a shared folder in storage2.

This option involves copying Image1 to a different storage account in the South India region. While this would make the image available in that region, it does not integrate with the shared image gallery (SIG) feature, which is designed for managing and distributing VM images across regions. Moreover, copying the image manually to a new storage account does not address the requirement for seamless replication of changes between regions.

Option C: From SIG1, update the replication for the latest image version of Image1.

This is the correct and most efficient solution. Azure Shared Image Galleries support geo-replication, allowing you to replicate a single image across multiple regions. By enabling replication from SIG1 (in the East US region) to the South India region, Image1 will be available in both regions, and any changes made to the image (such as updates or patches) will automatically be reflected in both regions. This satisfies the requirement that changes to Image1 be available in both regions and ensures that Pool2 can use the same image as Pool1.

Option D: Configure geo-redundant storage (GRS) replication for storage1 and copy the VHD file of Image1 to the FSLogix profile container.

This option involves configuring geo-redundant storage (GRS) for storage1 and copying the VHD file to the FSLogix profile container. While GRS ensures the redundancy of the storage account, it does not directly help with replicating the virtual machine image across regions in a manner that is compatible with Azure Virtual Desktop (AVD) and Shared Image Gallery. FSLogix profile containers are for user profiles, not for replicating VM images. Therefore, this option does not meet the needs of deploying and managing session hosts across regions based on Image1.

By enabling replication in Shared Image Gallery (SIG1), you ensure that Image1 is automatically replicated to the South India region, thus fulfilling the deployment requirements for Pool2 while ensuring that any changes to Image1 are reflected in both the East US and South India regions. This makes Option C the most effective solution.