SAA-C03 Practice Question: A SaaS platform plans to run in two AWS Regions for lower latency
A SaaS platform plans to run in two AWS Regions for lower latency. The team wants to enable active-active writes (both regions accept updates) to avoid failover downtime. However, the business requires strong consistency for order status transitions (for example, only one transition from “Paid” to “Shipped” must be allowed).
Which statement is the best architectural choice to meet the consistency requirement?
⚠ Common exam trap
Many candidates assume AWS's global services (like DynamoDB global tables or Aurora Global Database) inherently provide strong consistency for multi-region writes, when in fact they are designed for eventual consistency and require careful trade-offs for strict ordering requirements.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use active-active writes only when the workload tolerates eventual consistency; for strongly consistent transitions, use a single-writer pattern with failover (active-passive/pilot light).
Active-active writes across AWS Regions cannot guarantee strong consistency due to the inherent latency and lack of synchronous replication between Regions. For order status transitions that require exactly-once semantics (e.g., only one transition from 'Paid' to 'Shipped'), a single-writer pattern (active-passive or pilot light) ensures that only one Region accepts writes at a time, avoiding conflicts and maintaining a single source of truth. AWS services like DynamoDB global tables offer eventual consistency for multi-region writes, while Aurora Global Database provides read replicas with failover but not active-active writes for strong consistency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use active-active writes only when the workload tolerates eventual consistency; for strongly consistent transitions, use a single-writer pattern with failover (active-passive/pilot light).
Why this is correct
Correct. Active-active multi-Region writes rely on asynchronous cross-Region replication (e.g., DynamoDB Global Tables or Aurora Global Database), so a write in one Region is not immediately visible in the other; concurrent updates to the same item can conflict and require last-write-wins or custom conflict resolution, which is inherently eventually consistent. Strongly consistent transitions, such as a transaction that must read its own write or maintain a linearizable order, cannot be guaranteed with multiple concurrent writers. A single-writer pattern (active-passive or pilot light) ensures only one Region accepts writes at a time; failover transfers write authority to the secondary Region, preserving strong consistency because there is never more than one authoritative writer.
- ✗
Active-active writes always provide strong consistency because AWS replicates data across Regions automatically and immediately.
Why it's wrong here
Wrong. AWS does not replicate data across Regions automatically and immediately for active-active setups; cross-Region replication is always asynchronous by design, with measurable lag (e.g., Aurora Global Database typically has sub-second to 1-second replication lag, and DynamoDB Global Tables propagate changes asynchronously). This means a write in one Region may not yet be visible in another Region, so reads from the remote Region can be stale. Active-active multi-master patterns are eventually consistent under concurrent conflicting updates; they do not provide strong consistency unless the application uses a conflict-free data model or accepts last-writer-wins semantics, which is not universal.
When this WOULD be correct
A question stating that the application uses a single AWS Region with multi-AZ deployment and requires strong consistency for all reads and writes, where synchronous replication within a Region can provide immediate consistency.
- ✗
Active-active writes can be used safely by simply enabling retries and expecting the application to resolve conflicts without coordination.
Why it's wrong here
Wrong. Enabling retries on write operations only handles transient network issues or throttling; it does not resolve data conflicts that occur when two Regions independently write to the same item or partition key. Without a centralized coordination authority, each Region may apply its own update, leading to divergence; retrying simply causes the request to be re-applied, which can compound the conflict rather than resolve it. Proper conflict resolution requires a deterministic strategy such as last-writer-wins, vector clocks, or application-specific merge logic, and even then, the result is eventually consistent, not strongly consistent.
When this WOULD be correct
In a scenario where the workload can tolerate eventual consistency and the application is designed to handle conflicts (e.g., using last-writer-wins or CRDTs), and the business requirement is high availability with low latency rather than strong consistency for specific transitions.
- ✗
To ensure strong consistency, run both Regions with different IAM roles and block cross-Region writes at the API layer only.
Why it's wrong here
Wrong. IAM roles and API-level write blocking only control who can issue write requests; they do not influence the replication consistency of the underlying data store. If both Regions are still able to accept writes under their respective IAM roles, the system is still multi-master and susceptible to conflicting updates; blocking cross-Region writes at the API layer alone does not prevent writes that bypass that layer or a future misconfiguration. Even if you block cross-Region writes, that only enforces a single-writer topology implicitly, but the statement claims IAM differences ensure strong consistency—which they do not; strong consistency requires a single authoritative write path and synchronous or ordered replication, not access control.
When this WOULD be correct
If the question required preventing cross-Region writes for security reasons (e.g., to enforce data sovereignty) and consistency was not a concern, then using different IAM roles to block writes at the API layer would be a valid approach.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Use active-active writes only when the workload tolerates eventual consistency; for strongly consistent transitions, use a single-writer pattern with failover (active-passive/pilot light).Correct answer▾
Why this is correct
Correct. Active-active multi-Region writes rely on asynchronous cross-Region replication (e.g., DynamoDB Global Tables or Aurora Global Database), so a write in one Region is not immediately visible in the other; concurrent updates to the same item can conflict and require last-write-wins or custom conflict resolution, which is inherently eventually consistent. Strongly consistent transitions, such as a transaction that must read its own write or maintain a linearizable order, cannot be guaranteed with multiple concurrent writers. A single-writer pattern (active-passive or pilot light) ensures only one Region accepts writes at a time; failover transfers write authority to the secondary Region, preserving strong consistency because there is never more than one authoritative writer.
✗Active-active writes always provide strong consistency because AWS replicates data across Regions automatically and immediately.Wrong answer — click to see why▾
Why this is wrong here
AWS does not replicate data across Regions automatically or immediately; cross-Region replication is asynchronous, so active-active writes cannot guarantee strong consistency.
★ When this WOULD be the correct answer
A question stating that the application uses a single AWS Region with multi-AZ deployment and requires strong consistency for all reads and writes, where synchronous replication within a Region can provide immediate consistency.
Why candidates choose this
Candidates may mistakenly believe that AWS handles cross-Region replication synchronously, similar to within-Region services like DynamoDB global tables or Aurora Global Database, which are actually asynchronous.
✗Active-active writes can be used safely by simply enabling retries and expecting the application to resolve conflicts without coordination.Wrong answer — click to see why▾
Why this is wrong here
Active-active writes without coordination cannot guarantee strong consistency for order status transitions; retries and application-level conflict resolution are insufficient to prevent two regions from simultaneously accepting conflicting transitions (e.g., 'Paid' to 'Shipped' in both regions).
★ When this WOULD be the correct answer
In a scenario where the workload can tolerate eventual consistency and the application is designed to handle conflicts (e.g., using last-writer-wins or CRDTs), and the business requirement is high availability with low latency rather than strong consistency for specific transitions.
Why candidates choose this
Candidates may assume that retries and application logic can resolve all conflicts, underestimating the difficulty of ensuring strong consistency across regions without a centralized coordinator or locking mechanism.
✗To ensure strong consistency, run both Regions with different IAM roles and block cross-Region writes at the API layer only.Wrong answer — click to see why▾
Why this is wrong here
Blocking cross-Region writes at the API layer with different IAM roles does not prevent concurrent writes from being accepted in both regions before the API layer can reject them, so it cannot guarantee strong consistency for order status transitions.
★ When this WOULD be the correct answer
If the question required preventing cross-Region writes for security reasons (e.g., to enforce data sovereignty) and consistency was not a concern, then using different IAM roles to block writes at the API layer would be a valid approach.
Why candidates choose this
Candidates may think that IAM-based API restrictions can enforce write ordering across regions, but IAM cannot coordinate the timing of concurrent requests in a distributed system.
Analysis generated from the official SAA-C03 blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
You might also like
Similar SAA-C03 questions
- A consumer application reads from an Amazon SQS queue. Some messages have an invalid format and always fail processing.…
- A healthcare company stores patient records in an Amazon DynamoDB table. The table must be recoverable to any point with…
- A company is building a serverless application that processes messages from an Amazon SQS queue using AWS Lambda. The ap…
- A healthcare analytics team runs a containerized reporting service on Amazon ECS with the Fargate launch type in a singl…
- Based on the exhibit, the web tier becomes unavailable if us-west-2a has an outage. What is the best change to improve r…
Written by Johnson Ajibi, MSc IT Security
Security Systems Architect · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.