nerdexam
Microsoft

AZ-104 · Question #680

Hotspot Question You have an Azure subscription that contains the virtual networks shown in the following table. The subscription contains the virtual machines shown in the following table. Each…

The correct answer is The Remote Desktop Connection client (mstsc.exe) can be used to connect to VM1 through Bastion1. = No; The Azure portal can use SSH to connect to VM2 through Bastion1. = Yes; The Azure portal can be used to connect to VM3 through Bastion1. = No. Azure Bastion is a browser-based service that provides secure RDP/SSH connectivity directly through the Azure portal - it does NOT support the native Remote Desktop Connection client (mstsc.exe) in the Basic/Standard tier without the native client feature explicitly enabled…

Submitted by kev92· Mar 4, 2026Configure and manage virtual networking - specifically secure remote access using Azure Bastion across virtual network topologies (AZ-104: Implement and Manage Virtual Networking)

Question

Hotspot Question You have an Azure subscription that contains the virtual networks shown in the following table. The subscription contains the virtual machines shown in the following table. Each virtual machine contains only a private IP address. You create an Azure bastion for VNet1 as shown in the following exhibit. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Answer:

Exhibits

AZ-104 question #680 exhibit 1
AZ-104 question #680 exhibit 2
AZ-104 question #680 exhibit 3
AZ-104 question #680 exhibit 4
AZ-104 question #680 exhibit 5
AZ-104 question #680 exhibit 6

Answer Area

  • The Remote Desktop Connection client (mstsc.exe) can be used to connect to VM1 through Bastion1.No
  • The Azure portal can use SSH to connect to VM2 through Bastion1.Yes
  • The Azure portal can be used to connect to VM3 through Bastion1.No

Explanation

Azure Bastion is a browser-based service that provides secure RDP/SSH connectivity directly through the Azure portal - it does NOT support the native Remote Desktop Connection client (mstsc.exe) in the Basic/Standard tier without the native client feature explicitly enabled. VM2 is a Linux VM on VNet1 (or a peered VNet), so the Azure portal can use SSH through Bastion1 to connect to it. VM3 resides on VNet3, which is not peered with VNet1 where Bastion1 is deployed, so Bastion1 cannot reach VM3 - Bastion only covers the VNet it is deployed in and directly peered VNets (with the correct SKU and peering settings).

Topics

#Azure Bastion#Virtual Network Peering#Remote Access#Network Security

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-104 Practice