Examkin

Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

A financial services company is deploying a high-frequency trading application on a fleet of Amazon EC2 instances. The application requires extremely low-latency, point-to-point network communication between the EC2 instances to coordinate order matching. The instances are managed by an Auto Scaling group and sit behind an Application Load Balancer. The application service is bound to port 84438443, but the target group health check is querying the default HTTP port 8080, marking the instances as unhealthy. Which combination of actions should a solutions architect take to resolve the health check issues and optimize the network performance of the instances?

  1. A
    Leave the target group health check port configured to port 8080, and launch the EC2 instances in a cluster placement group.
  2. Modify the target group health check settings to query port 84438443, and launch the EC2 instances in a cluster placement group.Answer
  3. C
    Modify the target group health check settings to query port 84438443, and launch the EC2 instances in a spread placement group.
  4. D
    Leave the target group health check port configured to port 8080, and launch the EC2 instances in a partition placement group.

Answer

Modify the target group health check settings to query port 84438443, and launch the EC2 instances in a cluster placement group.
The correct solution is to modify the target group health check settings to query port 84438443 and launch the EC2 instances in a cluster placement group. A cluster placement group groups instances closely together within a single Availability Zone, enabling low-latency, high-throughput network communication. Changing the health check port to 84438443 ensures the load balancer queries the active port of the application, resolving the health check failures.

Step-by-Step Solution

1
Identify the cause of the target group health check failure.
The application listens on port 84438443, but the health check queries port 8080, causing all checks to fail.
Health checks must target the active port where the application is listening to report correct status.
2
Determine the optimal EC2 placement strategy for low-latency node-to-node communication.
Select a cluster placement group.
Cluster placement groups place instances physically close to each other within a single Availability Zone, enabling low-latency, high-throughput network performance.
3
Combine the health check correction and the placement group selection.
Update the load balancer target group health check port to 84438443 and launch the instances within a cluster placement group.
This dual configuration resolves the health check failures and satisfies the low-latency networking requirement.

Key Concept

Optimizing EC2 network latency using placement groups and aligning load balancer health check ports with active services.
Rate this question

Topics

High-Performing and Elastic Compute Solutions

More questions from this topic