An enterprise is designing a hub-and-spoke virtual network topology in Azure. The transit hub virtual network, `vnet-hub-transit` (), contains a firewall subnet, `AzureFirewallSubnet` (), hosting an Azure Firewall with a private IP address of . The application virtual network, `vnet-spoke-app` (), is peered with `vnet-hub-transit` and contains two subnets: `snet-web` () and `snet-biz` (). Another virtual network, `vnet-spoke-db` (), contains the database tier and is also peered with `vnet-hub-transit`.
You need to configure a route table associated with `snet-web`. The routing configuration must meet the following requirements:
- Route all outbound internet traffic from `snet-web` through the Azure Firewall.
- Route all database-bound traffic from `snet-web` to `vnet-spoke-db` through the Azure Firewall.
- Ensure that VMs within `snet-web` can communicate directly with VMs in `snet-biz` without routing traffic through the firewall.
Which route configuration should you apply to the route table associated with `snet-web`?
- AA route for pointing to the virtual appliance at , and a route for pointing to the virtual appliance at .
- BA route for pointing to the virtual appliance at , and separate route table entries mapping individual IP addresses for all external Azure dependencies instead of utilizing the `AzureCloud` Service Tag in the route table.
- A route for pointing to the virtual appliance at , and a route for pointing to the virtual appliance at .Cevap
- DA route for pointing to the virtual appliance at , and deploying an Azure Traffic Manager profile configured with path-based routing to terminate and forward HTTP traffic from the web tier to the database tier.