A financial services firm is modernizing its payment processing platform by migrating key workloads to Azure. The architecture team is designing a load balancing and traffic delivery solution that must meet the following requirements:
* External client transactions over HTTPS must be routed globally to regional endpoints using path-based rules (e.g., routing `/process` and `/refund` requests to dedicated backend services) with SSL/TLS termination performed at the edge.
* The internal backend database tier, which communicates over TCP port , must be load-balanced regionally across virtual machines in a virtual network.
* The database virtual machines currently have legacy Basic SKU Public IP addresses assigned for administrative access.
* The solution must support high-availability configurations for all load balancers without validation or deployment failures.
Which architecture configuration should you recommend to meet these requirements?
- ADeploy Azure Traffic Manager to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.
- Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.Answer
- CDeploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic, keeping the database virtual machines' public IP addresses on the Basic SKU.
- DDeploy Azure Application Gateway to manage global HTTP/S routing and SSL/TLS termination. Deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic, keeping the database virtual machines' public IP addresses on the Basic SKU.