Which statement correctly describes the connectivity scope of Azure VNet peering?
Think about how Azure connects virtual networks internally without extra devices.
Azure VNet peering connects virtual networks directly, even across regions, without needing gateways or routing traffic over the internet.
You have two VNets in different Azure regions that must communicate with low latency and high bandwidth. Which design choice best supports this?
Consider Azure's native features for private, fast network connections.
VNet peering across regions provides low latency and high bandwidth by connecting VNets directly within Azure's backbone network.
After peering two VNets, which security consideration is true?
Think about how Azure controls traffic flow between networks.
NSGs apply to each VNet independently; peering does not merge or share NSG rules automatically. You must configure NSGs on each side to control traffic.
You have three VNets: VNet1 peered with VNet2, and VNet2 peered with VNet3. Which statement about routing is true?
Consider how Azure handles routing between peered VNets.
Azure VNet peering does not support transitive routing. Each VNet must be peered directly to communicate.
In a large Azure environment with many VNets, what is the best practice to simplify and secure VNet peering management?
Think about how to reduce complexity and improve security in network design.
Hub-and-spoke reduces the number of peerings needed and centralizes control, improving manageability and security.