HOTSPOT
-
You have an Azure subscription that contains the resources shown in the following table.
You establish BGP peering between NVA1 and Hub1.
You need to implement transit connectivity between VNet1 and VNet3 via Hub1 by using BGP peering. The solution must minimize costs.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
the given answer is correct refer to https://learn.microsoft.com/en-us/azure/virtual-wan/scenario-bgp-peering-hub
On Hub1, propagate routes from connections to VNet1 and VNet2 to: 1. A custom route table and associate the routes with the defaultRouteTable: Cost: Minimal. Custom route tables are free if you don't use peering policies. Associating with the default route table avoids managing a separate table for each VNet. 2. A custom route table and associate the routes with the same custom route table: Cost: Minimal. Similar to option 1, but creates a separate table for all routes. This introduces some management overhead but might be preferred if you need more granular control over routing in the future. 3. The defaultRouteTable and associate the routes with the defaultRouteTable: Cost: Potentially higher. Adding routes to the default route table might trigger Azure Virtual WAN charges for route aggregation if you have many networks connected to the hub.
Everything you need to know can be found in this section: https://learn.microsoft.com/en-us/azure/virtual-wan/scenario-bgp-peering-hub. An extract: The following steps are required when BGP peering isn't used on the virtual hub: Virtual hub configuration On the Hub 1's defaultRouteTable, configure static route for VNET5 (subnet 10.2.1.0/24) pointing to VNET2 connection. On Hub 1's virtual network connection for VNET2, configure static route for VNET5 pointing to VNET2 NVA IP (subnet 10.2.0.5). On Hub 1, propagate routes from connections for VNET1 and VNET2 to the defaultRouteTable, and associate them to the defaultRouteTable. Virtual network configuration On VNET5, set up a user-defined route (UDR) to point to VNET2 NVA IP.