A technology company is deploying a self-managed distributed search engine cluster on Amazon EC2 instances. The cluster nodes must communicate with each other with the lowest possible network latency to ensure fast query indexing. Additionally, an Application Load Balancer (ALB) is used to expose an internal management dashboard that runs on port 8443 of the same instances, while the standard HTTP port 80 is closed on the instances' firewalls. Which combination of configurations will meet the performance requirements and prevent the instances from being falsely marked as unhealthy by the load balancer?
- ADeploy the EC2 instances in a spread placement group. Configure the ALB target group's health checks to use port 8443.
- Deploy the EC2 instances in a cluster placement group. Configure the ALB target group's health checks to use port 8443.Answer
- CDeploy the EC2 instances in a partition placement group. Configure the ALB target group's health checks to use port 8443.
- DDeploy the EC2 instances in a cluster placement group. Configure the ALB target group's health checks to use the default port 80.
Answer
Deploying the EC2 instances in a cluster placement group and configuring the Application Load Balancer's target group health check to port 8443.
Deploying the EC2 instances in a cluster placement group provides low-latency, high-throughput communication by physically grouping instances within a single Availability Zone. Additionally, configuring the Application Load Balancer (ALB) health checks to target port 8443 aligns the health probes with the port where the management daemon is actually listening, ensuring the instances are not incorrectly marked as unhealthy due to port 80 being closed.
Step-by-Step Solution
Key Concept
Amazon EC2 Placement Groups and Elastic Load Balancing Health Checks
Estimated Time:1m 30s