Soru

Zorluk: Orta

A genomics research institute is deploying a DNA sequencing pipeline on Amazon EC2 instances. The workload requires a tightly-coupled cluster of compute nodes to perform distributed sequence alignment using Message Passing Interface (MPI). In addition, a web dashboard queries a status daemon running on port 94439443 of these instances to monitor alignment progress. The dashboard traffic is distributed to the instances via an Application Load Balancer (ALB) listening on port 443443.

Which TWO configurations should a solutions architect implement to achieve optimal network performance for the MPI workload and ensure the ALB correctly monitors the status daemon?

  1. Deploy the EC2 instances in a cluster placement group within a single Availability Zone.Cevap
  2. B
    Deploy the EC2 instances in a spread placement group across multiple Availability Zones.
  3. Configure the ALB target group's health checks to use port 94439443 instead of the default traffic port.Cevap
  4. D
    Configure the ALB target group to perform health checks on the default traffic port of 443443.
  5. E
    Deploy the EC2 instances in a partition placement group to isolate processing workloads on distinct hardware partitions.

Cevap

Deploy the EC2 instances in a cluster placement group within a single Availability Zone, and configure the Application Load Balancer target group's health checks to use the custom daemon port instead of the default traffic port.
The correct configurations are to deploy the EC2 instances in a cluster placement group and to configure the ALB target group's health checks to use the specific port where the status daemon runs. A cluster placement group places instances physically close to each other in a single Availability Zone, providing the low-latency network performance required by tightly-coupled MPI workloads. Additionally, specifying the custom daemon port for the ALB health checks ensures the load balancer accurately monitors the status daemon's health rather than the main web server port.

Adım Adım Çözüm

1
Determine the placement group requirement for a tightly-coupled MPI computing workload.
A cluster placement group is selected because it enables low-latency, high-throughput node-to-node networking within a single Availability Zone.
Tightly-coupled cluster nodes must communicate with minimal latency, which is the primary benefit of cluster placement groups.
2
Identify the correct health check port configuration for the status daemon.
The health check port in the target group configuration must be explicitly set to the daemon's port.
If the daemon runs on a custom port that is different from the main traffic port, the default traffic port health check will fail to monitor the actual daemon.

Anahtar Kavram

Tightly-coupled high-performance computing (HPC) environments require cluster placement groups for low-latency networking, and load balancers must have health checks aligned with the specific service ports of monitored daemons.
Bu soruyu puanla