QuestionQ173

VerifiedImplement and manage virtual networking

Scenario

You have an Azure subscription that contains the following resources:

  • A virtual network that has a subnet named Subnet1
  • Two network security groups (NSGs) named NSG-VM1 and NSG-Subnet1
  • A virtual machine named VM1 that has the required Windows Server configurations to allow Remote Desktop connections

NSG-Subnet1 has only the default inbound security rules.

NSG-VM1 has the default inbound security rules and the following custom inbound security rule:

  • Priority: 100
  • Source: Any
  • Source port range: *
  • Destination: *
  • Destination port range: 3389
  • Protocol: UDP
  • Action: Allow

VM1 has a public IP address and is connected to Subnet1. NSG-VM1 is associated with the network interface of VM1. NSG-Subnet1 is associated with Subnet1.

You need to be able to establish Remote Desktop connections from the internet to VM1.

Solution: You add an inbound security rule to NSG-Subnet1 that allows connections from the Internet source to the VirtualNetwork destination on port range 3389 and uses the UDP protocol.

Does this satisfy the goal?

Explanation

Remote Desktop Protocol (RDP) uses TCP port 3389 by default, not UDP. Although the proposed rule correctly targets port 3389 and the Internet-to-VirtualNetwork path, it specifies the UDP protocol instead of TCP. Since UDP 3389 is not the standard RDP protocol, the connection will not succeed. Additionally, NSG rules are evaluated by the 5-tuple (source, source port, destination, destination port, protocol), so UDP and TCP are completely distinct rules.

Community Discussion

No comments yet. Be the first to start the discussion!