A gaming company is deploying a multiplayer session hosting platform on Amazon EC2. The hosting nodes run a proprietary game server application that requires single-digit microsecond network latency for real-time state synchronization between the instances. Player traffic is distributed across the instances using a Network Load Balancer (NLB) targeting TCP port . The instance readiness and health status are managed by an administrative daemon listening on TCP port .
Which combination of configuration steps will satisfy the latency requirements and ensure proper health monitoring?
- ALaunch the EC2 instances in a spread placement group. Configure the Network Load Balancer target group health check to explicitly use TCP port .
- BLaunch the EC2 instances in a partition placement group. Configure the Network Load Balancer target group health check to use the default traffic port.
- Launch the EC2 instances in a cluster placement group. Configure the Network Load Balancer target group health check to explicitly use TCP port .Cevap
- DLaunch the EC2 instances in a cluster placement group. Configure the Network Load Balancer target group health check to use the default traffic port.
Cevap
Launch the EC2 instances in a cluster placement group. Configure the Network Load Balancer target group health check to explicitly use TCP port .
The correct option addresses both performance and monitoring requirements. Launching EC2 instances in a cluster placement group ensures they are placed physically close to each other, achieving the single-digit microsecond network latency required for real-time synchronization. Configuring the Network Load Balancer to check TCP port ensures that the load balancer correctly routes traffic based on the administrative daemon's status rather than simply checking the traffic port.
Adım Adım Çözüm
Anahtar Kavram
Combining cluster placement groups for low-latency node communication with custom health check port routing in Elastic Load Balancing.
Tahmini Süre:2m 30s