A healthcare provider is redesigning the network architecture for a patient portal application hosted on Azure Virtual Machines in the East US region. The portal requires:
* Path-based routing to direct /imaging/* request traffic to a dedicated backend pool.
* SSL/TLS termination at the load balancing tier.
* High-availability load balancing for a backend database tier using TCP port 1433.
The Virtual Machines currently have Basic SKU Public IP addresses assigned to their Network Interface Cards (NICs) for direct administrative access. You need to design the regional load balancing solution while ensuring compatibility across all tiers.
Which TWO actions should you recommend? (Select TWO)
- Deploy an Azure Application Gateway to handle the portal's path-based routing and SSL/TLS termination.Cevap
- Upgrade the Public IP addresses assigned to the virtual machine NICs to the Standard SKU to support integration with a Standard Load Balancer backend pool.Cevap
- CDeploy Azure Traffic Manager to manage the path-based routing and SSL/TLS termination for the portal.
- DConfigure a Basic Load Balancer with custom rules to offload SSL/TLS certificates and route traffic based on URL paths.
Cevap
Deploy an Azure Application Gateway to handle the portal's path-based routing and SSL/TLS termination, and upgrade the Public IP addresses assigned to the virtual machine NICs to the Standard SKU to support integration with a Standard Load Balancer backend pool.
Azure Application Gateway is a regional Layer 7 load balancer that supports path-based routing and SSL/TLS termination. For the database tier (TCP 1433), a Standard Load Balancer is required. To prevent validation failures due to SKU mismatch, any public IPs attached to the virtual machines in the Standard Load Balancer's backend pool must be upgraded from the Basic SKU to the Standard SKU.
Adım Adım Çözüm
Anahtar Kavram
Selecting and integrating Azure load balancing solutions based on protocol, routing, and SKU compatibility constraints.