Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

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 91009100, 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?

  1. A
    Deploy the EC2 instances in a spread placement group, and update the ALB target group health check settings to monitor port 91009100.
  2. B
    Deploy the EC2 instances in a cluster placement group, and configure the ALB target group health check to query the default traffic port.
  3. Deploy the EC2 instances in a cluster placement group, and update the ALB target group health check settings to monitor port 91009100.Answer
  4. D
    Deploy 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 91009100 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

1
Address inter-node network latency by choosing the correct placement group.
Identify that a cluster placement group packs instances close together inside an Availability Zone, enabling low-latency, high-throughput network performance.
Tightly coupled applications like simulations require minimal network latency, which cluster placement groups provide.
2
Resolve the Application Load Balancer health check failures.
Update the target group's health check configuration to target port 91009100 instead of the default traffic port.
By default, target groups perform health checks on the traffic port or port 8080. If the management service runs on port 91009100, the default health check will fail because there is no listener on the default port.

Key Concept

Selecting cluster placement groups for low-latency node-to-node communication and configuring ALB custom health check ports.
Estimated Time:2m 0s
Rate this question