Examkin

Soru

Zorluk: OrtaDesign Traffic Routing and Failover Strategies

An enterprise is designing a disaster recovery and business continuity solution for a web application deployed across the East US and West US regions. The application consists of an HTTPS-based frontend and an Azure SQL Database backend.

The architecture must meet the following requirements:
- Automatically route client requests to the region with the lowest latency.
- Offload SSL/TLS decryption from the backend web servers to a centralized global entry point.
- Provide automatic failover for the database layer with a single connection string that automatically redirects write operations to the new primary server.
- Ensure that the primary web application can survive a regional outage with minimal manual intervention.

Which design should you recommend?

  1. A
    Deploy Azure Traffic Manager for global routing and SSL termination, and configure Azure SQL Database active geo-replication with manual failover.
  2. Deploy Azure Front Door for global routing and SSL termination, and configure Azure SQL Database auto-failover groups.Cevap
  3. C
    Deploy Azure Front Door for global routing and SSL termination, and configure Read-Access Geo-Redundant Storage (RA-GRS) to support active-active database writes in both regions.
  4. D
    Deploy Azure Traffic Manager for global routing, configure an Azure Application Gateway in each region to perform SSL termination, and configure Azure SQL Database active geo-replication.

Cevap

Deploy Azure Front Door for global routing and SSL termination, and configure Azure SQL Database auto-failover groups.
The correct architecture uses Azure Front Door at the ingress layer to provide global Anycast routing, lowest-latency path optimization, and centralized SSL termination. For the data layer, it uses Azure SQL Database auto-failover groups to automate database failover and present a single read-write endpoint, eliminating the need to update database connection strings in the web app during a failover event.

Adım Adım Çözüm

1
Analyze global routing and SSL termination requirements.
Identify that Azure Front Door is an Anycast-based routing service that operates at Layer 7, allowing it to perform centralized SSL/TLS termination and route HTTP/S requests with minimal failover latency. In contrast, Azure Traffic Manager works at the DNS level (Layer 4) and cannot decrypt or terminate SSL traffic.
This determines the correct ingress and routing service for HTTP-based workloads needing SSL offloading.
2
Analyze database HA/DR and listener requirements.
Select Azure SQL Database auto-failover groups because they provide a read-write listener endpoint (a single connection string) and automate the failover process to the secondary region. In contrast, active geo-replication requires manual initiation of failover and client-side connection string changes, while RA-GRS is a storage redundancy option that is read-only in the secondary region.
This satisfies the requirement for automatic database failover with a single connection string.
3
Synthesize the components into a single architecture.
Combine Azure Front Door and Azure SQL Database auto-failover groups to form a complete, automated end-to-end failover solution for the global application.
This guarantees that both front-end and back-end layers meet the high-availability and business continuity requirements.

Anahtar Kavram

Design Traffic Routing and Failover Strategies
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru