Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

A gaming studio is deploying a real-time multiplayer simulation application on Amazon EC2. The architecture has two primary requirements: the EC2 instances must communicate with each other with the lowest possible network latency to synchronize physics calculations, and player connections must be distributed across these instances using a custom game protocol listening on port 7200.

Which two actions should a solutions architect take to meet these performance and scaling requirements? (Select TWO.)

  1. Launch the EC2 instances in a cluster placement group within a single Availability Zone.Answer
  2. B
    Launch the EC2 instances in a spread placement group across multiple Availability Zones.
  3. Configure a Network Load Balancer target group with the health check port set explicitly to 7200.Answer
  4. D
    Configure a Network Load Balancer target group with the health check port defaulting to port 80.
  5. E
    Deploy the simulation workload on AWS Lambda functions configured with provisioned concurrency.

Answer

Launch the EC2 instances in a cluster placement group within a single Availability Zone, and configure a Network Load Balancer target group with the health check port set explicitly to 7200.
To achieve the lowest possible network latency for node-to-node communication, the EC2 instances must be launched in a cluster placement group. Since the game protocol is bound to port 7200, the Network Load Balancer target group health checks must be explicitly directed to port 7200 to prevent healthy instances from being falsely marked as unhealthy.

Step-by-Step Solution

1
Determine the network requirement for synchronization.
The simulation requires the lowest possible node-to-node network latency.
This determines that a cluster placement group is necessary, as it groups instances physically close together on the network.
2
Determine the application port configuration.
The game application listens on a custom port 7200.
This is required to bind incoming traffic and configure health check endpoints.
3
Align the load balancer health check settings with the application port.
Configure the target group to perform health checks specifically on port 7200.
Using the default port 80 will cause health checks to fail since the application does not listen on that port.

Key Concept

Low-latency compute node placement groups and correct load balancer health check configuration for custom application ports.
Estimated Time:1m 30s
Rate this question