SAP-C02 · Question #325
A company uses an on-premises data analytics platform. The system is highly available in a fully redundant configuration across 12 servers in the company's data center. The system runs scheduled…
The correct answer is D. Split the 12 instances across three Availability Zones in the chosen AWS Region. Run three. To achieve high availability for scheduled jobs and cost optimization for user jobs with a consumption-based model, the 12 EC2 instances should be split across three Availability Zones using a strategy that leverages On-Demand instances for critical workloads and Spot Instances…
Question
A company uses an on-premises data analytics platform. The system is highly available in a fully redundant configuration across 12 servers in the company's data center. The system runs scheduled jobs, both hourly and daily, in addition to one-time requests from users. Scheduled jobs can take between 20 minutes and 2 hours to finish running and have tight SLAs. The scheduled jobs account for 65% of the system usage. User jobs typically finish running in less than 5 minutes and have no SLA. The user jobs account for 35% of system usage. During system failures, scheduled jobs must continue to meet SLAs. However, user jobs can be delayed. A solutions architect needs to move the system to Amazon EC2 instances and adopt a consumption-based model to reduce costs with no long-term commitments. The solution must maintain high availability and must not affect the SLAs. Which solution will meet these requirements MOST cost-effectively?
Options
- ASplit the 12 instances across two Availability Zones in the chosen AWS Region. Run two
- BSplit the 12 instances across three Availability Zones in the chosen AWS Region. In one of the
- CSplit the 12 instances across three Availability Zones in the chosen AWS Region. Run two
- DSplit the 12 instances across three Availability Zones in the chosen AWS Region. Run three
How the community answered
(54 responses)- A15% (8)
- B6% (3)
- C26% (14)
- D54% (29)
Why each option
To achieve high availability for scheduled jobs and cost optimization for user jobs with a consumption-based model, the 12 EC2 instances should be split across three Availability Zones using a strategy that leverages On-Demand instances for critical workloads and Spot Instances for tolerant ones.
Distributing instances across only two Availability Zones offers less resilience against an AZ failure compared to three AZs, which is critical for meeting tight SLAs during system failures.
This option is incomplete, but similar to C, it proposes using three AZs, but the subsequent phrase "In one of the" does not suggest a complete or robust high-availability and cost-optimization strategy.
This option is incomplete, but similar to B, it proposes using three AZs, but "Run two" is less comprehensive than "Run three" in the context of potentially needing multiple instance types or scaling strategies for different workloads.
Splitting instances across three Availability Zones provides the highest level of redundancy against AZ failures, which is crucial for critical scheduled jobs, and "Run three" likely refers to a comprehensive strategy involving On-Demand instances for SLAs and Spot Instances for cost-saving user jobs.
Concept tested: High availability, Spot Instances, mixed workloads
Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances.html
Community Discussion
No community discussion yet for this question.