Examkin

Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

An insurance firm runs a distributed risk-modeling application on Amazon EC2 instances. The application consists of compute nodes that frequently communicate with each other, requiring low-latency and high-throughput node-to-node network communication. A Network Load Balancer (NLB) distributes incoming simulation jobs to these EC2 instances on custom port 8090. The target group is configured to perform health checks on port 80, which causes the NLB to mark all instances as unhealthy. Which two configuration changes should a solutions architect make to resolve these issues and optimize the compute architecture?

  1. Launch the EC2 instances in a cluster placement group.Answer
  2. Modify the target group health check configuration to query port 8090.Answer
  3. C
    Launch the EC2 instances in a spread placement group.
  4. D
    Launch the EC2 instances in a partition placement group.
  5. E
    Configure the target group health checks to use port 443.

Answer

Deploy the EC2 instances in a cluster placement group, and modify the target group health check configuration to query port 8090.
To achieve low-latency and high-throughput communication between nodes, instances must be launched in a cluster placement group. Additionally, since the application listens on port 8090 and the target group is querying port 80, the health check port configuration must be changed to port 8090 so that the Network Load Balancer can successfully verify instance health.

Step-by-Step Solution

1
Analyze the network latency and throughput requirements of the risk-modeling application.
The application requires high-throughput, low-latency node-to-node communication.
This requirement determines the correct placement group strategy.
2
Select the appropriate EC2 placement group.
A cluster placement group is selected.
Cluster placement groups place instances close together within a single Availability Zone, enabling low-latency and high-throughput TCP/IP communication.
3
Investigate the health check failure for the target group.
The target group is configured to health check on port 80, but the application runs on port 8090.
The mismatch causes the NLB health checks to fail, marking the instances as unhealthy.
4
Reconfigure the target group health check port.
The health check port is updated to 8090.
This aligns the health check with the actual port the application is listening on, allowing the NLB to detect the instances as healthy.

Key Concept

Selecting cluster placement groups for low-latency node-to-node communication and aligning target group health check ports with the application port.
Rate this question

Topics

High-Performing and Elastic Compute Solutions

More questions from this topic