Azure VNet Peering Configuration Quiz

1. Which Azure resource must exist in both VNets to enable peering?

Network Security Group

Virtual Network

Route table

Load balancer

2. In a hub-and-spoke VNet topology, how do spokes communicate with each other?

Direct peering between spokes

Through the hub with forwarded traffic enabled

Via VPN gateways only

They cannot communicate

3. What is required to troubleshoot peering connectivity issues?

Network Watcher and IP Flow Verify

Only Azure Portal

ExpressRoute diagnostics

VPN gateway logs

4. Does VNet peering incur charges for data transfer between peered VNets?

No, peering is always free

Yes, at standard data transfer rates

Only for global peering

Only for cross-subscription peering

5. Which peering state indicates a successful bidirectional peering connection?

Initiated

Connected

Peered

Active

6. What is the primary use case for 'Allow forwarded traffic' in VNet peering?

Connecting hub-and-spoke VNet topologies

Encrypting peering traffic

Reducing latency

Improving DNS resolution

7. Can you peer a VNet with overlapping address spaces?

Yes, overlapping is allowed

No, address spaces must be unique

Only if using NAT

Only in the same region

8. In peering, which setting allows a VNet to use a remote VNet's gateway?

Allow gateway transit

Use remote gateways

Allow forwarded traffic

Enable transit routing

9. What is a key difference between regional and global VNet peering?

Global peering has higher costs

Regional peering requires a gateway

Global peering connects VNets across regions

Regional peering supports more connections

10. How does traffic routing work in VNet peering by default?

Manual route configuration required

Automatic via system routes

Only through VPN gateways

Via Azure Firewall only

11. What is the primary benefit of VNet peering over VPN gateways?

Lower latency and higher bandwidth

Encryption of all traffic by default

Support for on-premises connectivity only

Automatic DNS resolution across regions

12. What is the latency typically associated with VNet peering?

10-50 ms

1-5 ms

100+ ms

Depends on VPN gateway capacity

13. Can VNet peering be configured between VNets in different Azure subscriptions?

No, same subscription is required

Yes, if both subscriptions are in the same tenant

Yes, but only in the same region

No, cross-subscription peering is not supported

14. In VNet peering, what is the role of the Network Watcher?

Establish the peering connection

Monitor and troubleshoot peering connectivity

Encrypt traffic between VNets

Manage IP address allocation

15. What does the 'Allow forwarded traffic' setting enable in VNet peering?

Traffic from non-peered VNets to pass through the peered VNet

Automatic routing between peered VNets

Encryption of peered traffic

DNS name resolution across VNets

16. Which setting must be enabled to allow VMs in a peered VNet to communicate with on-premises resources via a VPN gateway?

Allow gateway transit

Allow forwarded traffic

Use remote gateways

Enable transit peering

17. By default, does VNet peering allow traffic from peered VNets to reach on-premises networks?

Yes, automatically

No, unless a gateway is configured

Only with ExpressRoute

Only in the same region

18. What is the maximum number of peering connections a single VNet can have?

10

50

500

Unlimited

19. When establishing VNet peering, which of the following must be unique?

Address space of both VNets

Resource group names

Region location

Subnet names

20. Which peering type allows connectivity between VNets in different Azure regions?

Local peering

Global peering

Regional peering

Cross-subscription peering

Azure Network Engineer VNet Peering Configuration Quiz