Note: This question is part of a series of questions that present the same scenario. Each questions in the series
contains a unique solution that might meet the stated goals. Some questions 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 create an Ubuntu Linux virtual machine (VM) by using the Azure Portal. You do not specify a password
when you create the VM.
You need to connect to the terminal of the VM.
Solution: You connect to the private IP address of the VM by using Secure Shell (SSH) and specify your public
key.
Does the solution meet the goal?
A.
Yes
B.
No
Explanation:
You need to connect to the public IP, not the private IP.
wrong.
you connect to your private ip
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ssh-from-windows
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/create-ssh-keys-detailed
never mind it’s public
yeah wouldn’t really make much sense for your machine to be presenting your private key to anyone who attempts to connect.
And you should use your private key, not public
Right.
I guess because the question doesn’t discuss you having ExpressRoute and Peering configured – the privateIP is non-addressable external of the vNET
To *connect* to the VM you created you need:
Your private key (your public key is used during VM creation)
The public IP address (the connection string from the “connect” link, or the .cloudapp.azure.com DNS name for the VM)