Question

Difficulty: EasyHigh-Performing and Elastic Compute Solutions

A company is deploying a distributed graph database cluster on Amazon EC2. The database nodes require maximum throughput and the lowest possible latency for node-to-node synchronization. Additionally, the cluster must be fronted by a Network Load Balancer (NLB) listening on custom port 9900 to route client queries to the database nodes. Which combination of steps should the solutions architect take to meet these requirements? (Select TWO.)

  1. Launch the EC2 instances within a cluster placement group.Answer
  2. Configure the target group of the Network Load Balancer to perform health checks on port 9900.Answer
  3. C
    Launch the EC2 instances within a spread placement group.
  4. D
    Configure the target group of the Network Load Balancer to perform health checks on the default HTTP port 80.
  5. E
    Launch the EC2 instances within a partition placement group.

Answer

To meet the requirements, the solutions architect should launch the EC2 instances in a cluster placement group and configure the Network Load Balancer target group to perform health checks on port 9900.
Launching the EC2 instances in a cluster placement group ensures that the instances are placed physically close together in the AWS infrastructure, providing the low-latency, high-throughput network performance required. Configuring the target group health check port to use port 9900 ensures that the Network Load Balancer correctly checks the port where the database application is active, preventing healthy targets from being marked as unhealthy.

Step-by-Step Solution

1
Analyze the network latency and throughput requirements between the EC2 instances.
The application requires high throughput and very low node-to-node latency, which points to the need for a cluster placement group.
Cluster placement groups place instances physically close to each other within a single Availability Zone, enabling high-performance networking.
2
Analyze the load balancing and health check requirements.
The database application listens on custom port 9900, meaning health checks must be directed to port 9900.
Querying the default port 80 instead of the custom port 9900 would fail, causing the load balancer to incorrectly identify all instances as unhealthy.

Key Concept

High-Performance and Elastic Compute Solutions require appropriate placement groups for low-latency node-to-node communication, and correct health check configuration to ensure traffic is correctly routed to healthy custom ports.
Rate this question