Design around failure
Compare multi-AZ deployments, decoupled components and recovery strategies against a workload’s availability needs.
SAA-C03 · Associate
Build the judgment to choose secure, resilient AWS architectures—and explain why they fit.
Your free account includes a full SAA-C03 practice exam.
ExamNova practice
Practise, review your answers and see where to focus next.
Preview a questionFor people moving into solution design or strengthening an existing AWS architecture role. The work is choosing between plausible designs when availability, performance, security and cost pull in different directions.
Compare multi-AZ deployments, decoupled components and recovery strategies against a workload’s availability needs.
Reason through identity policies, network isolation, encryption and cross-account access.
Match compute, storage and database services to access patterns, scale and operating cost.
Explore the domains and topics in your ExamNova study path.
Explore Design Secure Architectures
Explore Design Resilient Architectures
Explore Design High-Performing Architectures
Explore Design Cost-Optimized Architectures
Percentages show ExamNova’s practice balance. Consult the official guide for the vendor’s current exam outline.
Explore a topic with sample questions and explanations.
Read the scenario. Consider your answer, then reveal the reasoning.
When reviewing a scenario, identify the requirement that rules each alternative out. Knowing a service name is only the first step.
A media service is comparing a DynamoDB table in on-demand capacity mode with a single-Region MemoryDB for Redis OSS cluster. Which TWO statements correctly describe current direct pricing considerations for these specific configurations?
MemoryDB for Redis OSS receives Valkey's data-written allowance, so node-hours include its first 10 TB written each month. — MemoryDB pricing distinguishes the Valkey and Redis OSS engines. The advertised Valkey allowance for data written cannot be transferred to this Redis OSS estimate, whose data-written volume remains a direct pricing meter in addition to node-hours.
DynamoDB on-demand bills read and write request units without requiring provisioned read or write throughput. — DynamoDB on-demand automatically manages throughput capacity and bills reads and writes as request units. Storage and optional features can add other charges, but the customer does not reserve an hourly quantity of read or write capacity for this mode.
MemoryDB for Redis OSS bills node-hours and data written, plus snapshot storage beyond its included Regional allowance. — A MemoryDB for Redis OSS estimate includes the selected nodes for the time they run and the volume of data written. Snapshot storage up to the documented Regional allowance is included; storage beyond that allowance is a separate charge.
DynamoDB provisioned mode bills only consumed read and write capacity, so unused provisioned capacity has no charge. — DynamoDB provisioned capacity can be economical for steady, predictable traffic, but AWS bills the hourly read and write capacity that the customer provisions. Unused provisioned capacity therefore remains billable, unlike on-demand request-based throughput.
One place to practise, understand your results and plan the next session.
Start with your free exam. Explore Exam, Endless and Custom practice modes as you build your study routine.
Review the reasoning behind your answers and return to the decisions that need another look.
Use domain-level performance and readiness to see strengths, gaps and areas you have yet to assess.
Explore hands-on tasks connected to SAA-C03. These are real Labs from the catalogue.
Repair network.yaml so the private subnet can reach Amazon S3 without an internet path. Keep the existing public route and the private subnet's safeguards.
medium · About 18 min
LabUpdate checkout-stack.yaml so checkout survives the loss of one Availability Zone and an instance that stops serving traffic is replaced. The application answers health checks on /health with HTTP 200. Run two instances steady-state, scaling no lower than two and no higher than four, and give a replacement instance up to two minutes to come into service. Keep the existing target-group traffic path, network, listener, security groups and private-only instances.
medium · About 18 min
Create your free account. Start practising.
Start Free