Examkin

Question

Difficulty: HardHigh-Performing and Elastic Compute Solutions

A gaming company is deploying a backend matchmaking and state synchronization engine on Amazon EC2 instances. The engine requires sub-millisecond latency and high network throughput for peer-to-peer node communication to keep game states synchronized. The game client traffic is distributed using a Network Load Balancer (NLB) configured to route UDP and TCP traffic to port 82008200 on the instances. Which two actions should the solutions architect take to meet these performance and reliability requirements? (Choose two.)

  1. Launch the Amazon EC2 instances in a cluster placement group.Answer
  2. Configure the target group health checks to explicitly use port 82008200.Answer
  3. C
    Launch the Amazon EC2 instances in a spread placement group.
  4. D
    Launch the Amazon EC2 instances in a partition placement group.
  5. E
    Configure the target group health checks to use the default health check port (port 8080).

Answer

The correct options are to launch the EC2 instances in a cluster placement group and to configure the target group health checks to explicitly use port 82008200.
Launching the Amazon EC2 instances in a cluster placement group ensures that the compute nodes are physically close together within a single Availability Zone, enabling low-latency, high-throughput network performance. In addition, configuring the target group health checks to explicitly use port 82008200 ensures that the Network Load Balancer correctly monitors the status of the custom application port rather than failing on the default port.

Step-by-Step Solution

1
Analyze the low-latency networking requirements of the peer-to-peer matchmaking engine.
The application requires sub-millisecond node-to-node latency, which points to using an EC2 cluster placement group.
A cluster placement group places instances physically close together within a single Availability Zone, enabling high-speed, low-latency communication.
2
Analyze the port mapping for the application and the health check configuration.
The application runs on port 82008200. Configuring the target group health checks to use this custom port ensures accurate health monitoring.
Using the default port like port 8080 for health checks when the application is running on port 82008200 would lead to false-negative health check results, causing the NLB to mark healthy targets as unhealthy.

Key Concept

Optimizing compute node-to-node network latency and health monitoring configurations for high-performance applications on AWS.
Rate this question

Topics

High-Performing and Elastic Compute Solutions

More questions from this topic