A company has an application with a front end that communicates with backend instances via a Network Load Balancer (NLB) within the same VPC. The application is designed for high availability across two Availability Zones. The company aims to minimize cross-Availability Zone traffic, ensuring that front-end traffic remains within the same Availability Zone unless no healthy targets are available in that zone. If no healthy targets exist in the same Availability Zone, traffic should be routed to the other Availability Zone.

Which solution fulfills these requirements?

Exam-Like

Create a private hosted zone with weighted routing for each Availability Zone. Point the primary record to the local Availability Zone NLB DNS record. Point the secondary record to the Regional NLB DNS record. Configure the front end of the application to perform DNS lookups on the local private hosted zone records.

0.0%

Turn off cross-zone load balancing on the NLB. Configure the front end of the application to perform DNS lookups on the local Availability Zone NLB DNS record.

20.0%

Create a private hosted zone. Create a failover record for each Availability Zone. For each failover record, point the primary record to the local Availability Zone NLB DNS record and point the secondary record to the Regional NLB DNS record. Configure the front end of the application to perform DNS lookups on the local private hosted zone records.

40.0%

Enable sticky sessions (session affinity) so that the NLB can bind a user’s session to targets in the same Availability Zone.

40.0%

AWS Certified Advanced Networking - Specialty

Get started today

Comments