A company runs custom statistical analysis software on a cluster of Amazon EC2 instances. The software is highly sensitive to network latency between nodes, although network throughput is not a…

Question

Options

• APlace all the EC2 instances into a cluster placement group.
• BConfigure and assign two Elastic IP addresses for each EC2 instance.
• CConfigure jumbo frames on all the EC2 instances in the cluster.
• Dincreases distance, worsening latency.

• A
  73% (32)
• B
  9% (4)
• C
  5% (2)
• D
  14% (6)

Explanation

The AWS Cloud Operations and Compute documentation explains that placement groups control how EC2 instances are physically arranged within AWS data centers to optimize network Cluster placement groups place instances physically close together within a single Availability Zone, connected through high-bandwidth, low-latency networking (ideal for tightly coupled, HPC, or distributed workloads). Spread placement groups distribute instances across distinct racks or Availability Zones for fault tolerance, increasing latency. Partition placement groups separate instances into partitions for isolation, not latency reduction. Therefore, to minimize latency for workloads such as computational clusters, the CloudOps engineer should use a cluster placement group. This placement ensures single-digit microsecond latency and enhanced packet rate performance between instances. Elastic IPs (Option B) do not influence internal networking. Jumbo frames (Option C) can marginally improve throughput but do not reduce propagation latency. Spread placement (Option Hence, Option A -- using a cluster placement group -- delivers the lowest possible network latency and is AWS's best-practice design for HPC-style clusters.

No community discussion yet for this question.