Examkin

Soru

Zorluk: OrtaHigh-Performing and Elastic Compute Solutions

A biotechnology company is deploying a distributed molecular dynamics simulation pipeline on Amazon EC2 instances. The simulation nodes must communicate frequently with each other over a low-latency, high-throughput network to synchronize state. The application listens on custom TCP port 6006 and is placed behind a Network Load Balancer (NLB). During testing, the NLB marks all instances as unhealthy, and node-to-node communication latency is too high. Which combination of steps will resolve these performance and health check issues?

  1. A
    Launch the EC2 instances in a spread placement group, and update the NLB target group health check configuration to use the custom port 6006.
  2. B
    Launch the EC2 instances in a cluster placement group, and configure a security group rule on the instances to redirect incoming health checks from port 80 to port 6006.
  3. Launch the EC2 instances in a cluster placement group, and update the NLB target group health check configuration to use the custom port 6006.Cevap
  4. D
    Launch the EC2 instances in a partition placement group, and configure the NLB target group to perform health checks on the default port 80.

Cevap

Launch the EC2 instances in a cluster placement group, and update the NLB target group health check configuration to use the custom port 6006.
The correct option correctly addresses both issues. Using a cluster placement group packs instances close together within a single Availability Zone, which enables low-latency, high-throughput node-to-node communication. Configuring the NLB target group to perform health checks on the custom port 6006 ensures that the NLB successfully connects to the active application listener and marks the instances as healthy.

Adım Adım Çözüm

1
Analyze the network latency requirement.
Identify that the simulation nodes require low-latency, high-throughput node-to-node communication.
Tightly coupled HPC workloads require cluster placement groups to ensure instances are physically close together in the same Availability Zone.
2
Analyze the NLB health check failure.
Determine that the application is listening on custom port 6006, but the health check is failing.
By default, target groups may perform health checks on traffic ports or default ports like 80. If the custom port is not configured for health checks, the NLB cannot verify application health.
3
Select the correct combination of placement group and port configuration.
Select a cluster placement group for low latency and configure the target group health check to query port 6006.
This resolves both the high latency issue and the unhealthy target registration issue.

Anahtar Kavram

Selecting the correct EC2 placement group for low-latency communication and aligning ELB target group health check ports with custom application ports.
Bu soruyu puanla

Konular

High-Performing and Elastic Compute Solutions

Bu konudan daha fazla soru