An enterprise is designing a regional application architecture in the East US region. The application consists of two tiers:
- A web tier hosted on Azure Virtual Machines that requires SSL/TLS termination, URL path-based routing, and HTTP/S load balancing.
- A database tier hosted on Azure Virtual Machines that requires internal TCP load balancing.
All virtual machines in the database tier currently have Basic SKU Public IP addresses assigned.
You need to recommend the load balancing services and the required configuration changes to support this architecture. Which two actions should you recommend?
- Deploy Azure Application Gateway to load balance the web tier.Cevap
- Deploy a Standard Azure Load Balancer to load balance the database tier, and upgrade the database virtual machines' Public IP addresses to Standard SKU.Cevap
- CDeploy Azure Traffic Manager to load balance the web tier and perform SSL/TLS termination.
- DDeploy a Standard Azure Load Balancer to load balance the database tier, and retain the Basic SKU Public IP addresses on the database virtual machines.
- EDeploy a Basic Azure Load Balancer to load balance the database tier, and assign Standard SKU Public IP addresses to the database virtual machines.
Cevap
To support this architecture, you should deploy Azure Application Gateway to load balance the web tier, and deploy a Standard Azure Load Balancer to load balance the database tier while upgrading the database virtual machines' Public IP addresses to Standard SKU.
Deploying Azure Application Gateway satisfies the Layer 7 requirements (SSL/TLS termination and URL path-based routing) for the web tier. Deploying a Standard Azure Load Balancer meets the database tier's Layer 4 TCP load balancing needs, and upgrading the virtual machines' Public IPs to the Standard SKU ensures SKU compatibility and avoids validation errors.
Adım Adım Çözüm
Anahtar Kavram
Choosing load balancing services based on OSI layer capabilities and ensuring matching resource SKUs to avoid validation errors.