Examkin

Soru

Zorluk: OrtaDesign Traffic Routing and Failover Strategies

An enterprise is designing a multi-region disaster recovery and business continuity solution for a web application deployed in the East US and West US regions. The application requirements include:

1. Global HTTPS traffic must be routed to the closest region with sub-minute failover detection, SSL/TLS termination, and path-based routing (e.g., routing `/api/*` requests to a specialized service).
2. The back-end relational database must support automatic failover to the secondary region without requiring connection string modifications in the application code.
3. Storage data must be replicated to the secondary region, but write operations are strictly restricted to the primary region until a failover occurs.

Which combination of Azure services and configurations should you recommend?

  1. Azure Front Door for global traffic routing; Azure SQL Database auto-failover groups; and Read-Access Geo-Redundant Storage (RA-GRS) with write operations directed only to the primary endpoint.Cevap
  2. B
    Azure Traffic Manager for global traffic routing; Azure SQL Database auto-failover groups; and Read-Access Geo-Redundant Storage (RA-GRS) with write operations directed only to the primary endpoint.
  3. C
    Azure Front Door for global traffic routing; Azure SQL Database active geo-replication with manual failover and separate regional connection strings; and Read-Access Geo-Redundant Storage (RA-GRS) with write operations directed only to the primary endpoint.
  4. D
    Azure Front Door for global traffic routing; Azure SQL Database auto-failover groups; and Read-Access Geo-Redundant Storage (RA-GRS) configured to allow active-active write operations to both regional endpoints simultaneously.

Cevap

Azure Front Door for global traffic routing; Azure SQL Database auto-failover groups; and Read-Access Geo-Redundant Storage (RA-GRS) with write operations directed only to the primary endpoint.
The correct architecture uses Azure Front Door for global Layer 7 routing (providing SSL termination and path-based routing), Azure SQL Database auto-failover groups (offering unified listener endpoints that prevent connection string updates), and RA-GRS with writes routed strictly to the primary endpoint.

Adım Adım Çözüm

1
Evaluate the global routing requirements.
Azure Front Door is selected because it operates at Layer 7 (HTTP/HTTPS) and natively supports Anycast routing, SSL/TLS termination, path-based routing rules, and sub-minute failovers using health probes. Azure Traffic Manager is ruled out since it operates at the DNS level and cannot perform SSL termination or inspect URL paths.
We must satisfy the requirement for global traffic routing, SSL termination, and path-based routing (/api/*).
2
Evaluate the database auto-failover requirements.
Azure SQL Database auto-failover groups are selected because they provide read-write and read-only listener endpoints that remain constant during a failover, eliminating the need to update application connection strings. Manual active geo-replication is ruled out because it lacks a unified listener endpoint.
We must satisfy the requirement to fail over without modifying connection strings in the application code.
3
Evaluate the storage replication and write constraints.
RA-GRS is selected with writes directed to the primary endpoint. RA-GRS provides read-only access to the secondary endpoint while keeping the primary writeable, satisfying the requirement. Attempting an active-active write configuration on RA-GRS is invalid.
We must verify that replication is geo-redundant and that writes are restricted to the primary region.

Anahtar Kavram

Designing multi-region architectures using Azure Front Door for Layer 7 global traffic routing and Azure SQL Auto-failover groups for database business continuity.
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru