A company has a furniture inventory application deployed on a fleet of Amazon EC2 instances across multiple Availability Zones behind an Application Load Balancer (ALB). The solutions architect observes that incoming traffic favors one EC2 instance, causing latency for some requests. What should the solutions architect do to resolve this issue?

The problem describes uneven traffic distribution, leading to latency on a specific instance. Session affinity, also known as sticky sessions, routes a user's requests to the same EC2 instance for the duration of their session. If a large number of users initiate sessions with one particular instance, it can become overloaded while others remain underutilized. Disabling sticky sessions will allow the ALB to distribute requests more evenly across all healthy instances, resolving the imbalance. Replacing the ALB with a Network Load Balancer (NLB) is incorrect because NLBs operate at Layer 4 and do not offer the advanced routing features like sticky sessions that are causing the problem here. Increasing the number of EC2 instances might temporarily alleviate the load on the overutilized instance but doesn't address the root cause of the uneven distribution. Adjusting health check frequency is unrelated to traffic distribution issues caused by session affinity.