SSH and RDP access in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you try to SSH into an Azure VM without opening port 22?

You have deployed a Linux VM in Azure. You try to connect using SSH but the connection times out. What is the most likely reason?

A The VM's public IP address is not assigned.

B The Network Security Group (NSG) does not allow inbound traffic on port 22.

C Azure blocks all SSH traffic by default for security reasons.

D The VM's operating system does not support SSH connections by default.

💡 Hint

Check the firewall rules controlling network traffic to the VM.

Azure VMs require that the Network Security Group allows inbound traffic on port 22 for SSH. Without this, the connection will time out.

❓ Configuration

intermediate

Which Azure CLI command opens RDP access on port 3389 for a Windows VM?

You want to allow RDP access to your Windows VM by opening port 3389 in the NSG. Which command correctly adds this rule?

A az vm open-port --name MyVM --resource-group MyGroup --port 22

B az network nsg rule create --nsg-name MyNSG --resource-group MyGroup --name AllowSSH --protocol Tcp --direction Inbound --priority 1000 --source-address-prefixes '*' --source-port-ranges '*' --destination-port-ranges 3389 --access Allow

C az network nsg rule create --nsg-name MyNSG --resource-group MyGroup --name AllowRDP --protocol Tcp --direction Inbound --priority 1000 --source-address-prefixes '*' --source-port-ranges '*' --destination-port-ranges 3389 --access Allow

D az vm open-port --name MyVM --resource-group MyGroup --port 80

💡 Hint

Look for the command that creates an NSG rule for port 3389 with the correct name and protocol.

Option C correctly creates an NSG rule named AllowRDP allowing inbound TCP traffic on port 3389, which is the default port for RDP.

❓ Architecture

advanced

Best practice for securing SSH access to Azure VMs

You want to secure SSH access to your Linux VMs in Azure. Which architecture approach is best to reduce exposure to the internet?

A Use a jump box VM with a public IP and allow SSH only from trusted IPs to the jump box, then SSH from jump box to other VMs on private network.

B Disable SSH and use only Azure portal serial console for access.

C Allow SSH from any IP address by opening port 22 in the NSG.

D Open port 22 to the internet but require complex passwords on the VM.

💡 Hint

Think about minimizing direct internet exposure of your VMs.

Using a jump box (bastion host) limits direct SSH exposure. Only the jump box has a public IP and strict access, improving security.

❓ security

advanced

What is the effect of enabling Azure Bastion for RDP and SSH access?

You enable Azure Bastion on your virtual network. What is the main effect on how you access your VMs?

A You must open port 3389 and 22 on NSGs to use Azure Bastion.

B Azure Bastion disables all RDP and SSH access to VMs.

C Azure Bastion requires installing additional software on your local machine.

D You can connect to VMs via RDP and SSH directly through the Azure portal without exposing public IPs or opening ports.

💡 Hint

Consider how Azure Bastion changes the connection method to VMs.

Azure Bastion provides secure RDP and SSH access via the Azure portal over SSL, without exposing public IPs or opening ports.

✅ Best Practice

expert

How to enforce multi-factor authentication (MFA) for SSH access to Azure Linux VMs?

You want to require MFA when users SSH into your Azure Linux VMs. Which approach achieves this?

A Configure Azure Active Directory (Azure AD) login for Linux VMs and enable Conditional Access policies requiring MFA.

B Open port 22 and require users to enter a second password during SSH login.

C Use SSH keys only and disable password authentication.

D Enable MFA on the VM's local user accounts.

💡 Hint

Think about integrating Azure identity services with VM login.

Azure AD login for Linux VMs allows using Azure identities and Conditional Access policies, including MFA, for SSH access.