Courseiva
← Back to SAA-C03 questions

Scenario-based practice

Refer to the Exhibit Practice Questions

Practise SAA-C03 practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

15
scenario questions
SAA-C03
exam code
Amazon Web Services
vendor

Scenario guide

How to approach refer to the exhibit practice questions

Practise exhibit-style questions that ask you to read a topology, table, command output or diagram before choosing the best answer.

Quick answer

Exhibit-style questions test whether you can read a topology, command output, diagram or table before choosing the best answer.

How to extract the relevant detail from an exhibit.

How topology, command output or routing information affects the answer.

How to avoid answering from memory before reading the evidence.

How to map the exhibit back to the exam objective.

Related practice questions

Related SAA-C03 topic practice pages

Scenario questions usually connect to one or more exam topics. Use these links to review the underlying concepts behind the scenario.

Practice set

Practice scenarios

Question 1hardmultiple choice
Read the full DNS explanation →

Based on the exhibit, DNS still sends traffic to the primary Region even though Route 53 health checks show the primary endpoint is unhealthy. What is the best change to make failover work as intended?

Exhibit

Route 53 record sets for app.example.com:
- Record 1: Type A, RoutingPolicy=Simple, AliasTarget=alb-use1.amazonaws.com
- Record 2: Type A, RoutingPolicy=Simple, AliasTarget=alb-usw2.amazonaws.com

Health check status:
hc-primary: FAILED
hc-secondary: HEALTHY

Resolver test:
$ dig +short app.example.com
alb-use1.amazonaws.com

Ops note:
The intent is to send all traffic to us-east-1 normally and fail over to us-west-2 only when the primary is unhealthy.
Question 2hardmultiple choice
Full question →

Based on the exhibit, a serverless API on AWS Lambda experiences a predictable cold-start penalty every weekday at 09:00 UTC when a marketing campaign begins. The team wants the first requests to stay fast while minimizing extra cost during quiet periods. What is the best approach?

Exhibit

Lambda monitoring and deployment notes:
- Function: checkout-api-prod
- Current alias: live
- Invocations per day: low except weekdays 09:00-09:15 UTC
- REPORT log sample at 09:00 UTC:
  Init Duration: 842.31 ms
  Duration: 128.42 ms
  Billed Duration: 1000 ms
- REPORT log sample at 09:05 UTC:
  Init Duration: 0.00 ms
  Duration: 121.77 ms

Traffic pattern:
- Spikes are predictable and last about 15 minutes
- No need to keep high concurrency all day
Question 3mediummultiple choice
Full question →

Based on the exhibit, the web application must remain available even if one Availability Zone fails. What is the best change to improve resilience with the least redesign?

Exhibit

Application Load Balancer
  Subnets: subnet-a1 (us-east-1a), subnet-b1 (us-east-1b)
Auto Scaling group
  VPCZoneIdentifier: subnet-a1 (us-east-1a)
  DesiredCapacity: 2
  MinSize: 2
  MaxSize: 4
CloudWatch
  HealthyHostCount: 2
  HTTPCode_Target_5XX_Count: 0
Troubleshooting note
  A planned test that disabled us-east-1a caused the application to become unreachable.
Question 4hardmultiple choice
Full question →

Based on the exhibit, the company wants to lower CloudWatch and EC2 monitoring costs. Auditors require logs to be retained for 90 days, but operations only uses detailed per-instance metrics during rare troubleshooting events. Which change best reduces recurring cost while preserving the required visibility?

Exhibit

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
Question 5easymultiple choice
Full question →

Based on the exhibit, the database must fail over automatically if the primary Availability Zone goes down. Which solution should the architect choose?

Exhibit

Amazon RDS configuration:
- Engine: MySQL
- Deployment: Single-AZ
- Backup retention: 7 days
- Application connection string: db-prod.cluster-abcdefghijkl.us-east-1.rds.amazonaws.com

Operations note:
- During maintenance, the database endpoint stayed reachable only after a manual restore from snapshot.
Question 6hardmultiple choice
Full question →

Based on the exhibit, a DynamoDB-backed event processing system is throttling during a promotion. The table uses tenantId as the partition key and eventTime as the sort key. One tenant accounts for most of the write traffic, and the application must preserve fast lookups for that tenant without relying on a single hot partition. What change is the best fix?

Exhibit

Table schema:
- TableName: EventStore
- PartitionKey: tenantId (String)
- SortKey: eventTime (Number)

CloudWatch metrics during promotion:
- WriteThrottleEvents: increasing steadily
- ConsumedWriteCapacityUnits: near provisioned limit
- SuccessfulRequestLatency p95: 14 ms

Sample traffic distribution:
- tenantId=ACME: 82% of writes, 79% of reads
- all other tenants combined: 18% of writes, 21% of reads

Application note:
- Queries must continue to support tenant-scoped lookups by time range.
Question 7mediummultiple choice
Full question →

Based on the exhibit, what is the most appropriate change to restore application access while keeping encryption at rest with customer-managed KMS controls?

Exhibit

Application log excerpt:

2026-04-11T09:14:22Z ERROR S3 GetObject failed: AccessDenied
2026-04-11T09:14:22Z ERROR KMS Decrypt failed for key arn:aws:kms:us-east-1:111122223333:key/abcd-1234

Current setup:
- S3 bucket default encryption: SSE-KMS
- EC2 application role: AppServerRole
- Bucket policy allows s3:GetObject for AppServerRole
- KMS key policy currently allows only the account root principal
- No direct KMS permissions are attached to AppServerRole
Question 8mediummultiple choice
Full question →

Based on the exhibit, a faulty deployment corrupted production data at 10:30 UTC and the issue was discovered at 10:55 UTC. The team needs to recover the database to the last good state before the corruption. Which action should they take?

Exhibit

RDS backup configuration:
  Automated backups: enabled
  Backup retention: 14 days
  Latest manual snapshot: 2026-04-18 02:00 UTC

Operations log:
  10:30 UTC - schema migration started
  10:36 UTC - application errors began
  10:55 UTC - corrupted rows discovered

Requirement:
  Restore to a point before the bad migration without losing the entire day of changes
Question 9mediummultiple choice
Full question →

Based on the exhibit, the application team wants the database to keep the same connection endpoint during failover and to reconnect automatically after the primary instance becomes unavailable. Which change best meets the requirement?

Exhibit

application.properties:
  spring.datasource.url=jdbc:mysql://10.0.12.55:3306/orders
  spring.datasource.username=appuser
  spring.datasource.password=****

RDS event log:
  2026-04-12T03:14:22Z db-1 - Failover started
  2026-04-12T03:15:01Z db-1 - Primary unavailable
  2026-04-12T03:16:10Z app-server-2 - SQLRecoverableException: Communications link failure

Current deployment:
  Amazon RDS for MySQL, Multi-AZ enabled
  Application instances in two AZs
  Connection string uses an IP address that was entered manually
Question 10hardmultiple choice
Full question →

Based on the exhibit, the application tier is not replacing unhealthy instances even though the Auto Scaling group spans two Availability Zones. What change most directly improves automatic recovery when the application process fails?

Network Topology
$ aws autoscaling describe-auto-scaling-groupsauto-scaling-group-names orders-asg$ aws elbv2 describe-target-healthtarget-group-arn arn:aws:elasticloadbalancing:us-east-1:111122223333:targetgroup/orders-tg/abcd1234"AutoScalingGroups": ["AutoScalingGroupName": "orders-asg","DesiredCapacity": 4,"MinSize": 4,"MaxSize": 8,"AvailabilityZones": ["us-east-1a", "us-east-1b"],"HealthCheckType": "EC2","HealthCheckGracePeriod": 300,"TargetGroupARNs": ["arn:aws:elasticloadbalancing:us-east-1:111122223333:targetgroup/orders-tg/abcd1234"]TARGETSi-01e2a3b4: healthyi-02e3b4c5: healthyi-03f4c5d6: unhealthyi-04a5d6e7: unhealthyApplication health endpoint:2026-04-27T13:05:22Z GET /health -> 500EC2 status checks: passing
Question 11hardmultiple choice
Full question →

Based on the exhibit, the team must restore an Amazon RDS for PostgreSQL database to the exact state just before a bad delete happened. What is the best recovery approach?

Exhibit

RDS backup status:
- Automated backups: Enabled
- Backup retention period: 14 days
- Latest automated snapshot: 2026-04-27 09:00 UTC
- Latest restorable time: 2026-04-27 15:14 UTC

Incident timeline:
- 2026-04-27 15:11 UTC: deployment script accidentally deleted critical rows
- 2026-04-27 15:12 UTC: application detected missing data
- Required restore point: 2026-04-27 15:10 UTC

Operations note:
The business wants to recover to a new database first, verify data, and then cut over the application.
Question 12hardmultiple choice
Full question →

Based on the exhibit, the team wants to minimize compute cost for a workload with a steady 24/7 baseline and a separate nightly batch job that can be interrupted and resumed from checkpoints. They also expect to change EC2 instance families during the year as performance needs evolve. Which approach is the best fit?

Exhibit

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
Question 13mediummultiple choice
Read the full DNS explanation →

Based on the exhibit, the company wants DNS traffic to fail over automatically from the primary Region to a secondary Region when the primary endpoint is unhealthy. Which Route 53 change is best?

Exhibit

Route 53 record set
  Name: app.example.com
  Type: A (Alias)
  Routing policy: Simple
  Alias target: alb-primary-123.us-east-1.elb.amazonaws.com
  TTL: 60 seconds
Health check
  ID: hc-44
  Status: Inactive
Secondary environment
  ALB target exists in us-west-2: alb-secondary-456.us-west-2.elb.amazonaws.com
Operational note
  A Region outage should shift users to the secondary ALB without manual DNS changes.
Question 14mediummultiple choice
Full question →

Based on the exhibit, which AWS service should the team use so the database password can rotate automatically every 30 days and the application can retrieve it securely at runtime?

Exhibit

Application configuration excerpt:

DB_HOST=db-prod.abc123.us-east-1.rds.amazonaws.com
DB_USER=app_user
DB_PASSWORD=stored_in_env_var

Operational requirement:
- Password must rotate automatically every 30 days
- Application should retrieve the current password securely when starting connections
- Security wants a managed service that stores versions of the secret and supports rotation workflows
Question 15mediummultiple choice
Full question →

Based on the exhibit, the team wants to stop poison messages from consuming worker capacity and also prevent duplicate side effects if the same message is delivered more than once. Which design change best meets the requirement?

Exhibit

SQS queue attributes:
  VisibilityTimeout = 30 seconds
  RedrivePolicy = not configured

CloudWatch Logs:
  14:02:11 worker-a received messageId=7b2c8f4a
  14:02:43 worker-a started payment write for order 9912
  14:03:04 worker-a message visible again before delete
  14:03:11 worker-b received messageId=7b2c8f4a
  14:03:18 worker-b repeated payment write for order 9912

Application note:
  Average handler duration is 42-55 seconds during peak load

These SAA-C03 practice questions are part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style SAA-C03 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.