A logistics company is building a high-throughput route optimization engine on Amazon EC2. The workload requires a fleet of compute-optimized instances to communicate with each other over a low-latency network using Message Passing Interface (MPI). The instances also run a management daemon on port 9090 which needs to be monitored by an Application Load Balancer (ALB) target group. Which two actions should the solutions architect take to meet these performance and monitoring requirements?
- Launch the EC2 instances in a cluster placement group.Answer
- Configure the ALB target group health checks to specifically query port 9090.Answer
- CLaunch the EC2 instances in a spread placement group.
- DLaunch the EC2 instances in a partition placement group.
- EConfigure the ALB target group health checks to use the default traffic port while setting the daemon port to 9090.
Answer
Launch the EC2 instances in a cluster placement group and configure the ALB target group health checks to specifically query port 9090.
The correct configuration requires launching the instances in a cluster placement group to minimize network latency for the MPI workload, and configuring the target group health checks to target the custom port where the daemon is listening to prevent false unhealthy states.
Step-by-Step Solution
Key Concept
Low-latency EC2 placement groups and custom port target group health checking