AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company is deploying a new, computationally intensive workload on AWS for market simulation. The application is tightly-coupled and requires the lowest possible inter-node latency for optimal performance. The workload runs for several hours at a time, is fault-tolerant and can be interrupted, making it highly cost-sensitive. The company also wants to maximize the availability of compute capacity by allowing for flexibility in the specific EC2 instance types used, mitigating the risk of capacity unavailability for any single instance type.
Which approach meets all of these requirements MOST effectively?
Launch EC2 Spot Instances using an Auto Scaling group configured with a launch template. Configure the Auto Scaling group to launch instances into a Partition Placement Group spread across multiple Availability Zones.
Create an Auto Scaling group with On-Demand Instances launched into a Spread Placement Group across multiple Availability Zones. Use multiple instance types in the launch template's overrides.
Configure an EC2 Fleet with a Spot allocation strategy. Specify multiple instance types that meet the performance requirements and launch them into a single Cluster Placement Group within a single Availability Zone.
Use an EC2 Auto Scaling group with a mixed instances policy to launch instances into a Cluster Placement Group that spans multiple Availability Zones.
The correct answer is to use an EC2 Fleet with a Spot allocation strategy and launch instances into a Cluster Placement Group.
Cluster Placement Group: This is the only placement strategy that groups instances into a low-latency, high-throughput network within a single Availability Zone. This directly addresses the requirement for the lowest possible inter-node latency for a tightly-coupled High-Performance Computing (HPC) workload.
Spot Allocation Strategy: Since the workload is interruptible and cost-sensitive, Spot Instances are the most cost-effective compute pricing option.
EC2 Fleet with Multiple Instance Types: Using an EC2 Fleet (or an Auto Scaling group with a mixed instances policy) with multiple suitable instance types specified (e.g., using attribute-based instance selection) addresses the need for compute capacity resilience. If one instance type has limited Spot capacity, the fleet can provision other specified instance types, ensuring the workload can run.
Incorrect answers explained:
Partition Placement Group: This strategy is designed for large, distributed workloads like HDFS or Cassandra, where instances are spread across logical partitions on distinct hardware racks. It does not provide the lowest possible latency required for tightly-coupled workloads.
Spread Placement Group: This strategy places each instance on distinct underlying hardware to reduce correlated failures. This maximizes the availability of individual critical instances but increases inter-node latency, making it unsuitable for this use case.
Cluster Placement Group spanning multiple Availability Zones: This option is incorrect because a Cluster Placement Group, by design, cannot span multiple Availability Zones. This is a fundamental limitation that an architect must know when designing for low-latency networking.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a Cluster Placement Group in EC2?
Open an interactive chat with Bash
How does the Spot allocation strategy in EC2 Fleet work?
Open an interactive chat with Bash
Why can't a Cluster Placement Group span multiple Availability Zones?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Continuous Improvement for Existing Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access