A research institution is deploying a seismic data processing cluster on Amazon EC2 instances to analyze real-time earthquake signals. The cluster requires sub-millisecond node-to-node communication latency to perform fast Fourier transform calculations. To receive incoming seismic data feeds from remote stations, the instances are registered with an Application Load Balancer (ALB) target group configured for HTTP traffic on port 8088. The application's health status endpoint is also served on port 8088, but the instances are currently marked unhealthy by the ALB, and node-to-node latency is too high. Which configuration will resolve the health check issues and achieve the required network performance?
- ALaunch the instances in a spread placement group. Set the target group health check port to 8088.
- BLaunch the instances in a cluster placement group. Leave the target group health check port at the default configuration.
- Launch the instances in a cluster placement group. Set the target group health check port to 8088.Cevap
- DLaunch the instances in a partition placement group. Leave the target group health check port at the default configuration.
Cevap
Launch the instances in a cluster placement group. Set the target group health check port to 8088.
Deploying the EC2 instances in a cluster placement group ensures that the nodes are physically located close to each other within a single Availability Zone, enabling low-latency, high-throughput node-to-node communication. Configuring the load balancer's target group health check port to 8088 ensures the load balancer queries the port where the application actually listens and reports health, resolving the health check failures.
Adım Adım Çözüm
Anahtar Kavram
High-performing and elastic compute configurations, specifically EC2 placement groups and ELB health check port alignment.