An enterprise is designing the network routing topology for an Azure environment. The topology includes the following components:
- A hub virtual network named `vnet-hub-cus` () containing an Azure Firewall with the private IP address and an ExpressRoute virtual network gateway.
- A production spoke virtual network named `vnet-prod-spoke` () with a subnet named `snet-prod-app` ().
- A shared services spoke virtual network named `vnet-shared-spoke` () with a subnet named `snet-shared-db` ().
The virtual networks `vnet-prod-spoke` and `vnet-shared-spoke` are peered directly with `vnet-hub-cus` but are not peered with each other.
The design must meet the following requirements:
- All traffic between `snet-prod-app` and `snet-shared-db` must be routed through the Azure Firewall for inspection.
- Virtual machines in `snet-prod-app` must be able to communicate with the on-premises network () via the ExpressRoute gateway.
- Traffic between virtual machines within the same subnet (`snet-prod-app`) must remain local and bypass the Azure Firewall.
Which TWO configurations should you implement to meet these requirements?
- In the route table associated with the `snet-prod-app` subnet, add a route for with the next hop set to the Virtual Appliance IP address .Cevap
- Configure the virtual network peering between `vnet-hub-cus` and `vnet-prod-spoke` to enable gateway transit on the hub virtual network and use the remote virtual network's gateway on the spoke virtual network.Cevap
- CIn the route table associated with the `snet-prod-app` subnet, add a route for with the next hop set to the Virtual Appliance IP address .
- DIn the route table associated with the `snet-prod-app` subnet, add a route for with the next hop set to the Virtual Appliance IP address , and disable gateway route propagation.