You have an Azure subscription named Subscription1. Subscription1 contains a virtual machine named VM1. You have a computer Computer1 that runs Windows
10. Computer1 is connected to the Internet.
You add a network interface named Interface1 to VM1 as shown in the exhibit. (Click the Exhibit tab.)
From Computer1, you attempt to connect to VM1 by using Remote Desktop, but the connection fails.
You need to establish a Remote Desktop connection to VM1.
What should you do first?
To establish a Remote Desktop connection to VM1, you must ensure that the virtual machine is running. If VM1 is not started, it will not accept any incoming connections, including those for Remote Desktop. Therefore, the first step is to start VM1. The network security rule for port 3389 (used for Remote Desktop) is already set to allow inbound connections, so the primary action required in this scenario is to make sure VM1 is operational.
Answer is correct, but explanation is not. When VM has a dynamic, public IP address and is deallocated (stopped), IP is returned to the pool and instead of seeing the IP in 'networking', you see the publicIP name instead.
Also agree that answer is correct, but explanation is wrong. In particular the exclamation mark does not indicate any problem. In my experience this indicate a security risk to a common port being opened to the public. It is not an indication that VM need to be started
You cannot delate DenyAllOutBound or DenyAllInBound rules. They are Azure default rules.
Correct answer but not explanation
If it's not turned on you can't connect to it can you? B is the answer