SAP-C03 · Domain 3: Cost-Optimized Architecture Design · 15% of the exam
Task 3.4: Optimize storage and database costs.
Cheaper data at rest: S3 and EFS tiering and lifecycle rules, EBS volume types and IOPS, database capacity modes, reserved capacity and Database Savings Plans, backup retention that costs less, and observability data filtered and kept only as long as needed.
Backup retention and observability data that cost less
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the AWS documentation page that proves it.
Question 1 · choose 1
A new Aurora PostgreSQL database will serve a workload that is quiet most of the day and spikes sharply at unpredictable times. The team wants capacity to follow demand automatically and to pay only for what it uses. Which configuration fits?
AA provisioned instance resized by a scheduled job
BAurora Serverless capacity for the DB instances
CThe largest provisioned instance class sized for the peak
DMore read replicas added by hand during spikes
Show the answer and why
AA provisioned instance resized by a scheduled job
Incorrect
Schedules cannot follow spikes that come at unpredictable times.
BAurora Serverless capacity for the DB instances
Correct
Aurora Serverless adjusts capacity automatically based on application demand, and you are charged only for the resources consumed.
CThe largest provisioned instance class sized for the peak
Incorrect
Sizing for the peak pays for unused capacity most of the day.
DMore read replicas added by hand during spikes
Incorrect
Manual changes are slow and replicas do not add write capacity.
A new records system writes documents to S3 that must be kept for ten years but are almost never read after 90 days, and retrieval within a few days is acceptable. Which approach keeps storage cost lowest?
AStore the documents on EBS volumes attached to a file server
BUse S3 Standard-IA for all ten years to keep retrieval fast
CKeep all documents in S3 Standard
DAdd a lifecycle rule to S3 Glacier Deep Archive after 90 days
Show the answer and why
AStore the documents on EBS volumes attached to a file server
Incorrect
Block storage costs more and is not suited to archives.
BUse S3 Standard-IA for all ten years to keep retrieval fast
Incorrect
Standard-IA costs more than archive classes for data that is almost never read.
CKeep all documents in S3 Standard
Incorrect
S3 Standard is priced for frequently accessed data.
DAdd a lifecycle rule to S3 Glacier Deep Archive after 90 days
Correct
Lifecycle rules can transition objects that do not need real-time access to S3 Glacier Deep Archive.
Long-term archives that are rarely read move to Deep Archive by lifecycle.
A new Aurora PostgreSQL cluster runs an I/O-heavy workload, and read and write I/O charges are 40% of the cluster's bill and vary month to month. Finance wants lower and more predictable database costs. Which change fits?
AMove the database to an RDS Single-AZ DB instance
BAdd more Aurora Replicas to spread the I/O
CSwitch the cluster to Aurora I/O-Optimized storage
DTurn on Aurora Backtrack
Show the answer and why
AMove the database to an RDS Single-AZ DB instance
Incorrect
This gives up Aurora's availability to change cost, and is not the direct fix.
BAdd more Aurora Replicas to spread the I/O
Incorrect
More replicas add instance cost; I/O is still charged per request.
CSwitch the cluster to Aurora I/O-Optimized storage
Correct
I/O-Optimized has no charges for read and write I/O and is the best choice when I/O spending is 25% or more of the Aurora bill.
DTurn on Aurora Backtrack
Incorrect
Backtrack is an Aurora MySQL feature that rewinds data; it does not change I/O pricing.
When I/O dominates Aurora cost, use I/O-Optimized storage.
A new orders table in Amazon DynamoDB will see steady traffic around the clock, mostly writes of new orders, with a daily peak about three times the baseline that builds over an hour, and growth of about 10% a month that the team can forecast reliably. Finance wants the table's throughput charges to follow a capacity plan it approves in advance rather than the number of requests served. Requests must not be throttled during the daily ramp, the team will not change capacity by hand, and capacity must not stay at peak level all day. Which configuration meets these requirements?
AProvisioned capacity mode with auto scaling, its minimum at the baseline and its maximum above the forecast peak
BOn-demand capacity mode with a maximum throughput setting at the forecast peak to cap the table's request rate
CProvisioned capacity mode set to the forecast peak all day, raised each month to match the growth forecast
DProvisioned capacity mode fixed at the baseline, with a DynamoDB Accelerator (DAX) cluster in front of the table for the peak
Show the answer and why
AProvisioned capacity mode with auto scaling, its minimum at the baseline and its maximum above the forecast peak
Correct
Provisioned tables are charged for the hourly capacity provisioned, not for the requests consumed, which gives cost predictability for steady workloads with forecastable growth. Auto scaling uses target tracking to move capacity between the minimum and maximum as traffic changes.
BOn-demand capacity mode with a maximum throughput setting at the forecast peak to cap the table's request rate
Incorrect
On-demand needs no capacity planning, and a maximum throughput setting caps how fast the table can be used. But on-demand charges for the requests served, which is the billing model finance does not want.
CProvisioned capacity mode set to the forecast peak all day, raised each month to match the growth forecast
Incorrect
Fixed provisioning at the peak avoids throttling and is predictable, but it pays for peak capacity around the clock and needs a manual change every month, which the team will not do.
DProvisioned capacity mode fixed at the baseline, with a DynamoDB Accelerator (DAX) cluster in front of the table for the peak
Incorrect
DAX is a write-through cache for eventually consistent reads and is not ideal for write-intensive applications. Every write still goes to the table first, so the peak's order writes would be throttled at baseline capacity.
The constraints are billing that follows an approved capacity plan, no throttling, no manual changes and no all-day peak capacity. On-demand bills per request even with a throughput cap, fixed peak provisioning wastes capacity and needs monthly edits, and a read cache does not absorb a peak made of writes. Provisioned capacity with auto scaling between the baseline and the peak meets every constraint.
A new platform template still provisions gp2 EBS volumes, and some are oversized only to get more IOPS. The team wants lower storage cost with the same performance. Which change fits?
AMove the volumes to io2 Block Express for consistent performance
BUse instance store for all volumes
CUse gp3 volumes with IOPS set independently of size
DMove the volumes to st1 HDD volumes
Show the answer and why
AMove the volumes to io2 Block Express for consistent performance
Incorrect
io2 is the highest-performance type for critical, IOPS-intensive workloads, more than this workload needs.
BUse instance store for all volumes
Incorrect
Instance store data is temporary and not suited to persistent volumes.
CUse gp3 volumes with IOPS set independently of size
Correct
gp3 lets you provision performance independently of volume size, at a 20 percent lower price per GiB than gp2.
DMove the volumes to st1 HDD volumes
Incorrect
Throughput-optimized HDD does not suit transactional workloads that need IOPS.
gp3 removes the need to oversize volumes for IOPS and costs less per GiB.
Every Monday a QA team restores the latest snapshot of a 6 TB production Aurora PostgreSQL cluster into 10 test environments. Each environment has its own AWS account in the same organization as the production account, and the key policy of the cluster's KMS key already lets these accounts use the key. The restores take hours, and storage for the 10 full copies is now one of the largest items on the QA bill, although each week's tests change less than 2% of the data. The testers need writable copies of recent production data in their own accounts, ready within minutes, and the tests must not run on the production instances. Finance wants the copies' storage cost cut sharply. Which solution meets these requirements?
AShare the production cluster with the 10 test accounts through AWS RAM and have each account create its own Aurora clone of the cluster
BKeep restoring the latest snapshot every week, but on smaller instance classes and with the copies kept for only five days
CAdd Aurora Replicas to the production cluster and point each test environment at the instance endpoint of its own replica
DExport the latest snapshot to Amazon S3 in Parquet each week and let the test environments query the export with Amazon Athena
Show the answer and why
AShare the production cluster with the 10 test accounts through AWS RAM and have each account create its own Aurora clone of the cluster
Correct
A clone starts by sharing data pages with its source through copy-on-write, so new storage is allocated only for changed data, and cloning is faster and more space-efficient than restoring a snapshot. A cluster shared through AWS RAM can be cloned by each authorized account, one cross-account clone per account and up to 15 per cluster, and each clone gets its own DB instances.
BKeep restoring the latest snapshot every week, but on smaller instance classes and with the copies kept for only five days
Incorrect
A restore creates a new DB cluster by physically copying the data, which is slower and uses more space than cloning, so each environment still stores a full copy while it exists. Smaller instances cut compute, not storage.
CAdd Aurora Replicas to the production cluster and point each test environment at the instance endpoint of its own replica
Incorrect
Replicas share the cluster volume, so they add no storage copies, but they are read-only instances inside the production cluster and account, while the testers need writable copies in their own accounts.
DExport the latest snapshot to Amazon S3 in Parquet each week and let the test environments query the export with Amazon Athena
Incorrect
Snapshot export writes compressed Parquet files that tools such as Athena can analyze, but tests that write to a PostgreSQL database cannot run against exported files.
The constraints are writable copies of recent data in each test account, ready in minutes, off the production instances, and far less storage. Snapshot restores are slow full copies, replicas are read-only and stay in the production cluster, and exported Parquet files are not a database. Sharing the cluster through AWS RAM lets each of the 10 accounts create one cross-account clone, well within the 15 allowed per cluster, and each clone stores only the pages its environment changes.
A data lake bucket encrypts objects with SSE-KMS under a customer managed key. Ingestion jobs write about a billion small objects a day, and analytics jobs read most of them within a week, so AWS KMS request charges are now larger than the S3 storage bill. Compliance requires that the data stay encrypted with that customer managed key under the company's key policy. The team wants the KMS request cost cut sharply without changing the ingestion or analytics code. Which change meets these requirements?
AChange the bucket's default encryption to SSE-S3 so that new objects no longer need any requests to AWS KMS
BSwitch the bucket's default encryption to DSSE-KMS with the same customer managed key for stronger protection
CRequest a higher AWS KMS request quota for the account so that the ingestion jobs are not throttled at peak
DTurn on S3 Bucket Keys for SSE-KMS in the bucket's default encryption with the same customer managed key
Show the answer and why
AChange the bucket's default encryption to SSE-S3 so that new objects no longer need any requests to AWS KMS
Incorrect
SSE-S3 adds no encryption fees, so it would remove the KMS charges, but the objects would no longer be protected by the company's customer managed key, which compliance requires.
BSwitch the bucket's default encryption to DSSE-KMS with the same customer managed key for stronger protection
Incorrect
DSSE-KMS applies two layers of encryption for standards that require multilayer encryption. It brings more KMS API calls and a higher cost than SSE-KMS, and S3 Bucket Keys are not supported with it.
CRequest a higher AWS KMS request quota for the account so that the ingestion jobs are not throttled at peak
Incorrect
KMS request quotas are adjustable through Service Quotas, which helps when calls are throttled. A higher quota does not lower the number of requests or their cost.
DTurn on S3 Bucket Keys for SSE-KMS in the bucket's default encryption with the same customer managed key
Correct
A bucket-level key reduces SSE-KMS request costs by up to 99 percent by cutting the request traffic from S3 to AWS KMS, while objects stay encrypted under the same KMS key. It needs no change to client applications and applies to new objects.
The constraints are the same customer managed key, a large cut in KMS request cost, and no code changes. SSE-S3 drops the required key, DSSE-KMS costs more and cannot use Bucket Keys, and a quota increase only allows more requests. S3 Bucket Keys keep SSE-KMS with the same key while sharply reducing calls to AWS KMS for the new objects that dominate this workload.
A provisioned DynamoDB table holds web session items that are useless 24 hours after they are created. Every night a job scans the whole table and deletes old items, and the read and write capacity it consumes has become a large part of the table's cost. The team wants to stop paying for these deletions and the scan, run no clean-up job at all, and make sure the application never treats an expired session as valid, even if an expired item is still in the table. Which solution meets these requirements?
ASwitch the table to on-demand capacity mode so that the nightly job no longer needs provisioned capacity set aside for it
BAdd a global secondary index on the creation date so that the job queries only old items instead of scanning the table
CTurn on TTL with an expiration timestamp on each item, and filter out expired items in the application's queries
DProcess the table's stream with a Lambda function that deletes each session item once it is older than 24 hours
Show the answer and why
ASwitch the table to on-demand capacity mode so that the nightly job no longer needs provisioned capacity set aside for it
Incorrect
On-demand mode removes capacity planning for the nightly burst, but the job would still run, and every read and delete it makes would still be billed as a request.
BAdd a global secondary index on the creation date so that the job queries only old items instead of scanning the table
Incorrect
A query on an index avoids reading the whole table, but the job still runs and issues every delete, and the index adds its own storage and write costs.
CTurn on TTL with an expiration timestamp on each item, and filter out expired items in the application's queries
Correct
DynamoDB deletes expired items automatically, without consuming write throughput, typically within a few days of expiration. Because expired items can be read until then, AWS advises filter expressions to remove them from query and scan results.
DProcess the table's stream with a Lambda function that deletes each session item once it is older than 24 hours
Incorrect
DynamoDB Streams captures item-level changes for processing, so the function could find old items without a scan, but its deletes still consume write capacity like any other delete.
The constraints are no paid deletes, no scan, no clean-up job, and no expired session accepted. On-demand mode, an index and a stream-driven function all keep a component that issues paid deletes. TTL deletes expired items without using write throughput, and filtering on the expiration attribute covers the days before an expired item is removed.