An enterprise is designing a global disaster recovery and traffic routing solution for a hybrid workload deployed across the East US and West US regions. The workload consists of two primary services:
1. A web application API running on HTTPS that requires Web Application Firewall (WAF) protection, URL path-based routing (routing `/static/*` to storage and `/api/*` to compute), and SSL/TLS termination at the edge.
2. A latency-sensitive database replication daemon communicating over custom TCP port . The database clients have a legacy configuration that hardcodes or aggressively caches DNS query results, ignoring any DNS Time to Live (TTL) values.
Which two routing and load balancing strategies should you implement to satisfy the requirements for both services?
- Deploy Azure Front Door for the HTTPS web API to handle SSL/TLS termination, path-based routing, and WAF protection at the global edge.Cevap
- Deploy an Azure Cross-Region Load Balancer (Global Tier) to expose a single static Anycast IP address for routing the custom TCP port traffic.Cevap
- CDeploy Azure Traffic Manager for the HTTPS web API to route client requests using the performance routing method and offload SSL/TLS decryption.
- DDeploy Azure Traffic Manager for the TCP database replication daemon to perform DNS-based failover with a -second DNS TTL.
- EConfigure the database tier to replicate write operations using Read-Access Geo-Redundant Storage (RA-GRS) to allow simultaneous database writes in both East US and West US.