SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
SAA-C03 · Domain 4

Design Cost-Optimized Architectures practice questions

Design Cost-Optimized Architectures is worth 20% of the SAA-C03 exam — the lightest of the 4 domains. Cost-optimized storage, compute, database, and network designs, plus the cost-visibility tooling to govern spend. 6 fully worked examples are further down this page, answers included.

Exam weight
20%
the lightest of the 4 domains
Questions
112
across 4 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Design Cost-Optimized Architectures questions, fully explained

Questions from the SAA-C03 bank mapped to domain 4, with the answer key and the reasoning behind every option. None of them repeat the examples on the main SAA-C03 practice page.

Question 1Design Cost-Optimized Architectures

A healthcare provider archives diagnostic images to Amazon S3 for seven years. An image is retrieved roughly once per quarter, and when a physician requests one it must display in milliseconds. Which storage class is MOST cost-effective?

Choose one.

  • a
    S3 Standard-IA

    It provides millisecond access but at a higher storage price than Glacier Instant Retrieval; IA pricing is tuned for monthly access, not quarterly.

  • b
    S3 Glacier Instant Retrieval Correct

    It offers the lowest storage price of any class that keeps millisecond access, is designed for roughly quarterly access, and the seven-year retention clears its 90-day minimum easily.

  • c
    S3 Glacier Flexible Retrieval

    It stores data cheaply but restores asynchronously in minutes to hours, violating the millisecond display requirement.

  • d
    S3 Glacier Deep Archive

    It is the cheapest storage but restores take around 12 hours, which fails the requirement that images display immediately.

The concept

Glacier Instant Retrieval keeps millisecond access at the lowest storage price that still allows it, targeting data accessed about once a quarter, with a 90-day minimum storage duration and a retrieval fee.

Why that’s the answer

The requirements are quarterly access, millisecond retrieval, and seven-year retention. Millisecond retrieval immediately vetoes both asynchronous Glacier tiers: Flexible Retrieval restores in minutes to hours and Deep Archive in about 12 hours, so their lower storage prices are irrelevant, since a cheaper option that breaks a stated requirement is wrong. Between the two synchronous survivors, Glacier Instant Retrieval stores data cheaper than Standard-IA and its retrieval fees are priced for exactly this quarterly pattern, and the 90-day minimum duration is trivially satisfied by seven-year retention. Standard-IA over-pays on storage for an access frequency lower than the monthly pattern it targets.

How to reason it out
  1. Apply the retrieval-tolerance veto first: milliseconds are required, eliminating Glacier Flexible Retrieval and Deep Archive.
  2. Compare the remaining synchronous classes on the stated frequency: quarterly access matches Glacier Instant Retrieval; monthly access would match Standard-IA.
  3. Verify the minimum-duration trap: seven years far exceeds the 90-day minimum, so no penalty applies.
  4. Choose Glacier Instant Retrieval as the cheapest class meeting every stated requirement.

Exam tip: When milliseconds are required, only Standard, the IA classes, and Glacier Instant Retrieval qualify; quarterly frequency selects Glacier Instant Retrieval.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

Question 2Design Cost-Optimized Architectures

A solutions architect reviews an S3 bucket that contains three datasets, all in their current classes for a year: a working dataset that analysts query every day (S3 Standard); compliance reports read about once a month that must open immediately (S3 Standard); and temporary files that a job deletes 7 days after creation (S3 Standard-IA). Which TWO changes reduce S3 costs without violating any access requirement? (Select TWO.)

Choose TWO.

  • a
    Transition the compliance reports to S3 Standard-IA. Correct

    Monthly access with immediate reads is exactly the Standard-IA pattern: much lower storage cost, and the small retrieval fees at monthly frequency are far below the savings.

  • b
    Move the temporary files from S3 Standard-IA back to S3 Standard. Correct

    Files deleted at 7 days trip Standard-IA's 30-day minimum duration, billing 23 phantom days per object; Standard has no minimum and is cheaper for this data.

  • c
    Transition the working dataset to S3 Standard-IA.

    Daily queries would generate per-GB retrieval fees that swamp the storage savings; frequently accessed data belongs in Standard.

  • d
    Transition the compliance reports to S3 Glacier Deep Archive.

    Deep Archive restores take around 12 hours, violating the requirement that reports open immediately.

  • e
    Move the temporary files to S3 One Zone-IA.

    One Zone-IA carries the same 30-day minimum duration as Standard-IA, so 7-day data still pays the minimum-duration surcharge.

The concept

Cost-optimal class selection can mean moving data down to a cheaper class or moving it back up: minimum-duration and retrieval-fee traps make an infrequent-access class the expensive choice for short-lived or frequently read data.

Why that’s the answer

The compliance reports are the textbook Standard-IA fit: monthly access, immediate reads required, retained long past the 30-day minimum, so transitioning them saves real money. The temporary files are in the wrong direction entirely: at 7-day retention, Standard-IA's 30-day minimum bills 23 unused days per object, so returning them to Standard, which has no minimum, is a cost reduction. The working dataset must stay in Standard because daily retrieval fees in any IA class would exceed the storage savings. Deep Archive for the reports fails the immediate-access requirement, and One Zone-IA for the temp files keeps the same 30-day minimum-duration trap while adding single-AZ risk.

How to reason it out
  1. Classify each dataset by access frequency and retention: daily access, monthly access with immediate reads, and 7-day-lifetime files.
  2. Match monthly-plus-immediate to Standard-IA and transition the reports.
  3. Check the temp files against IA's 30-day minimum: 7-day retention fails it, so move them back to Standard.
  4. Reject IA for the daily dataset by pricing the retrieval fees mentally.
  5. Reject Deep Archive wherever immediate access is stated.

Exam tip: IA classes save money only when data is both long-lived and rarely read; otherwise Standard is the cheaper class.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

Question 3Design Cost-Optimized Architectures

A startup is launching a data lake in Amazon S3. Nobody can predict which objects will stay in heavy use and which will go cold, and objects that go cold sometimes become popular again. The team wants the lowest storage cost without anyone having to tune rules over time. Which approach is MOST cost-effective?

Choose one.

  • a
    Upload the objects directly to S3 Standard-IA and keep them in that storage class.

    Objects that stay in heavy use would pay a per-GB retrieval fee on every read, which can easily exceed the storage saving.

  • b
    Upload the objects to S3 Standard and add a lifecycle rule that transitions them to S3 Glacier Flexible Retrieval after 90 days.

    Objects that become popular again would need a restore before every read and pay retrieval fees; lifecycle transitions never move an object back to a faster tier.

  • c
    Upload the objects directly to S3 Intelligent-Tiering and keep them in that storage class. Correct

    It moves each object between access tiers based on its own access, moves reheated objects back to the frequent tier automatically, and charges no retrieval fees or minimum-duration charges.

  • d
    Upload the objects to S3 Standard and add a lifecycle rule that transitions them to S3 Standard-IA after 30 days.

    Age-based transitions assume every object cools at the same rate; objects still in heavy use after 30 days would pay retrieval fees, and the rule never moves reheated objects back.

The concept

S3 Intelligent-Tiering monitors each object and moves it between tiers by its actual access, in both directions, for a small per-object monitoring fee and with no retrieval fees or minimum-duration charges.

Why that’s the answer

The deciding facts are that access is unpredictable per object and that cold objects can reheat. Lifecycle rules work on object age, not access, and only ever move data down to cheaper tiers, so any age-based rule either leaves cold objects in Standard too long or pushes hot ones into a class that bills retrievals. A blanket Standard-IA choice punishes the hot objects with retrieval fees. Intelligent-Tiering decides per object from real access, moves reheated objects back up automatically, and needs no rule tuning.

How to reason it out
  1. Notice the access pattern: unpredictable per object, and cold objects can become hot again.
  2. Reject age-based lifecycle rules: they cannot tell hot objects from cold ones and never move data back up.
  3. Reject a single infrequent-access class: hot objects would pay retrieval fees.
  4. Choose Intelligent-Tiering, which tiers each object by its own access with no retrieval fees.

Exam tip: Unknown or changing access per object is the Intelligent-Tiering pattern; lifecycle rules suit predictable, age-based cooling.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

Question 4Design Cost-Optimized Architectures

A media platform stores user-generated videos in Amazon S3. Some videos stay popular for years, while others go cold within weeks and occasionally trend again months later. The same pipeline also writes millions of metadata records of 2-8 KB each, one S3 object per record. Which TWO actions produce the MOST cost-effective storage design? (Select TWO.)

Choose TWO.

  • a
    Create a lifecycle rule that transitions the videos to S3 Standard-IA 30 days after upload.

    Videos that stay popular or trend again would pay a retrieval fee on every view, and lifecycle transitions never move an object back to a tier without retrieval fees.

  • b
    Upload the videos directly to S3 Glacier Instant Retrieval and keep them in that class.

    Glacier Instant Retrieval is priced for data read about once a quarter; popular videos would pay its retrieval fee on every view.

  • c
    Store the videos in S3 Intelligent-Tiering. Correct

    It moves each video between tiers based on its own access and moves a reheated video back to the frequent tier automatically, with no retrieval fee when an old video trends again.

  • d
    Store the small metadata objects in S3 One Zone-IA to lower their per-GB price.

    The IA classes bill each object as at least 128 KB, so a 4 KB record is charged as 128 KB and costs far more than in Standard; the per-object request charges are untouched.

  • e
    Batch the small metadata records into larger aggregated objects before uploading them. Correct

    Fewer, larger objects cut the per-request PUT charges, and objects above 128 KB can then be tiered; small objects otherwise stay at the frequent-access rate in Intelligent-Tiering.

The concept

Intelligent-Tiering handles unpredictable, bidirectional access per object, but objects under 128 KB are not monitored or tiered, and the IA classes bill a 128 KB minimum object size. Tiny objects are made cheaper by aggregating them, not by choosing a class.

Why that’s the answer

The videos show the exact pattern Intelligent-Tiering exists for: some hot for years, others cold quickly but occasionally reheating, which a one-way lifecycle rule or a hand-picked infrequent class punishes with retrieval fees. The metadata records are a separate problem. At 2-8 KB, every IA class would bill each record as 128 KB, and Intelligent-Tiering would leave them at the frequent-access rate. Batching them into larger objects cuts the number of PUT requests and makes the data large enough to tier. One Zone-IA looks cheapest per GB but is the most expensive option for tiny objects.

How to reason it out
  1. Identify the video access pattern as unpredictable and bidirectional, which selects Intelligent-Tiering.
  2. Reject one-way lifecycle transitions and fixed infrequent classes, because reheated videos would pay retrieval fees.
  3. Check the metadata object size against the 128 KB minimum billable size of the IA classes.
  4. Aggregate the small records into larger objects to cut request charges and make tiering effective.

Exam tip: Intelligent-Tiering for unpredictable objects; batch tiny objects into larger ones, because IA classes bill them as 128 KB.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

Question 5Design Cost-Optimized Architectures

A company stores customer statements in S3. Each statement is opened often in its first 30 days, then a few times a month for the next 11 months, and those opens must be immediate. Statements must then be retained for 6 more years for auditors who accept retrievals taking up to 12 hours, and deleted at the end of year 7. Which lifecycle design is MOST cost-effective?

Choose one.

  • a
    Store statements in S3 Standard; transition to S3 Glacier Instant Retrieval at 30 days, to S3 Glacier Deep Archive at 365 days, and expire them at 7 years.

    Glacier Instant Retrieval stores more cheaply but charges about three times Standard-IA's per-GB retrieval fee, so opening each statement a few times a month costs more than the storage it saves.

  • b
    Store statements in S3 Standard; transition to S3 Glacier Instant Retrieval at 30 days, to S3 Glacier Flexible Retrieval at 365 days, and expire them at 7 years.

    This pays Glacier Instant Retrieval's high retrieval fees for monthly opens and then Glacier Flexible Retrieval's higher storage rate for an archive phase that tolerates 12-hour restores.

  • c
    Store statements in S3 Standard; transition to S3 Standard-IA at 30 days, to S3 Glacier Flexible Retrieval at 365 days, and expire them at 7 years.

    The first two phases are right, but Glacier Flexible Retrieval stores at a higher price than Deep Archive, and the auditors' 12-hour tolerance means nothing justifies paying for faster restores.

  • d
    Store statements in S3 Standard; transition to S3 Standard-IA at 30 days, to S3 Glacier Deep Archive at 365 days, and expire them at 7 years. Correct

    Each phase lands in the cheapest class that meets it: Standard for frequent opens, Standard-IA for immediate reads a few times a month, and Deep Archive, whose standard restores finish within 12 hours, for the audit years.

The concept

A lifecycle waterfall assigns each phase of an object's life to the cheapest class that meets that phase's access pattern, weighing storage price against per-GB retrieval fees, then checks each archive tier against the stated retrieval tolerance.

Why that’s the answer

Phase one is frequent access, so S3 Standard avoids retrieval fees. Phase two needs immediate opens a few times a month. Both Standard-IA and Glacier Instant Retrieval read in milliseconds, but at us-east-1 list prices Standard-IA ($0.0125 per GB-month plus $0.01 per GB retrieved) beats Glacier Instant Retrieval ($0.004 plus $0.03 per GB retrieved) once more than about 0.4 of the data is read each month, and reading each statement several times a month is far above that. Phase three tolerates 12-hour retrievals, which Deep Archive's standard restores meet, and six years clear its 180-day minimum many times over, so the cheapest S3 class is the right archive. The expiration action enforces the 7-year deletion. Glacier Flexible Retrieval works in the archive phase but buys restore speed no requirement asks for.

How to reason it out
  1. Map the three phases: frequent for 30 days, immediate reads a few times a month to year 1, archival with 12-hour tolerance to year 7.
  2. For the middle phase, compare the two millisecond classes on storage plus retrieval cost at the stated read rate; frequent monthly reads favour Standard-IA.
  3. For the archive phase, match the 12-hour tolerance to Deep Archive and confirm six years clears its 180-day minimum.
  4. Add an expiration action at 7 years to enforce deletion.

Exam tip: Instant-read classes trade storage price for retrieval fees: reads every month favour Standard-IA, reads a few times a year favour Glacier Instant Retrieval.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

Question 6Design Cost-Optimized Architectures

A versioned S3 bucket is billed for eight times the size of its live dataset, which has been stable for months because objects are overwritten daily. Governance requires versioning to stay enabled, every overwritten version to be recoverable for 30 days, and the three most recent previous versions of each object to be kept indefinitely. Which change reduces storage costs the MOST while meeting these requirements?

Choose one.

  • a
    Add a lifecycle rule that transitions noncurrent versions to S3 Glacier Deep Archive 30 days after they become noncurrent.

    This lowers the per-GB price of old versions but keeps every one of them forever, so the version count keeps growing; deleting the versions governance does not need saves more.

  • b
    Add a lifecycle rule that expires current versions 30 days after creation and keeps the three newest noncurrent versions.

    Expiring current versions on a versioned bucket adds delete markers that hide the live data from applications, and it does nothing to remove old noncurrent versions.

  • c
    Add a lifecycle rule that transitions current versions to S3 Standard-IA 30 days after creation and leaves the noncurrent versions as they are.

    The live data is overwritten daily, so current versions rarely reach 30 days, and the noncurrent versions that cause the growth are left untouched.

  • d
    Add a lifecycle rule that expires noncurrent versions 30 days after they become noncurrent and keeps the three newest noncurrent versions. Correct

    NoncurrentVersionExpiration with NoncurrentDays set to 30 and NewerNoncurrentVersions set to 3 deletes old versions after the 30-day recovery window while always retaining the three most recent ones.

The concept

Versioning keeps every overwritten or deleted version, billed at full price, until a lifecycle rule acts on noncurrent versions. NoncurrentVersionExpiration can delete versions a set number of days after they become noncurrent while retaining a set number of newer noncurrent versions.

Why that’s the answer

A bucket billed for many times its live size, with a stable live dataset and frequent overwrites, is accumulating noncurrent versions. The governance rules map exactly onto one lifecycle action: expire noncurrent versions 30 days after they become noncurrent (the recovery window) and retain the three newest noncurrent versions (the indefinite keep). Transitioning noncurrent versions to Deep Archive is the tempting alternative because it is cheap per GB, but it keeps every version forever, so the bill keeps climbing. Expiring current versions confuses the two version types and hides live data behind delete markers. Tiering current versions misses the growth entirely.

How to reason it out
  1. Diagnose the growth: stable live data, daily overwrites and a versioned bucket mean noncurrent versions are accumulating.
  2. Map each governance rule to a lifecycle setting: the 30-day recovery window becomes NoncurrentDays, and the three kept versions become NewerNoncurrentVersions.
  3. Compare deleting with archiving: archiving lowers the rate but keeps an ever-growing number of versions.
  4. Reject any rule that acts on current versions, which are not the source of the growth.

Exam tip: Versioned-bucket growth is fixed with noncurrent-version expiration; NewerNoncurrentVersions keeps the last few versions safe.

Cost-Optimized Storage: S3 Classes, Lifecycle Policies, and EBS Economics — the lesson that teaches this.

What SAA-C03 domain 4 tests, topic by topic

The official exam guide breaks Design Cost-Optimized Architectures into 4 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published SAA-C03 practice questions per topic in Design Cost-Optimized Architectures
TopicWhat it coversQuestions
Design cost-optimized storage solutionsExam guide task 4.1. Cost tooling (Cost Explorer, AWS Budgets, Cost and Usage Report, cost allocation tags, multi-account billing); S3 storage classes, lifecycle tiering, and Requester Pays; block storage volume-type economics (HDD vs SSD); choosing the lowest-cost storage service, size, migration/transfer method, and backup/archival solution; storage auto scaling.28
Design cost-optimized compute solutionsExam guide task 4.2. Purchasing options (Spot Instances, Reserved Instances, Savings Plans); instance family selection and right-sizing; Lambda vs EC2 vs Fargate cost trade-offs; containers, serverless, and microservices for utilization; hybrid compute options (Outposts); scaling strategies (horizontal vs vertical, EC2 hibernation) and load-balancer choice (ALB layer 7 vs NLB layer 4 vs Gateway LB) against each workload’s availability needs.28
Design cost-optimized database solutionsExam guide task 4.3. Cost-effective database services and types (DynamoDB vs RDS, serverless, time series, columnar) and engine selection; backup retention and snapshot-frequency policy design; caching to reduce database spend; capacity planning; homogeneous vs heterogeneous migrations across locations and engines.28
Design cost-optimized network architecturesExam guide task 4.4. NAT gateway cost strategies (single shared vs per-AZ, NAT instance vs NAT gateway); connectivity choices (Direct Connect vs VPN vs internet); minimizing data-transfer costs via routing (Region-to-Region, AZ-to-AZ, private vs public), VPC endpoints, Transit Gateway, and VPC peering; CDN/edge caching needs; throttling strategy and bandwidth allocation (single vs multiple VPNs, Direct Connect speed).28
Total112

Revise Design Cost-Optimized Architectures before you drill it

Other SAA-C03 domains

Design Cost-Optimized Architectures: your questions

Design Cost-Optimized Architectures is domain 4 of the SAA-C03 exam guide and carries 20% of the scored content — the lightest of the 4 domains. On a 65-question paper that works out to roughly 13 questions, though AWS does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official SAA-C03 exam guide.