You have an Azure virtual machine named VM1 Ilia! has a private IP address only. You configure the Windows Admin Center extension on VM1. You have an on-premises computer that runs Windows 11. You…

Question

Options

• Aan Azure Bastion host on the virtual network that contains VM1.
• Ba VPN connection to the virtual network that contains VM1.
• Ca network security group 1NSG) rule that allows inbound traffic on port 443.
• Da private endpoint on the virtual network that contains VM1.

• A
  3% (1)
• B
  68% (21)
• C
  10% (3)
• D
  19% (6)

Explanation

VM1 has only a private IP address, meaning it is not reachable from the public internet. The Windows Admin Center extension in the Azure portal communicates with the VM over its private IP using HTTPS (port 443). For the Azure portal to reach this private IP on behalf of the administrator, network connectivity must exist between the portal's backend and the VNet - but more importantly, for the on-premises computer running the management session, a VPN connection to the virtual network provides routable access to VM1's private IP so WAC can function. Azure Bastion (A) provides browser-based RDP/SSH, not WAC access. An NSG rule (C) alone cannot create routing from the internet to a private IP. A private endpoint (D) exposes Azure PaaS services privately and is not applicable to managing a VM via WAC.

No community discussion yet for this question.