A company's web application uses an Application Load Balancer (ALB) to direct traffic to Amazon EC2 instances across three Availability Zones. The company has deployed a newer version of the applicati

Question

Options

• ADisable cross-zone load balancing on the ALB's target group. Initiate a zonal shift on the ALB to
• BDisable cross-zone load balancing on the ALB's target group. Manually remove instances in the
• CConfigure cross-zone load balancing on the ALB's target group to inherit settings from the ALB.
• DConfigure cross-zone load balancing on the ALB's target group to inherit settings from the ALB.

• A
  56% (19)
• B
  24% (8)
• C
  6% (2)
• D
  15% (5)

Explanation

Cross-zone load balancing distributes incoming traffic across all available instances, regardless of their Availability Zone (AZ). To ensure that traffic can be directed away from a specific AZ, cross-zone load balancing must be disabled. This way, traffic will only go to instances in the same AZ where it was initially directed, allowing more control over which AZs receive traffic. Zonal shift is an efficient and quick way to direct traffic away from a specific AZ in the event of a problem. Initiating a zonal shift allows you to temporarily stop traffic from being routed to the instances in the affected AZ without disrupting traffic to the other AZs. This approach ensures that the application remains available and stable during a rollback or incident. By disabling cross-zone load balancing and using a zonal shift, the company can quickly and efficiently direct traffic away from the problematic Availability Zone while ensuring that the application remains available and stable in the other AZs. This approach provides the most operational efficiency with minimal disruption.

No community discussion yet for this question.