Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

A research institution is deploying a seismic data processing cluster on Amazon EC2 instances to analyze real-time earthquake signals. The cluster requires sub-millisecond node-to-node communication latency to perform fast Fourier transform calculations. To receive incoming seismic data feeds from remote stations, the instances are registered with an Application Load Balancer (ALB) target group configured for HTTP traffic on port 8088. The application's health status endpoint is also served on port 8088, but the instances are currently marked unhealthy by the ALB, and node-to-node latency is too high. Which configuration will resolve the health check issues and achieve the required network performance?

  1. A
    Launch the instances in a spread placement group. Set the target group health check port to 8088.
  2. B
    Launch the instances in a cluster placement group. Leave the target group health check port at the default configuration.
  3. Launch the instances in a cluster placement group. Set the target group health check port to 8088.Answer
  4. D
    Launch the instances in a partition placement group. Leave the target group health check port at the default configuration.

Answer

Launch the instances in a cluster placement group. Set the target group health check port to 8088.
Deploying the EC2 instances in a cluster placement group ensures that the nodes are physically located close to each other within a single Availability Zone, enabling low-latency, high-throughput node-to-node communication. Configuring the load balancer's target group health check port to 8088 ensures the load balancer queries the port where the application actually listens and reports health, resolving the health check failures.

Step-by-Step Solution

1
Analyze the node-to-node communication latency requirement.
Identify that a cluster placement group is required to group instances physically close together on the same underlying hardware to minimize network latency.
Other placement groups like spread or partition are designed to maximize physical isolation, which increases network latency.
2
Analyze the load balancer health check failure.
Identify that the application serves health check endpoints on port 8088, but the ALB defaults to port 80 (or the default listener configuration) which has no service running.
A target group health check port mismatch causes the load balancer to mark healthy targets as unhealthy.
3
Select the correct combination of configurations.
Combine the cluster placement group configuration with setting the health check port specifically to port 8088.
This dual configuration addresses both the network latency performance requirements and the health check failures.

Key Concept

High-performing and elastic compute configurations, specifically EC2 placement groups and ELB health check port alignment.
Rate this question