Examkin

Soru

Zorluk: ZorHigh-Performing and Elastic Compute Solutions

A biotechnology company is deploying a distributed genomic sequencing pipeline on Amazon EC2. The sequencing tasks require tightly-coupled compute nodes that communicate via Message Passing Interface (MPI) to process large datasets with sub-millisecond node-to-node latency. Additionally, a Network Load Balancer (NLB) is configured to route incoming telemetry data to a proprietary ingestion service running on custom port 5005150051 on these EC2 instances. The solutions architect needs to design a high-performing and elastic compute infrastructure that supports both the low-latency MPI communication and the correct routing of ingestion data.

Which TWO actions should the solutions architect take to meet these requirements?

  1. Launch the EC2 instances in a cluster placement group within a single Availability Zone.Cevap
  2. Configure the Network Load Balancer target group health checks to explicitly monitor port 5005150051.Cevap
  3. C
    Launch the EC2 instances in a spread placement group to distribute the instances across distinct hardware racks.
  4. D
    Configure the Network Load Balancer target group health checks to use the default target port of 8080.
  5. E
    Launch the EC2 instances in a partition placement group to distribute the instances across multiple logical partitions.

Cevap

Launch the EC2 instances in a cluster placement group within a single Availability Zone, and configure the Network Load Balancer target group health checks to monitor port 50051.
The correct architecture requires launching the EC2 instances in a cluster placement group and configuring the Network Load Balancer target group health checks to explicitly monitor port 5005150051. A cluster placement group places instances physically close to one another within a single Availability Zone, providing the low-latency, high-throughput network performance required for Message Passing Interface (MPI) and tightly-coupled compute workloads. Additionally, because the proprietary ingestion service is running on custom port 5005150051, the health checks must be explicitly directed to that port to ensure correct monitoring of the application daemon; otherwise, the load balancer will fail to reach the instances and flag them as unhealthy.

Adım Adım Çözüm

1
Analyze the network latency requirement for MPI-based workloads.
Tightly-coupled MPI workloads require sub-millisecond node-to-node latency, which is achieved by packing EC2 instances close together physically.
This determines the choice of EC2 placement groups, highlighting that a cluster placement group is necessary.
2
Identify the incorrect placement group configurations.
Spread and partition placement groups introduce physical separation to reduce risk, which conflicts with low-latency requirements.
This eliminates options recommending spread or partition placement groups.
3
Analyze the ingestion service architecture and port settings.
The proprietary ingestion service is bound to port 5005150051, and standard HTTP services (port 8080) are not serving this application.
This establishes that the target group health checks must query the service port to properly reflect instance health.
4
Evaluate the behavior of default health checks.
Using the default traffic port 8080 for health checks fails because no process is listening on it, causing healthy instances to be marked unhealthy.
This ensures the selection of explicit custom health check port configurations.

Anahtar Kavram

Low-latency compute clusters and custom port target group health checks
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

High-Performing and Elastic Compute Solutions

Bu konudan daha fazla soru