FCP_ZCS_AD-7-4 practice question 2 of 10

What characterizes the branch-to-branch topology in an Azure virtual WAN?

Full set: 35 questions
Answer options
A: Increased redundancy through multiple connections to the central hub
B: Enhanced security through centralized traffic management
C: Simplified network architecture with reduced hub dependencies
D: Improved scalability for branch offices connecting to Azure Correct answer
Correct Answer:
D. Improved scalability for branch offices connecting to Azure
Explanation

In Azure Virtual WAN, enabling branch-to-branch connectivity lets every site build only a single VPN/ExpressRoute link to its regional Virtual WAN hub. Azure then automatically provides any-to-any traffic flow across Microsoft’s backbone, so additional branches can be on-boarded without creating new peerings or tunnels between existing sites. This managed, cloud-transit model therefore chiefly distinguishes itself by giving very large and rapidly growing branch footprints the ability to scale simply and quickly.

Why Incorrect

A. Concerns hub redundancy; branch-to-branch is about inter-site scale, not multiple hub links.
B. Centralized security (e.g., Azure Firewall) is a hub feature, not the defining trait of branch-to-branch.
C. Architecture is simplified, but reliance on hubs is not reduced—traffic still transits the hub, so statement is inaccurate.

References

1. Microsoft Learn – “About Azure Virtual WAN,” section “Branch-to-branch traffic flows”

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

2. Microsoft Learn – “Azure Virtual WAN design considerations,” subsection “Scalability benefits of branch-to-branch connectivity”

https://learn.microsoft.com/en-us/azure/virtual-wan/design-guide#branch-to-branch-scalability

Scroll to Top