AZ-700 Question 122
Single answerContoso, Inc. needs a private, high-bandwidth connection directly from their on-premises data centers to Azure. Their traffic demands exceed 10 Gbps, and they require a physical cross-connect to Microsoft for increased security and performance. Which ExpressRoute connectivity model best fits Contoso� requirements?
- A
A. ExpressRoute via a Connectivity Provider
- B
B. ExpressRoute Direct
- C
C. ExpressRoute Local
- D
D. ExpressRoute Global Reach
Show answer and explanation
Correct answer: B
Explanation
ExpressRoute Direct is designed for scenarios requiring large bandwidth and a physical cross-connect to Microsoft� enterprise edge, typically at 10 Gbps or more. It offers full control and a dedicated private connection, which meets Contoso� specific requirements for high-performance, secure connectivity. As outlined in Microsoft� ExpressRoute documentation, organizations with substantial traffic demands or specialized security and performance needs often select ExpressRoute Direct for direct and dedicated connections.
- A. Incorrect.
A. ExpressRoute via a Connectivity Provider � Incorrect. This option relies on a service provider� network to reach Azure. While it� suitable for most common use cases, it doesn�t provide a dedicated physical cross-connect to Microsoft at 10 Gbps or higher levels of capacity, which is specifically required by Contoso.
- B. Correct.
B. ExpressRoute Direct � Correct. This model provides a direct physical cross-connect at supported peering locations, enabling dedicated high-capacity circuits (10 Gbps or more) directly to Microsoft. It matches Contoso� need for high performance and secure connectivity.
- C. Incorrect.
C. ExpressRoute Local � Incorrect. ExpressRoute Local offers discounted data transfer rates within a single Azure region and is typically chosen to optimize costs within a localized deployment. It does not address the requirement for 10+ Gbps capacity and a dedicated cross-connect.
- D. Incorrect.
D. ExpressRoute Global Reach � Incorrect. Global Reach extends on-premises connections by allowing ExpressRoute circuits to connect to each other through Microsoft� network. This is beneficial for interconnecting branches but does not fulfill the requirement for a dedicated, high-bandwidth cross-connect for Azure directly.