Examkin

Question

Difficulty: MediumHigh-Performing and Elastic Compute Solutions

A petroleum exploration firm is deploying a distributed reservoir simulation application on Amazon EC2. The application relies on Message Passing Interface (MPI) for tightly coupled, high-throughput node-to-node communication. To handle input parameter submissions, the EC2 instances are registered to a Target Group behind an Application Load Balancer (ALB). The simulation workload runs on port 9095, while a lightweight administrative dashboard on the instances listens on port 8088 to process health checks. Currently, the ALB is marking all registered EC2 instances as unhealthy. Which combination of actions will resolve the health check failures and optimize compute performance for the simulation workload?

  1. Launch the EC2 instances in a cluster placement group. Set the Target Group health check port to 8088.Answer
  2. B
    Launch the EC2 instances in a spread placement group. Set the Target Group health check port to 8088.
  3. C
    Launch the EC2 instances in a cluster placement group. Leave the Target Group health check port configured to traffic-port.
  4. D
    Launch the EC2 instances in a partition placement group. Leave the Target Group health check port configured to traffic-port.

Answer

Launch the EC2 instances in a cluster placement group. Set the Target Group health check port to 8088.
The correct option correctly suggests launching the EC2 instances in a cluster placement group to achieve the low-latency network performance required by MPI-based simulation workloads, and changing the health check port to 8088 to match the port of the administrative dashboard that handles health checks.

Step-by-Step Solution

1
Analyze the network latency and throughput requirements of the MPI application.
Identify that a cluster placement group is necessary to locate the EC2 instances close together on the same underlying hardware to achieve low-latency, high-throughput communication.
MPI applications require tightly coupled node-to-node communication that only cluster placement groups can deliver on AWS.
2
Identify the cause of the load balancer marking the instances as unhealthy.
Determine that the health check requests are being sent to the default traffic-port (port 9095), where the simulation runs instead of the administrative dashboard (port 8088).
The load balancer health checks must be explicitly configured to target the port where the health check service is active.
3
Configure the target group settings.
Change the health check port configuration from 'traffic-port' to port 8088.
This redirects health check traffic to the administrative dashboard, allowing the ALB to receive successful health check responses and mark the instances as healthy.

Key Concept

Selecting appropriate EC2 placement groups for high-performance compute workloads and configuring custom health check ports on target groups.
Estimated Time:2m 0s
Rate this question

Topics

High-Performing and Elastic Compute Solutions

More questions from this topic