AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A retail company operates 15 AWS accounts in an AWS Organizations consolidated-billing setup. Across the organization, Auto Scaling groups in the us-east-1 Region keep at least 1,100 m7i.large instances running at all times. The workload is steady but engineering teams expect to migrate some services to newer instance families within the next 12 months after performance testing. Day-to-day traffic adds up to 400 additional instances that start and stop automatically, and the company's semi-annual flash-sale events require up to 50 % more capacity for 24 hours.
Finance has issued these requirements:
Maximize savings on the always-on capacity.
Allow transparent moves to a different instance family in the same Region without additional administration.
Keep purchasing and management centralized in the payer account; discounts must be shared with all member accounts.
Avoid operational risk from capacity reclaims during the flash-sale events.
Which purchasing strategy meets the requirements MOST cost-effectively?
Purchase 3-year Standard Reserved Instances for 1,100 m7i.large instances in each member account and use Spot Instances for additional capacity.
Purchase 3-year EC2 Instance Savings Plans for 1,500 m7i.large instances in each member account and rely on capacity rebalance to handle peaks.
Purchase 3-year Convertible Reserved Instances for 1,100 m7i.large instances in the payer account and use On-Demand Instances for the remaining capacity.
Purchase a 3-year, no-upfront Compute Savings Plan in the payer account sized to the 1,100-instance baseline and run any additional capacity On-Demand.
A Compute Savings Plan purchased in the payer account meets every requirement. Compute Savings Plans apply automatically to any EC2 usage in any Region and any instance family, so the discount continues to apply even after the workload transitions away from m7i.large. Because the plan is bought once at the management account level, its benefit is shared automatically with all linked accounts under consolidated billing, eliminating the need to manage reservations per account. A 3-year, no-upfront term maximizes the discount (up to 66 % compared with On-Demand) while requiring no further administration.
The dynamic daily workload and the two flash-sale days are left on On-Demand Instances. This avoids the interruption risk of Spot and prevents over-committing to reservations that might not be needed year-round.
Why the other options are not optimal:
Standard Reserved Instances or EC2 Instance Savings Plans lock the discount to the m7i family, so the planned migration would forfeit the reservation benefit or require repurchasing new reservations.
Convertible RIs allow exchanges but each change must be done manually, and the maximum discount (about 54 %) is lower than that of a Compute Savings Plan.
Covering variable capacity with Spot Instances would introduce the risk of interruption during mission-critical flash-sale periods.
Therefore, a single Compute Savings Plan sized for the 1,100-instance baseline, with excess capacity billed On-Demand, provides the best mix of savings, flexibility, and operational simplicity.
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 Compute Savings Plan in AWS?
Open an interactive chat with Bash
Why are Compute Savings Plans better than Reserved Instances for this scenario?
Open an interactive chat with Bash
Why are Spot Instances not ideal for flash-sale events?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access