Examkin

Soru

Zorluk: OrtaHigh-Performing and Elastic Compute Solutions

A technology company is deploying a distributed search index compilation engine on a fleet of Amazon EC2 instances. The compilation nodes must frequently synchronize index shards with each other, requiring the lowest possible latency for inter-node communication. A Network Load Balancer (NLB) is configured to route jobs from a coordinator service to the nodes on TCP port 8888. A custom health monitoring daemon runs on each instance on TCP port 8899. Currently, the NLB is marking all instances as unhealthy because the target group is using the default health check settings. Which combination of steps should the solutions architect take to resolve the health check issue and optimize inter-node network performance? (Select TWO.)

  1. Launch the EC2 instances in a cluster placement group.Cevap
  2. Configure the target group health check port to use port 8899.Cevap
  3. C
    Launch the EC2 instances in a partition placement group.
  4. D
    Launch the EC2 instances in a spread placement group.
  5. E
    Change the NLB listener port to 8899 and set the target group health check port to use the traffic port.

Cevap

Launch the EC2 instances in a cluster placement group and configure the target group health check port to use port 8899.
To achieve the lowest possible network latency and high-throughput inter-node communication, the instances must be launched in a cluster placement group. In addition, the health check port in the Network Load Balancer target group must be modified to use port 8899 so that health checks query the monitoring daemon instead of failing on the default traffic port.

Adım Adım Çözüm

1
Analyze inter-node network requirements.
The compilation engine requires minimal latency and maximum throughput for index shard synchronization.
Choosing a cluster placement group colocates instances on the same underlying hardware backplane within a single Availability Zone, meeting the low-latency requirement.
2
Diagnose the load balancer health check failure.
The target group defaults to using the traffic port (8888) for health checks, where no health monitoring daemon is running.
Configuring the target group to explicitly probe port 8899 aligns the health check with the custom health monitoring daemon.

Anahtar Kavram

Selecting the correct EC2 placement group for low-latency networking and aligning target group health check ports with service daemons.
Bu soruyu puanla

Konular

High-Performing and Elastic Compute Solutions

Bu konudan daha fazla soru