Courseiva

SAA-C03 Design Cost-Optimized Architectures Practice Question

A company keeps daily database backups in an S3 bucket. They may restore from backups during the first 30 days if there is an issue. After 30 days, backups are rarely restored, but must be retained for 2 years. Which lifecycle strategy most cost-effectively meets these requirements?

⚠ Common exam trap

A common mix-up: candidates assume immediate deletion (Option A) or immediate archiving (Option D) are acceptable, failing to recognize the dual requirement of frequent access in the first 30 days and long-term retention at minimal cost, which the lifecycle policy elegantly addresses.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use an S3 lifecycle policy to keep backups in S3 Standard for 30 days, then transition them to S3 Glacier Deep Archive for the remainder of the 2-year retention period.

It balances cost and compliance: backups are kept in S3 Standard for the first 30 days when restores are frequent, ensuring low-latency access, then transitioned to S3 Glacier Deep Archive for the remaining retention period. S3 Glacier Deep Archive offers the lowest storage cost (approximately $0.00099/GB/month) for long-term retention, and the lifecycle policy automates the transition without manual intervention. This approach minimizes storage costs while meeting the 2-year retention requirement.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Delete backups after 30 days to avoid storage costs, since restores are rare.

    Why it's wrong here

    Deleting backups after 30 days would violate the stated requirement to retain database backups for 2 years, likely breaking regulatory or business continuity obligations. Even if restores are rare, backups serve disaster recovery and audit needs; premature deletion means data can be permanently lost if a corruption is discovered later. S3 Lifecycle rules should never delete data before the retention window expires, and this option offers no path to meet the compliance mandate.

    When this WOULD be correct

    If the requirement were to only retain backups for 30 days with no longer-term retention needed, then deleting after 30 days would be the most cost-effective strategy.

  • ✗

    Keep all backups in S3 Standard for the entire 2-year retention period.

    Why it's wrong here

    Keeping all backups in S3 Standard for two years is unnecessarily expensive because S3 Standard offers high availability and low-latency access that are not needed for backups that are accessed rarely after the first month. Over a 24-month period, the per-GB storage cost of S3 Standard is roughly six times that of S3 Glacier Deep Archive, so this approach wastes significant budget without any compliance or operational benefit. S3 Lifecycle policies exist specifically to avoid this over-provisioning by transitioning data to appropriate storage classes over time.

    When this WOULD be correct

    If the requirement was to restore backups instantly at any time during the 2-year period with no retrieval delays, and cost was not a primary concern, then keeping all data in S3 Standard would be correct.

  • ✓

    Use an S3 lifecycle policy to keep backups in S3 Standard for 30 days, then transition them to S3 Glacier Deep Archive for the remainder of the 2-year retention period.

    Why this is correct

    This is correct because an S3 Lifecycle policy can automate the transition of objects after a specified number of days. Storing backups in S3 Standard for the first 30 days ensures rapid restoration during the period when failures are most likely to be detected, then transitioning to S3 Glacier Deep Archive for the remaining ~23 months meets the 2-year retention requirement at drastically lower storage cost. Lifecycle transitions are metadata operations, so they incur no retrieval charge, making this the most cost-effective and compliant approach.

  • ✗

    Move backups to S3 Glacier Deep Archive immediately after creation, even for the first 30 days.

    Why it's wrong here

    Immediately moving backups to S3 Glacier Deep Archive ignores the operational need for rapid restoration during the first 30 days; Deep Archive has a retrieval time of up to 12 hours, which is unacceptable for a recent backup that might be needed for urgent recovery. Additionally, S3 Glacier Deep Archive has a minimum storage duration of 90 days, so if you need to delete or move an object sooner, you'll incur an early-deletion charge. A lifecycle policy that delays the transition to Deep Archive balances both fast initial recovery and long-term cost efficiency.

    When this WOULD be correct

    If the requirement stated that backups are never restored within the first 30 days and must be retained for 2 years with the lowest possible storage cost, then moving them immediately to S3 Glacier Deep Archive would be the most cost-effective strategy.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.

✓Use an S3 lifecycle policy to keep backups in S3 Standard for 30 days, then transition them to S3 Glacier Deep Archive for the remainder of the 2-year retention period.Correct answer▾

Why this is correct

This is correct because an S3 Lifecycle policy can automate the transition of objects after a specified number of days. Storing backups in S3 Standard for the first 30 days ensures rapid restoration during the period when failures are most likely to be detected, then transitioning to S3 Glacier Deep Archive for the remaining ~23 months meets the 2-year retention requirement at drastically lower storage cost. Lifecycle transitions are metadata operations, so they incur no retrieval charge, making this the most cost-effective and compliant approach.

✗Delete backups after 30 days to avoid storage costs, since restores are rare.Wrong answer — click to see why▾

Why this is wrong here

This option fails to meet the requirement that backups must be retained for 2 years, as it deletes them after only 30 days.

★ When this WOULD be the correct answer

If the requirement were to only retain backups for 30 days with no longer-term retention needed, then deleting after 30 days would be the most cost-effective strategy.

Why candidates choose this

Candidates may focus solely on cost savings and overlook the explicit 2-year retention requirement, assuming that rare restores justify immediate deletion.

✗Keep all backups in S3 Standard for the entire 2-year retention period.Wrong answer — click to see why▾

Why this is wrong here

Keeping all backups in S3 Standard for 2 years incurs high storage costs for data that is rarely accessed after 30 days, making it not cost-effective.

★ When this WOULD be the correct answer

If the requirement was to restore backups instantly at any time during the 2-year period with no retrieval delays, and cost was not a primary concern, then keeping all data in S3 Standard would be correct.

Why candidates choose this

Candidates may think S3 Standard is the default safe choice and overlook the cost savings of transitioning to lower-cost storage classes for rarely accessed data.

✗Move backups to S3 Glacier Deep Archive immediately after creation, even for the first 30 days.Wrong answer — click to see why▾

Why this is wrong here

Moving backups to Glacier Deep Archive immediately after creation would incur retrieval costs and delays for restores during the first 30 days, when restores are common, making it less cost-effective and operationally unsuitable.

★ When this WOULD be the correct answer

If the requirement stated that backups are never restored within the first 30 days and must be retained for 2 years with the lowest possible storage cost, then moving them immediately to S3 Glacier Deep Archive would be the most cost-effective strategy.

Why candidates choose this

Candidates may assume that the cheapest storage class is always best, overlooking the need for quick and frequent access during the initial 30-day period.

Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

AWS S3 Storage Class Comparison

Storage ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

About these practice questions

Courseiva writes every SAA-C03 question from scratch — 935 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.