Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

An engineering company runs a distributed computational fluid dynamics (CFD) simulation suite on a group of Amazon EC2 instances. The simulation nodes must exchange data with the lowest possible latency and maximum throughput. The administration team wants to monitor these nodes using a web dashboard that listens on TCP port 3000 of each instance, routed through an Application Load Balancer (ALB) that accepts traffic on port 443. The ALB target group is currently failing health checks.

Which actions should the solutions architect take to satisfy the latency requirements and resolve the health check issues? (Select TWO.)

  1. Place the EC2 instances within a cluster placement groupAnswer
  2. B
    Place the EC2 instances within a spread placement group
  3. C
    Place the EC2 instances within a partition placement group
  4. Configure the target group health check port to explicitly query port 3000Answer
  5. E
    Set the target group health check port to use the traffic port

Answer

Place the EC2 instances within a cluster placement group to meet the low latency requirement, and configure the target group health check port to explicitly query port 3000 to resolve the failing health checks.
To achieve the lowest possible network latency and highest throughput for inter-node communication, instances must be launched in a cluster placement group. Additionally, because the backend monitoring dashboard listens on port 3000 while the Application Load Balancer routes user traffic on port 443, the target group's health check port must be explicitly configured to port 3000 so the health check requests reach the active service.

Step-by-Step Solution

1
Analyze the network latency requirements for the distributed fluid dynamics simulation.
Determine that a cluster placement group is required to achieve the lowest possible network latency and high throughput.
Cluster placement groups place instances close together within a single Availability Zone, optimizing node-to-node performance.
2
Identify the cause of the load balancer target group health check failures.
Note the port mismatch: the web dashboard service on the instances listens on port 3000, while the ALB target group receives traffic on port 443.
By default, target group health checks query the traffic port (port 443). Since no service is listening on port 443 on the EC2 instances, the health checks fail.
3
Correct the target group configuration to resolve the health check failure.
Override the default health check port by setting it explicitly to port 3000.
This configuration routes health checks directly to the active web dashboard service port.

Key Concept

Tightly coupled compute workloads require cluster placement groups for low-latency node-to-node communication, and Elastic Load Balancing target groups must align health check ports with the backend application port.
Rate this question