An autonomous vehicle research company is running large-scale LiDAR sensor simulation workloads across a fleet of Amazon EC2 instances. The simulation nodes must frequently exchange spatial data frames with microsecond-level network latency. The nodes also run a management service on port , which is registered with an Application Load Balancer (ALB). During initial testing, the simulation experiences significant network latency, and the ALB target group marks all EC2 instances as unhealthy. Which combination of actions should a solutions architect take to resolve these issues?
- ADeploy the EC2 instances in a spread placement group, and update the ALB target group health check settings to monitor port .
- BDeploy the EC2 instances in a cluster placement group, and configure the ALB target group health check to query the default traffic port.
- Deploy the EC2 instances in a cluster placement group, and update the ALB target group health check settings to monitor port .Answer
- DDeploy the EC2 instances in a partition placement group, and configure the ALB target group health check to query the default traffic port.
Answer
Deploying the EC2 instances in a cluster placement group and updating the ALB target group health check settings to monitor port resolves both the latency and health check issues.
A cluster placement group is the correct choice because it places instances physically close to each other within a single Availability Zone, providing the low-latency, high-throughput network performance required for tightly coupled applications. Furthermore, modifying the target group health check port to match the custom port where the management service is listening resolves the health check mismatch, allowing the load balancer to correctly identify the instances as healthy.
Step-by-Step Solution
Key Concept
Selecting cluster placement groups for low-latency node-to-node communication and configuring ALB custom health check ports.
Estimated Time:2m 0s