Examkin

Question

Difficulty: Very hardHigh-Performing and Elastic Compute Solutions

A software provider is deploying a containerized real-time telemetry processing application on Amazon ECS using AWS Fargate. The ingestion microservice receives high-velocity TCP traffic on port 8082, while administrative health and readiness checks are exposed on port 9000. Once ingested, the raw telemetry is streamed to a downstream high-performance computing (HPC) cluster of Amazon EC2 instances located in a single Availability Zone. This HPC cluster runs tightly-coupled Message Passing Interface (MPI) simulations that require sub-millisecond node-to-node network latency and maximum throughput.

Which TWO configuration steps must a solutions architect implement to satisfy the performance and health-monitoring requirements for this architecture?

  1. Deploy the EC2 instances within a cluster placement group and utilize instance types that support Elastic Fabric Adapter (EFA).Answer
  2. Configure the Network Load Balancer target group health checks to explicitly target port 9000 instead of the traffic port.Answer
  3. C
    Deploy the EC2 instances across multiple subnets within a spread placement group to distribute the workloads and achieve high availability.
  4. D
    Configure the Network Load Balancer target group to use the default traffic port setting for health checks to simplify resource management.
  5. E
    Attach a single Amazon EBS gp3 volume with Multi-Attach enabled to all EC2 instances in the cluster to provide a high-throughput shared scratch space.

Answer

Deploying the EC2 instances in a cluster placement group with EFA, and configuring the NLB target group health checks to use port 9000.
Deploying instances in a cluster placement group packs instances close together inside an Availability Zone, enabling low-latency, high-throughput network performance. Utilizing EFA enables OS-bypass networking, which is critical for scaling MPI-based HPC applications. Furthermore, since the application health check metrics are exposed on port 9000 rather than the service traffic port (8082), the NLB target group health check port must be explicitly configured to port 9000.

Step-by-Step Solution

1
Analyze the high-performance computing network requirement.
The tightly-coupled MPI application requires sub-millisecond node-to-node network latency and maximum throughput.
This is achieved by deploying EC2 instances in a cluster placement group within a single Availability Zone and utilizing EFA-enabled instance types.
2
Analyze the containerized ingestion service health check requirement.
The application serves ingestion traffic on port 8082 but exposes health checks on port 9000.
To prevent tasks from being incorrectly marked as unhealthy, the NLB target group health check port must be explicitly configured to port 9000 instead of defaulting to the traffic port.

Key Concept

High-Performance Compute Placement and Elastic Load Balancing Health Checks
Rate this question

Topics

High-Performing and Elastic Compute Solutions

More questions from this topic