An enterprise is designing a multi-region web application deployment across the East US and West US regions. The architecture must satisfy the following requirements:
- Route incoming traffic globally to the closest healthy region with SSL/TLS termination at the global edge.
- Perform URL-path routing (e.g., directing traffic under `/api/*` to dedicated API backends).
- Use regional load balancers to distribute traffic to Azure Virtual Machines in each region.
- The virtual machines currently have Basic SKU Public IP addresses assigned to their network interfaces.
Which two actions should you perform to meet these requirements and prevent validation failures? (Select two.)
- Deploy Azure Front Door to manage global traffic routing and Azure Application Gateway (Standard v2) in each region.Cevap
- Upgrade the Public IP addresses of the virtual machines to Standard SKU.Cevap
- CDeploy Azure Traffic Manager for global routing and SSL/TLS termination, and a Standard Load Balancer in each region.
- DAssociate the existing virtual machines directly with a regional Standard Load Balancer without altering their public IP configuration.
Cevap
Deploy Azure Front Door globally along with Azure Application Gateway in each region, and upgrade the virtual machines' public IP addresses to Standard SKU.
To satisfy the global routing and edge SSL/TLS termination requirements, Azure Front Door is the appropriate service because it operates at the global edge. To handle URL-path routing regionally, Azure Application Gateway (Standard v2) must be deployed in each region. Because these regional services utilize the Standard SKU, any public IP addresses associated with the backend virtual machines' network interfaces must be upgraded to the Standard SKU to avoid validation conflicts.
Adım Adım Çözüm
Anahtar Kavram
Azure Application Load Balancing and SKU Validation Constraints