A marketing agency is deploying a real-time ad bidding analytics application on a fleet of Amazon EC2 instances. The application performs distributed, high-performance computing calculations that require sub-millisecond node-to-node latency. The instances are deployed in a private subnet and are registered with an Application Load Balancer (ALB) that routes incoming traffic. The application service on the EC2 instances is configured to listen on custom port 8080.
Which combination of actions should a solutions architect take to meet the performance requirements and ensure that the ALB successfully forwards traffic to the EC2 instances? (Select TWO.)
- Launch the EC2 instances in a cluster placement group within a single Availability Zone.Answer
- Configure the Application Load Balancer target group health check to query the custom port 8080.Answer
- CLaunch the EC2 instances in a spread placement group across multiple Availability Zones to ensure network performance.
- DConfigure the target group to perform health checks using the default port 80 to ensure the ALB can dynamically route traffic to the custom port.
- ELaunch the EC2 instances in a partition placement group to minimize network latency between nodes by distributing them across logical partitions.
Answer
Launch the EC2 instances in a cluster placement group within a single Availability Zone and configure the Application Load Balancer target group health check to query the custom port 8080.
To achieve sub-millisecond node-to-node latency, instances must be launched in a cluster placement group within a single Availability Zone. Additionally, because the application is listening on a custom port 8080, the ALB's target group health check must be explicitly configured to monitor port 8080 to prevent healthy targets from being marked as unhealthy.
Step-by-Step Solution
Key Concept
Low-latency compute clustering and application target group health check configuration