AZ-700 Question 134
Select 2A company has an existing ExpressRoute circuit with private peering configured. They want to connect to Microsoft 365 services using Microsoft peering while limiting the Microsoft public prefixes they receive to those required for Microsoft 365. You are tasked with setting up Microsoft peering and ensuring that only the relevant BGP communities for the desired services are advertised. Which two actions should you perform to correctly configure Microsoft peering in this scenario?
- A
Enable Microsoft peering on the existing ExpressRoute circuit and associate it with a route filter that is configured with the required BGP communities for Microsoft 365
- B
Use a single route filter for both private peering and Microsoft peering to streamline the advertisement of routes for all services
- C
Create a separate route filter for Microsoft services and select the appropriate service communities, then link that route filter to the ExpressRoute circuit
- D
Enable Microsoft peering on the private peering configuration, ensuring all existing route tables merge automatically with the new route filter
Show answer and explanation
Correct answers: A, C
Explanation
When setting up Microsoft peering, you must create and enable a route filter containing the BGP communities specific to the desired Microsoft services (for example, Microsoft 365). This route filter is associated with the ExpressRoute circuit under the Microsoft peering configuration. Configuring a separate route filter for the Microsoft peering is critical to limit the prefixes received and prevent unintended traffic exposure. For more details, refer to the official Microsoft documentation on ExpressRoute and Microsoft peering at https://learn.microsoft.com/azure/expressroute/how-to-routefilter-microsoft-peering-portal.
- A. Correct.
Correct. You must enable Microsoft peering and link the circuit to a route filter specifying only the BGP communities necessary for Microsoft 365. This ensures that only relevant prefixes are exchanged over Microsoft peering.
- B. Incorrect.
Incorrect. Private peering and Microsoft peering are different. You typically need a separate route filter for Microsoft peering to avoid advertising all routes or receiving unwanted public prefixes for other services.
- C. Correct.
Correct. Creating a dedicated route filter for Microsoft services allows you to pick appropriate communities (for example, for Microsoft 365) and link that filter to the ExpressRoute circuit. This ensures you only exchange prefixes required by those services.
- D. Incorrect.
Incorrect. Microsoft peering settings must be configured separately from private peering. You cannot simply enable Microsoft peering on the private peering configuration; a separate peering configuration is required to selectively receive Microsoft public prefixes.