SAA-C03 Design Cost-Optimized Architectures • Complete Question Bank
Complete SAA-C03 Design Cost-Optimized Architectures question bank — all 0 questions with answers and detailed explanations.
Drag a concept onto its matching description — or click a concept then click the description.
Amazon S3 Standard
Amazon S3 Standard-IA
Amazon S3 Glacier Instant Retrieval
Amazon S3 Glacier Deep Archive
Drag a concept onto its matching description — or click a concept then click the description.
Compute Savings Plan
Standard Reserved Instance
Spot Instances
On-Demand Instances
Drag a concept onto its matching description — or click a concept then click the description.
AWS Lambda
Amazon ECS on AWS Fargate
EC2 Spot Instances
EC2 On-Demand Instances
Drag a concept onto its matching description — or click a concept then click the description.
Gateway VPC endpoint
Interface VPC endpoint (AWS PrivateLink)
CloudFront with versioned objects and a long cache TTL
CloudFront Origin Shield
An application runs on EC2 in us-east-1 and frequently reads objects from an S3 bucket that is physically located in us-west-2. The finance team reports unexpectedly high inter-Region data transfer charges because the application retrieves objects for many user requests. A constraint: the bucket in us-west-2 must remain the system of record for compliance, but the application can read from a replica in us-east-1.
What should the solutions architect do to minimize network spend while meeting the compliance constraint?
A SaaS company uses an S3 bucket for database backups created daily. Backups are rarely restored; the company’s documented RTO is 24 hours, and the compliance policy requires backups be kept for 90 days. The team currently stores all backups in S3 Standard, which is costly.
Which single lifecycle policy change is most cost-optimized while still meeting the 24-hour RTO and 90-day retention?
A data engineering team runs a nightly ETL job on EC2. The job can be checkpointed every 5 minutes and can be retried from the last checkpoint if the instance terminates. The job runtime varies from 2 to 4 hours, and the team has no need for a specific instance type, as long as it completes before 7:00 AM local time. They currently run the job on On-Demand EC2, leading to high monthly compute cost.
Which change best reduces cost while maintaining the business deadline?
A marketing team runs a report-generation process that must execute once per day at 02:00 UTC. It usually completes in 10315 minutes, but sometimes takes up to 45 minutes due to varying data volumes. They currently run the workload on an EC2 instance that is always on, which wastes money during off-hours. The team wants to minimize operational overhead and pay mainly for actual execution time.
What is the best architecture choice?
A media company runs a 24/7 recommendation engine on EC2 in one AWS Region. The workload is interruption-intolerant, and the team expects steady usage but may change instance families and sizes during planned optimizations. Compared to the current On-Demand setup, they want the lowest cost while avoiding the rigidity of locking to a specific instance type.
What should the solutions architect recommend?
A company stores application logs in an S3 bucket. They retain logs for 180 days. Compliance requires that the logs be immutable once written, but the business only reviews logs about once per month. Currently, the team stores everything in S3 Standard, and their monthly S3 bill is too high. They want to reduce storage cost without changing the requirement to keep logs for 180 days.
Which lifecycle approach best meets the goal?
A marketing team runs a report-generation process that must execute once per day at 02:00 UTC. It usually completes in 10315 minutes, but sometimes takes up to 45 minutes due to varying data volumes. They currently run the workload on an EC2 instance that is always on, which wastes money during off-hours. The team wants to minimize operational overhead and pay mainly for actual execution time.
What is the best architecture choice?
An application runs on EC2 in us-east-1 and frequently reads objects from an S3 bucket that is physically located in us-west-2. The finance team reports unexpectedly high inter-Region data transfer charges because the application retrieves objects for many user requests. A constraint: the bucket in us-west-2 must remain the system of record for compliance, but the application can read from a replica in us-east-1.
What should the solutions architect do to minimize network spend while meeting the compliance constraint?
A SaaS company uses an S3 bucket for database backups created daily. Backups are rarely restored; the company’s documented RTO is 24 hours, and the compliance policy requires backups be kept for 90 days. The team currently stores all backups in S3 Standard, which is costly.
Which single lifecycle policy change is most cost-optimized while still meeting the 24-hour RTO and 90-day retention?
A data engineering team runs a nightly ETL job on EC2. The job can be checkpointed every 5 minutes and can be retried from the last checkpoint if the instance terminates. The job runtime varies from 2 to 4 hours, and the team has no need for a specific instance type, as long as it completes before 7:00 AM local time. They currently run the job on On-Demand EC2, leading to high monthly compute cost.
Which change best reduces cost while maintaining the business deadline?
A company stores application logs in an S3 bucket. They retain logs for 180 days. Compliance requires that the logs be immutable once written, but the business only reviews logs about once per month. Currently, the team stores everything in S3 Standard, and their monthly S3 bill is too high. They want to reduce storage cost without changing the requirement to keep logs for 180 days.
Which lifecycle approach best meets the goal?
A media company runs a 24/7 recommendation engine on EC2 in one AWS Region. The workload is interruption-intolerant, and the team expects steady usage but may change instance families and sizes during planned optimizations. Compared to the current On-Demand setup, they want the lowest cost while avoiding the rigidity of locking to a specific instance type.
What should the solutions architect recommend?
VPC: vpc-0a1b2c3d Private subnets: 10.0.10.0/24, 10.0.11.0/24 Route tables: 10.0.10.0/24 -> 0.0.0.0/0 -> nat-07fabc123 10.0.11.0/24 -> 0.0.0.0/0 -> nat-07fabc123 VPC Flow Logs (sample): 10.0.10.45 -> 52.216.23.11 ACCEPT 10.0.10.45 -> 54.239.28.85 ACCEPT 10.0.11.18 -> 52.94.76.21 ACCEPT Cost Explorer last 30 days: NATGateway-Hours: $31.20 NATGateway-Bytes: $614.80 App requirement: no internet access is needed; only AWS service access is required.
AWS Cost Explorer summary: Baseline web tier: 8 instances running 24/7, average utilization 35%-45% Nightly batch tier: 4 instances from 22:00-04:00 UTC Batch logs: 22:14 UTC: Spot interruption notice received 22:14 UTC: checkpoint saved to S3 22:17 UTC: job resumed on new instance Architecture notes: Batch jobs are restartable and tolerate interruption Operations wants freedom to switch instance families if needed
Current bucket: app-logs-prod Objects: compressed JSON logs, 150 GB per month Access pattern: Days 0-30: frequent reads for troubleshooting Days 31-120: occasional reads Days 121-400: rare reads, retrieval can take hours Compliance: retain all logs for 400 days, then delete Current storage class: S3 Standard for all objects Monthly S3 bill trend: rising steadily as log volume grows
CloudFront behavior summary: Origin: assets-prod.s3.amazonaws.com Cache policy: forwards all cookies, all query strings, and the Authorization header Origin request policy: forwards all headers Access logs: x-edge-result-type=Miss: 81% x-edge-result-type=Hit: 19% Object names: /static/app.v18a9f3.js /static/vendor.v18a9f3.css Request pattern: Many requests include Authorization: Bearer <token> Query strings are used only for analytics and do not affect file content
CloudWatch billing snapshot: Logs ingestion: moderate Logs storage: high Custom metrics: low Detailed monitoring charges: high EC2 fleet: 200 instances across 4 Auto Scaling groups Detailed monitoring enabled on every instance CloudWatch Logs groups: /app/prod/web: retention = Never Expire /app/prod/api: retention = Never Expire /app/prod/batch: retention = 365 days Compliance note: Keep logs available for at least 90 days No requirement for 1-minute EC2 metrics on all instances
Architecture inventory: 3 EC2 instances for RabbitMQ 2 EC2 instances for application workers Average broker CPU: 8%-12% Average broker memory: 18%-22% Monthly ops time spent on broker patching, backups, and failover testing: 14 hours Message requirements: Durable queueing At-least-once delivery acceptable No need for broker-managed topics or complex routing Failure note: A node reboot caused a 9-minute enqueue outage last month
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.