Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
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 the default inbound security rules only.
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 connects to Subnet1. NSG1-VM1 is associated to the network interface of VM1. NSGSubnet1 is associated to Subnet1.
You need to be able to establish Remote Desktop connections from the internet to VM1.
Solution: You modify the custom rule for NSG-VM1 to use the internet as a source and TCP as a protocol.
Does this meet the goal?
A . Yes
B . No
Answer: A
Explanation:
The default port for RDP is TCP port 3389. A rule to permit RDP traffic must be created automatically when you create your VM.
Note on NSG-Subnet1: Azure routes network traffic between all subnets in a virtual network, by default.
References: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-rdpconnection