AZ-700 Virtual Networks and Peering 1 — Questions and Answers
Question 1: What is the maximum number of virtual networks you can peer with a single Azure VNet by default?
- 100
- 200
- 500 (Correct answer)
- 50
Correct answer: 500
Azure VNet peering supports up to 500 peerings per virtual network by default.
Question 2: Which VNet peering type connects virtual networks in different Azure regions?
- Local VNet peering
- Global VNet peering (Correct answer)
- Cross-region peering
- Remote peering
Correct answer: Global VNet peering
Global VNet peering connects virtual networks across different Azure regions.
Question 3: When configuring VNet peering, which setting must be enabled to allow traffic from a peered network to use the local VNet's gateway?
- Allow forwarded traffic
- Use remote gateways
- Allow gateway transit (Correct answer)
- Allow virtual network access
Correct answer: Allow gateway transit
'Allow gateway transit' must be enabled on the hub VNet so spoke VNets can use its gateway.
Question 4: What address space overlap rule applies to Azure VNet peering?
- Overlapping address spaces are allowed with NAT
- Address spaces must not overlap (Correct answer)
- Only the first /24 must be unique
- Overlap is allowed for global peering only
Correct answer: Address spaces must not overlap
VNet peering requires that the address spaces of the peered VNets do not overlap.
Question 5: In a hub-spoke VNet topology, which component typically resides in the hub VNet?
- Application workloads
- Shared services like VPN Gateway and Azure Firewall (Correct answer)
- Individual department subnets
- Storage accounts
Correct answer: Shared services like VPN Gateway and Azure Firewall
Shared services such as VPN Gateway, Azure Firewall, and DNS reside in the hub VNet in a hub-spoke topology.
Question 6: Which Azure feature allows you to use a VNet in one subscription peered to a VNet in a different subscription?
- Cross-subscription VNet peering (Correct answer)
- VNet-to-VNet VPN
- Azure Private Link
- Azure Relay
Correct answer: Cross-subscription VNet peering
Cross-subscription VNet peering allows peering VNets across different Azure subscriptions using resource IDs.
What is the maximum number of virtual networks you can peer with a single Azure VNet by default?