Virtual networking

Azure Virtual Network peering connects VNets privately using Microsoft's backbone network, delivering high-bandwidth and low-latency connections without exposing traffic to the public internet. Option A is incorrect because peered traffic never traverses the public internet. Option C is also wrong because global peering allows connection across different Azure regions.

Azure Bastion provides secure, seamless RDP and SSH connectivity to virtual machines directly through the Azure portal over SSL, eliminating the need for public IP addresses on the VMs. Distractors like Option A and C are incorrect because Bastion is strictly an administrative access tool, not a load balancer or auto-scaling service.

Network Security Groups act as stateful packet-filtering firewalls operating at Layers 3 and 4 of the OSI model to filter inbound and outbound virtual network traffic. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.

• !Option A is incorrect because peered traffic never traverses the public internet.
• !Distractors like Option A and C are incorrect because Bastion is strictly an administrative access tool, not a load balancer or auto-scaling service.
• !It cannot span multiple VNets or be global, which makes those options incorrect.

Answer each from memory — you'll see instantly whether you're right and why.

Run a focused 10-question mini-mock on Virtual networking and see it stick.