Examkin

Soru

Zorluk: ZorDesign Traffic Routing and Failover Strategies

A global retail corporation is deploying a new order processing system across the East US and West Europe Azure regions. The architecture contains two workloads:

1. An admin dashboard: A web application (HTTPS) that requires SSL termination at the edge, path-based routing (routing `/reports/*` to a specialized backend pool), and protection from SQL injection attacks.
2. A legacy sync agent: A client application that synchronizes local inventory databases using a custom TCP protocol over port 9090.

Both workloads must be highly available with automatic failover between regions.

Which routing design should you recommend to meet these requirements?

  1. A
    Deploy Azure Traffic Manager to route traffic for both the admin dashboard and the legacy sync agent, configuring DNS-based routing with active-active failover.
  2. Deploy Azure Front Door to route traffic for the admin dashboard, and deploy Azure Traffic Manager to route traffic for the legacy sync agent.Cevap
  3. C
    Deploy Azure Front Door to route traffic for both the admin dashboard and the legacy sync agent, configuring custom routing rules to bypass HTTPS inspection for the port 9090 traffic.
  4. D
    Deploy a cross-region Azure Load Balancer to route traffic for both workloads, utilizing standard load balancing rules to forward port 443 and port 9090 traffic.

Cevap

Deploy Azure Front Door to route traffic for the admin dashboard, and deploy Azure Traffic Manager to route traffic for the legacy sync agent.
Deploying Azure Front Door for the admin dashboard and Azure Traffic Manager for the legacy sync agent is correct. Azure Front Door is an Anycast-based Layer 7 service providing SSL termination, path-based routing, and WAF features for the HTTPS admin dashboard. Since Front Door does not support custom TCP protocols, Azure Traffic Manager (which functions at the DNS level and is protocol-agnostic) is used to provide DNS-based routing and regional failover for the legacy sync agent on port 9090.

Adım Adım Çözüm

1
Analyze the protocol and feature requirements for the admin dashboard workload.
The workload uses HTTPS and needs SSL offloading at the edge, path-based routing, and WAF protection.
These requirements necessitate a global Layer 7 load balancer with application security integration, which points to Azure Front Door.
2
Analyze the protocol and port requirements for the legacy sync agent workload.
The legacy workload uses a custom TCP protocol over port 9090.
Because it uses a custom TCP protocol (non-HTTP) on an arbitrary port, Azure Front Door cannot be used. A DNS-based or Layer 4 global routing solution is required.
3
Evaluate combined traffic routing options to ensure all requirements and regional failover are met.
Select Azure Front Door for the HTTPS admin dashboard and Azure Traffic Manager for the legacy custom TCP agent.
This separation aligns each workload with a service that supports its protocols and required features, while providing robust cross-region failover capability.

Anahtar Kavram

Azure Front Door is a global Layer 7 load balancer that handles HTTP/HTTPS traffic with features like SSL offloading and WAF. Azure Traffic Manager is a DNS-based load balancer that operates at the DNS layer and is protocol-agnostic, making it ideal for non-HTTP/HTTPS protocols like custom TCP.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru