Adding Server2 to an AVD Host Pool: Which Two Actions?
You have an Azure Virtual Desktop deployment that contains a host pool named Pool1. Pool1 contains two session hosts. You build a custom virtual machine named Server2 that runs Windows Server. You need to add Server2 to Pool1. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Votes
62% of anonymous learners picked answer DE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the manual session-host registration sequence for a custom VM and traps candidates who confuse the AVD agent/token steps with Azure Arc's Connected Machine agent requirement.
Adding an existing Windows Server VM to an Azure Virtual Desktop host pool requires two manual steps: install the Remote Desktop Services Infrastructure Agent and provide a host pool registration token. The correct answer is D and E, not the Azure Connected Machine agent.
Many candidates choose B and D because they see 'custom virtual machine' and assume Azure Arc is required; however, the Azure Connected Machine agent is for Azure Local/Arc-enabled hosts, while standard AVD registration needs the RDS Infrastructure Agent plus the host pool registration token.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The question asks how to add an already-built Windows Server VM named Server2 to an existing AVD host pool named Pool1. In Azure Virtual Desktop, an existing or custom VM does not automatically become a session host; you must install the AVD agent components and register it. Option E covers installing the Remote Desktop Services Infrastructure Agent, which is the AVD agent component that lets the VM communicate with the AVD service. Option D covers providing the host pool registration token, which authenticates Server2 and associates it with Pool1. Both actions are required, and together they match the documented manual registration flow for joining a VM to an existing host pool.
Why the Other Options Are Wrong
Option A (Remote Desktop Connection Broker role) belongs to a traditional on-premises RDS deployment, not Azure Virtual Desktop. Option C (New-AzWvdHostPool) would create a brand-new host pool, but the scenario states that Pool1 already exists and only Server2 needs to be added. Option B (Azure Connected Machine agent) is the main distractor: it is needed for Azure Arc-enabled servers or Azure Local session hosts, not for a standard Windows Server VM being registered directly to an AVD host pool. Because the question never mentions Azure Local or Arc-enabled infrastructure, B is out of scope here.
Community Comment Notes
jeff1988 states that the registration token (D) is necessary to register the new session host and that the RDS Infrastructure Agent (E) is required for it to function in AVD. Hotwired34 points to the Microsoft Learn "Add session hosts to a host pool" page and highlights the RDAgent installer step plus "Enter registration token." Others such as soysoliscarlos and db7a78f prefer B and D, but their rationale centers on Azure Local prerequisites; bruce notes that Azure Local adds the Connected Machine agent requirement, which is not the case in this question. The DE consensus aligns with the standard AVD registration procedure.
Official Reference
Exam Strategy
When an AVD question asks how to add a custom or existing VM to a host pool, distinguish standard Azure AVD registration from Azure Local or Azure Arc scenarios. If the scenario does not mention Azure Local, Arc-enabled servers, or Azure Stack HCI, rule out the Azure Connected Machine agent and focus on the AVD agent plus registration token.
Frequently Asked Questions
Why isn't the Azure Connected Machine agent (B) required to add Server2 to Pool1?
Option B applies to Azure Arc-enabled servers or Azure Local session hosts. A standard Windows Server VM added to an AVD host pool needs the AVD agent and a host pool registration token.
Why is New-AzWvdHostPool (C) wrong for Server2?
New-AzWvdHostPool creates a new host pool, but Pool1 already exists. Adding Server2 requires registering it as a session host, not provisioning another host pool.
Related Analysis
Practice All AZ-140 Questions
Access 64 questions with complete answers and detailed explanations.
View Full AZ-140 Practice Test →