A financial company is deploying a distributed, high-throughput order matching engine on Amazon EC2 instances. The compute nodes require closely-coupled, low-latency node-to-node communication to synchronize order books. The matching engine application runs on a custom port of 8999. A Network Load Balancer (NLB) is configured to route client traffic to these nodes. The platform must scale dynamically while maintaining optimal network performance and ensuring the NLB accurately identifies healthy compute instances. Which two actions should the solutions architect take to meet these requirements?
- Launch the EC2 instances in a cluster placement group.Cevap
- Configure the Network Load Balancer target group health check to use port 8999.Cevap
- CLaunch the EC2 instances in a spread placement group across multiple Availability Zones.
- DConfigure the Network Load Balancer target group health check to query the default HTTP port 80.
- ELaunch the EC2 instances in a partition placement group with a partition count of seven.
Cevap
Launch the EC2 instances in a cluster placement group, and configure the Network Load Balancer target group health check to use port 8999.
The correct options are launching the instances in a cluster placement group and configuring the health check port to 8999. A cluster placement group places instances physically close together within a single Availability Zone, enabling low-latency, 10 Gbps or 25 Gbps node-to-node throughput. Additionally, since the application runs on custom port 8999, the load balancer's target group health check must specifically target port 8999 to successfully determine instance health.
Adım Adım Çözüm
Anahtar Kavram
High-performance EC2 configurations require cluster placement groups for low-latency node-to-node communication, and load balancer target group health check ports must match the application port.