An advertising technology company is deploying a real-time bidding (RTB) engine on Amazon EC2 instances to process ad auctions. The engine must maintain sub-millisecond node-to-node network latency to synchronize internal state tables across the cluster. The bidding application runs on a custom port, , on each EC2 instance. The company deploys a Network Load Balancer (NLB) with a listener on port to receive incoming HTTP requests from external ad exchanges and route them to the EC2 instances. During initial testing, the NLB marks all EC2 instances as unhealthy, and node-to-node communication latency is higher than expected. Which combination of EC2 placement and load balancer target group configuration will resolve these issues while meeting the performance requirements?
- ADeploy the EC2 instances in a spread placement group. Configure the NLB target group health check to query port 9080.
- BDeploy the EC2 instances in a cluster placement group. Configure the NLB target group health check to query port 80.
- Deploy the EC2 instances in a cluster placement group. Configure the NLB target group health check to query port 9080.Cevap
- DDeploy the EC2 instances in a partition placement group. Configure the NLB target group health check to query port 80.