An energy grid operator runs a distributed power-flow optimization simulator on a fleet of Amazon EC2 instances. The simulator nodes must communicate with each other using Message Passing Interface (MPI) with the lowest possible latency. The optimization service on each instance runs on port 7001. A Network Load Balancer (NLB) distributes management API requests to the instances, but currently reports all instances as unhealthy because the health check is set to the default port 80. Which configuration will achieve the required network performance and resolve the health check issue?
- AConfigure a partition placement group for the EC2 instances. Update the NLB target group health check port to 7001.
- BConfigure a cluster placement group for the EC2 instances. Keep the target group health check port at the default port 80.
- Configure a cluster placement group for the EC2 instances. Update the NLB target group health check port to 7001.Cevap
- DConfigure a spread placement group for the EC2 instances. Update the NLB target group health check port to 7001.
Cevap
Configure a cluster placement group for the EC2 instances. Update the NLB target group health check port to 7001.
For tightly-coupled MPI applications requiring low latency, a cluster placement group is the appropriate choice because it physically groups the instances together inside a single Availability Zone. Additionally, because the application is listening on port 7001, the health check port must be updated from the default port 80 to port 7001 so the load balancer can verify the actual application status instead of getting connection timeouts on an unused port.
Adım Adım Çözüm
Anahtar Kavram
Selecting the correct EC2 placement group for low-latency node-to-node communication and ensuring that the load balancer health check configuration aligns with the application port.
Tahmini Süre:2m 0s