AZ-140 Question #55: Real Exam Question with Answer & Explanation

Question

Case Study 1 - Contoso, Ltd 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. The on-premises Active Directory domain contains the users shown in the following table. The Azure AD tenant contains the cloud-only users 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. 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 a 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. Which three PowerShell modules should you install on Server1 to meet the technical requirements? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

• APester
• BRemoteDesktop
• CServerManager
• DActiveDirectory
• EHyper-V

Explanation

To convert User Profile Disks (UPDs) from the RDS deployment to FSLogix Profile Containers on Server1, Microsoft's migration script has three specific PowerShell module dependencies. ActiveDirectory (D) is required to look up user accounts and retrieve their Security Identifiers (SIDs), which FSLogix uses to map profiles to the correct users. Hyper-V (E) is needed because UPDs are stored as VHD/VHDX files - the module provides cmdlets to mount and access those virtual disks during the conversion. Pester (A) is a required dependency of the Microsoft-provided migration script itself, used internally for validation during the conversion process.

RemoteDesktop (B) is for managing RDS session hosts, gateways, and connection brokers - it handles infrastructure management, not profile format conversion, so it isn't needed on Server1 for this task. ServerManager (C) is for managing Windows Server roles and features and has no role in profile migration.

Memory tip: Think of the three things you need to move a user's "house" (profile): know who the user is (ActiveDirectory), physically access the old "house" (Hyper-V mounts the VHD), and pass the move-in inspection (Pester validates the result). The modules you might expect - RemoteDesktop and ServerManager - are for managing servers, not moving profiles.

No community discussion yet for this question.