Advanced
Software Architecture
#CAP-theorem
#PACELC
#consistency
#distributed-systems
CAP Theorem Language
5 exercises — practise the vocabulary of distributed systems consistency: why partition tolerance is not optional, AP vs. CP system behaviour, the PACELC model, linearizability vs. eventual consistency, and responding to CAP challenges in design interviews.
0 / 30 completed
1 / 30
A principal engineer states: "The CAP theorem tells us that in the presence of a network partition, a distributed system must choose between consistency and availability." A colleague asks: "So which of the three properties — C, A, or P — can we always guarantee without any sacrifice?" What is the correct answer?
CAP theorem vocabulary — the partition tolerance misconception:
The most important insight in CAP is that partition tolerance (P) is not optional in any system with more than one node communicating over a network. Network partitions — dropped packets, split networks, timeout failures — are an unavoidable reality of distributed systems. You cannot design them away.
The practical choice is therefore: when a partition occurs, do you return possibly stale data (choose Availability) or return an error until consistency is restored (choose Consistency)?
Correct framing for architecture discussions: "The real CAP choice is CP vs. AP — not whether to tolerate partitions, but how to behave when partitions occur."
The most important insight in CAP is that partition tolerance (P) is not optional in any system with more than one node communicating over a network. Network partitions — dropped packets, split networks, timeout failures — are an unavoidable reality of distributed systems. You cannot design them away.
The practical choice is therefore: when a partition occurs, do you return possibly stale data (choose Availability) or return an error until consistency is restored (choose Consistency)?
| Property | Definition | Can you opt out? |
|---|---|---|
| Consistency (C) | Every read returns the most recent write — all nodes see the same data at the same time | Yes — you can sacrifice C to remain available during a partition |
| Availability (A) | Every request receives a (non-error) response — even if the data may be stale | Yes — you can sacrifice A to guarantee consistency (return errors until quorum is restored) |
| Partition Tolerance (P) | The system continues operating despite network partitions between nodes | No — in any multi-node distributed system, partitions will happen; P must be assumed |
Correct framing for architecture discussions: "The real CAP choice is CP vs. AP — not whether to tolerate partitions, but how to behave when partitions occur."
2 / 30
A DBA says: "MongoDB in its default configuration — with write concern w:1 and read preference primaryPreferred — favours availability over consistency." What does this mean for read behaviour after a network partition that isolates the primary from the secondaries?
CAP vocabulary — AP system behaviour (MongoDB default):
In its default configuration, MongoDB is an AP system during a partition. With
Key vocabulary for distributed database discussions:
Architecture discussion phrase: "With primaryPreferred reads, we accept the risk of stale reads during a partition in exchange for continued availability — if your feature requires read-your-writes consistency, you must read from primary only."
In its default configuration, MongoDB is an AP system during a partition. With
primaryPreferred read preference, if the primary is unreachable, reads fall back to a secondary — which may be behind on replication, returning stale data.| MongoDB config | CAP classification | Partition behaviour |
|---|---|---|
w:1, primaryPreferred | AP — availability preferred | Reads may return stale secondary data; system stays responsive |
w:majority, primary | CP — consistency preferred | Reads only from primary; if primary is partitioned, reads fail until election completes |
Key vocabulary for distributed database discussions:
- Replication lag: the delay between a write on the primary and its application on a secondary
- Read preference: MongoDB configuration controlling which node the client reads from (
primary,primaryPreferred,secondary,nearest) - Write concern: the acknowledgement level required before a write is confirmed to the client (
w:1= primary only,w:majority= majority of replica set) - Stale read: a read that returns data not yet reflecting the latest committed write
Architecture discussion phrase: "With primaryPreferred reads, we accept the risk of stale reads during a partition in exchange for continued availability — if your feature requires read-your-writes consistency, you must read from primary only."
3 / 30
An architect mentions PACELC during a discussion about database selection: "CAP only tells half the story — we need to apply PACELC to evaluate this system properly." What does the PACELC model add to CAP that CAP alone does not address?
PACELC vocabulary — extending CAP:
PACELC = PA/ELC: If there is a Partition, choose between Availability and Consistency. Else (no partition), choose between Latency and Consistency.
The key insight: even during normal operation, a system that wants strong consistency must accept higher latency — it must wait for all replicas to acknowledge a write before confirming it. CAP doesn't model this everyday operational trade-off.
PACELC vocabulary phrase for architecture interviews: "The question isn't just what happens during a partition — PACELC reminds us that even in normal operation, requiring strong consistency means accepting higher write latency because the system must wait for cross-node acknowledgement before confirming."
PACELC = PA/ELC: If there is a Partition, choose between Availability and Consistency. Else (no partition), choose between Latency and Consistency.
The key insight: even during normal operation, a system that wants strong consistency must accept higher latency — it must wait for all replicas to acknowledge a write before confirming it. CAP doesn't model this everyday operational trade-off.
| System | Partition behaviour (PA/PC) | Normal operation (EL/EC) |
|---|---|---|
| DynamoDB (default) | PA — stay available | EL — optimise for low latency |
| DynamoDB (strong consistency) | PC — prefer consistency | EC — accept higher latency for consistency |
| Cassandra (tunable) | PA — stay available by default | EL — optimise for write latency |
| PostgreSQL (synchronous replication) | PC — block until replica confirms | EC — every write waits for replica acknowledgement |
PACELC vocabulary phrase for architecture interviews: "The question isn't just what happens during a partition — PACELC reminds us that even in normal operation, requiring strong consistency means accepting higher write latency because the system must wait for cross-node acknowledgement before confirming."
4 / 30
An engineer says: "We need strong consistency on the payment confirmation read — we can't accept eventual consistency here." What property must the system guarantee to correctly claim strong consistency for that read path?
Strong consistency vocabulary — linearizability:
Option A is the correct definition. Strong consistency (also called linearizability) is a specific, formal guarantee: any read that begins after a write completes must return that write's value — no stale reads, no matter which replica services the read.
Important vocabulary clarification: ACID isolation (even SERIALIZABLE) is a single-node concurrency control guarantee, not a distributed consistency guarantee. A replicated database with SERIALIZABLE isolation on each node can still return stale reads if reads are served from a lagging replica. Strong consistency in the distributed sense requires all reads to go through a single source of truth or a consensus protocol (e.g., Raft-based linearizable reads).
Option A is the correct definition. Strong consistency (also called linearizability) is a specific, formal guarantee: any read that begins after a write completes must return that write's value — no stale reads, no matter which replica services the read.
| Consistency model | Guarantee | Example |
|---|---|---|
| Strong / Linearizable | Every read returns the most recent write — operations appear instantaneous and globally ordered | Reading payment status immediately after writing "confirmed" always returns "confirmed" |
| Sequential consistency | All operations appear to execute in some global sequential order — but not necessarily real-time order | Writes from one client appear in order; ordering across clients is not guaranteed in real time |
| Causal consistency | Causally related operations are observed in causal order by all nodes | A reply to a message is always seen after the original message |
| Eventual consistency | All replicas will converge to the same value — eventually, given no new writes | Acceptable for profile photos; not acceptable for payment status |
Important vocabulary clarification: ACID isolation (even SERIALIZABLE) is a single-node concurrency control guarantee, not a distributed consistency guarantee. A replicated database with SERIALIZABLE isolation on each node can still return stale reads if reads are served from a lagging replica. Strong consistency in the distributed sense requires all reads to go through a single source of truth or a consensus protocol (e.g., Raft-based linearizable reads).
5 / 30
In a system design interview, the interviewer challenges you: "The design you've proposed is CA — it guarantees both consistency and availability. But does a CA system actually work in a distributed environment?" What is the correct, technically informed response to this challenge?
CAP vocabulary — responding to the CA challenge:
Option C is the correct and professionally credible response. It demonstrates deep understanding: CA is not a valid category for distributed systems, and the candidate can articulate the correct framing (CP vs. AP) and even differentiate by feature within the same system.
Advanced interview vocabulary — per-feature CAP classification:
Real systems often have mixed consistency requirements by feature. The strongest answer acknowledges this: "The payment path is CP — I prefer a 503 over a stale confirmation. The notification feed is AP — stale is acceptable and availability is more important than freshness." This level of precision signals senior-level architectural thinking.
Option C is the correct and professionally credible response. It demonstrates deep understanding: CA is not a valid category for distributed systems, and the candidate can articulate the correct framing (CP vs. AP) and even differentiate by feature within the same system.
| CAP category | Valid in distributed systems? | Behaviour during partition | Example systems |
|---|---|---|---|
| CP | Yes | Returns error or blocks until consistency is restored | HBase, etcd (Raft), ZooKeeper, Redis Cluster (writes) |
| AP | Yes | Returns possibly stale data; never returns an error | Cassandra, DynamoDB (default), CouchDB |
| CA | No — only valid on a single node | Cannot exist: you cannot both stay available AND consistent while a partition exists | Single-node PostgreSQL (no replication) |
Advanced interview vocabulary — per-feature CAP classification:
Real systems often have mixed consistency requirements by feature. The strongest answer acknowledges this: "The payment path is CP — I prefer a 503 over a stale confirmation. The notification feed is AP — stale is acceptable and availability is more important than freshness." This level of precision signals senior-level architectural thinking.
6 / 30
Sarah (Senior Developer): "Okay team, we're rolling out the new user profile service. It's designed for high availability – users should always be able to see their data, even if some servers are down. We've prioritized availability over strict consistency."This scenario directly tests understanding of CAP. Sarah's statement explicitly prioritizes availability, indicating a deliberate choice to accept eventual consistency. The key takeaway is that the CAP theorem dictates this trade-off; prioritizing one property necessitates sacrificing another. The incorrect options misunderstand the core concept by suggesting consistency *should* always be prioritized or failing to recognize the inherent trade-off.
7 / 30
Mark (API Developer) sends this Slack message after a service outage:
'Just noticed that read requests to the inventory service are returning stale data. The system automatically failed over to a secondary replica but it seems the cache hasn't been updated yet.' What does 'cache inconsistency' primarily relate to in the context of CAP and distributed systems?This question focuses on the practical implications of eventual consistency. Mark's message details a scenario where cached data is out-of-sync with the primary database after a failover. This demonstrates how reliance on caching can exacerbate eventual consistency challenges, directly relating to the CAP theorem's emphasis on data divergence during partitions.
8 / 30
David (Tech Lead) writes this comment in a code review:
'The API endpoint for order status should return the *most recent* version of the order data. We can't tolerate users seeing an old order if it's been updated.' What architectural principle is David primarily referencing when making this statement?David's comment centers around the need for strong consistency – guaranteeing users see the latest data. This directly relates to CAP's emphasis on consistency as a key property in distributed systems. The incorrect options misinterpret his statement by focusing on availability or efficiency without acknowledging the core architectural principle of ensuring data integrity.
9 / 30
Emily (Junior Developer) is discussing system design with her team:
'We need to ensure that when a user makes a payment, the confirmation is immediately visible on their account. We can't risk them thinking the transaction hasn't gone through.' What property of the CAP theorem *must* this system guarantee for that read path?This question directly tests understanding of the implications of strong consistency. Emily's statement highlights the critical need for immediate confirmation – this necessitates that the system guarantees strong consistency to avoid user confusion and potential issues. The other options misinterpret the requirements by focusing on availability or eventual consistency.
10 / 30
Ben (Architect) says during a meeting: 'We're building a globally distributed system. We need to consider not just CAP, but also PACELC – Properties, Availability, Consistency, Eventual, Latency, Cost.' What additional factor does the PACELC model bring to the discussion compared to just CAP?The PACELC model represents a more holistic approach to designing distributed systems. It acknowledges that CAP focuses primarily on consistency and availability but neglects other crucial dimensions like latency (response time), cost (infrastructure expenses), and the specific properties of the data being managed – all essential considerations for real-world system design beyond just the trade-off between C and A.
11 / 30
Sarah (Senior Developer): "Okay team, we're rolling out the new user profile service. It's designed for high availability – users should always be able to see their data, even if some servers are down. We've prioritized availability over strict consistency."This scenario directly tests understanding of CAP. Sarah's statement explicitly prioritizes availability, indicating a deliberate choice to accept eventual consistency. The key takeaway is that the CAP theorem dictates this trade-off; prioritizing one property necessitates sacrificing another. The incorrect options misunderstand the core concept by suggesting consistency *should* always be prioritized or failing to recognize the inherent trade-off.
12 / 30
Mark (API Developer) sends this Slack message after a service outage:
'Just noticed that read requests to the inventory service are returning stale data. The system automatically failed over to a secondary replica but it seems the cache hasn't been updated yet.' What does 'cache inconsistency' primarily relate to in the context of CAP and distributed systems?This question focuses on the practical implications of eventual consistency. Mark's message details a scenario where cached data is out-of-sync with the primary database after a failover. This demonstrates how reliance on caching can exacerbate eventual consistency challenges, directly relating to the CAP theorem's emphasis on data divergence during partitions.
13 / 30
David (Tech Lead) writes this comment in a code review:
'The API endpoint for order status should return the *most recent* version of the order data. We can't tolerate users seeing an old order if it's been updated.' What architectural principle is David primarily referencing when making this statement?David's comment centers around the need for strong consistency – guaranteeing users see the latest data. This directly relates to CAP's emphasis on consistency as a key property in distributed systems. The incorrect options misinterpret his statement by focusing on availability or efficiency without acknowledging the core architectural principle of ensuring data integrity.
14 / 30
Emily (Junior Developer) is discussing system design with her team:
'We need to ensure that when a user makes a payment, the confirmation is immediately visible on their account. We can't risk them thinking the transaction hasn't gone through.' What property of the CAP theorem *must* this system guarantee for that read path?This question directly tests understanding of the implications of strong consistency. Emily's statement highlights the critical need for immediate confirmation – this necessitates that the system guarantees strong consistency to avoid user confusion and potential issues. The other options misinterpret the requirements by focusing on availability or eventual consistency.
15 / 30
Ben (Architect) says during a meeting: 'We're building a globally distributed system. We need to consider not just CAP, but also PACELC – Properties, Availability, Consistency, Eventual, Latency, Cost.' What additional factor does the PACELC model bring to the discussion compared to just CAP?The PACELC model represents a more holistic approach to designing distributed systems. It acknowledges that CAP focuses primarily on consistency and availability but neglects other crucial dimensions like latency (response time), cost (infrastructure expenses), and the specific properties of the data being managed – all essential considerations for real-world system design beyond just the trade-off between C and A.
16 / 30
Sarah (Senior Developer): "Okay team, we're rolling out the new user profile service. It's designed for high availability – users should always be able to see their data, even if some servers are down. We've prioritized availability over strict consistency."This scenario directly tests understanding of CAP. Sarah's statement explicitly prioritizes availability, indicating a deliberate choice to accept eventual consistency. The key takeaway is that the CAP theorem dictates this trade-off; prioritizing one property necessitates sacrificing another. The incorrect options misunderstand the core concept by suggesting consistency *should* always be prioritized or failing to recognize the inherent trade-off.
17 / 30
Mark (API Developer) sends this Slack message after a service outage:
'Just noticed that read requests to the inventory service are returning stale data. The system automatically failed over to a secondary replica but it seems the cache hasn't been updated yet.' What does 'cache inconsistency' primarily relate to in the context of CAP and distributed systems?This question focuses on the practical implications of eventual consistency. Mark's message details a scenario where cached data is out-of-sync with the primary database after a failover. This demonstrates how reliance on caching can exacerbate eventual consistency challenges, directly relating to the CAP theorem's emphasis on data divergence during partitions.
18 / 30
David (Tech Lead) writes this comment in a code review:
'The API endpoint for order status should return the *most recent* version of the order data. We can't tolerate users seeing an old order if it's been updated.' What architectural principle is David primarily referencing when making this statement?David's comment centers around the need for strong consistency – guaranteeing users see the latest data. This directly relates to CAP's emphasis on consistency as a key property in distributed systems. The incorrect options misinterpret his statement by focusing on availability or efficiency without acknowledging the core architectural principle of ensuring data integrity.
19 / 30
Emily (Junior Developer) is discussing system design with her team:
'We need to ensure that when a user makes a payment, the confirmation is immediately visible on their account. We can't risk them thinking the transaction hasn't gone through.' What property of the CAP theorem *must* this system guarantee for that read path?This question directly tests understanding of the implications of strong consistency. Emily's statement highlights the critical need for immediate confirmation – this necessitates that the system guarantees strong consistency to avoid user confusion and potential issues. The other options misinterpret the requirements by focusing on availability or eventual consistency.
20 / 30
Ben (Architect) says during a meeting: 'We're building a globally distributed system. We need to consider not just CAP, but also PACELC – Properties, Availability, Consistency, Eventual, Latency, Cost.' What additional factor does the PACELC model bring to the discussion compared to just CAP?The PACELC model represents a more holistic approach to designing distributed systems. It acknowledges that CAP focuses primarily on consistency and availability but neglects other crucial dimensions like latency (response time), cost (infrastructure expenses), and the specific properties of the data being managed – all essential considerations for real-world system design beyond just the trade-off between C and A.
21 / 30
Sarah (Senior Developer): "Okay team, we're rolling out the new user profile service. It's designed for high availability – users should always be able to see their data, even if some servers are down. We've prioritized availability over strict consistency."This scenario directly tests understanding of CAP. Sarah's statement explicitly prioritizes availability, indicating a deliberate choice to accept eventual consistency. The key takeaway is that the CAP theorem dictates this trade-off; prioritizing one property necessitates sacrificing another. The incorrect options misunderstand the core concept by suggesting consistency *should* always be prioritized or failing to recognize the inherent trade-off.
22 / 30
Mark (API Developer) sends this Slack message after a service outage:
'Just noticed that read requests to the inventory service are returning stale data. The system automatically failed over to a secondary replica but it seems the cache hasn't been updated yet.' What does 'cache inconsistency' primarily relate to in the context of CAP and distributed systems?This question focuses on the practical implications of eventual consistency. Mark's message details a scenario where cached data is out-of-sync with the primary database after a failover. This demonstrates how reliance on caching can exacerbate eventual consistency challenges, directly relating to the CAP theorem's emphasis on data divergence during partitions.
23 / 30
David (Tech Lead) writes this comment in a code review:
'The API endpoint for order status should return the *most recent* version of the order data. We can't tolerate users seeing an old order if it's been updated.' What architectural principle is David primarily referencing when making this statement?David's comment centers around the need for strong consistency – guaranteeing users see the latest data. This directly relates to CAP's emphasis on consistency as a key property in distributed systems. The incorrect options misinterpret his statement by focusing on availability or efficiency without acknowledging the core architectural principle of ensuring data integrity.
24 / 30
Emily (Junior Developer) is discussing system design with her team:
'We need to ensure that when a user makes a payment, the confirmation is immediately visible on their account. We can't risk them thinking the transaction hasn't gone through.' What property of the CAP theorem *must* this system guarantee for that read path?This question directly tests understanding of the implications of strong consistency. Emily's statement highlights the critical need for immediate confirmation – this necessitates that the system guarantees strong consistency to avoid user confusion and potential issues. The other options misinterpret the requirements by focusing on availability or eventual consistency.
25 / 30
Ben (Architect) says during a meeting: 'We're building a globally distributed system. We need to consider not just CAP, but also PACELC – Properties, Availability, Consistency, Eventual, Latency, Cost.' What additional factor does the PACELC model bring to the discussion compared to just CAP?The PACELC model represents a more holistic approach to designing distributed systems. It acknowledges that CAP focuses primarily on consistency and availability but neglects other crucial dimensions like latency (response time), cost (infrastructure expenses), and the specific properties of the data being managed – all essential considerations for real-world system design beyond just the trade-off between C and A.
26 / 30
Sarah (Senior Developer): "Okay team, we're rolling out the new user profile service. It's designed for high availability – users should always be able to see their data, even if some servers are down. We've prioritized availability over strict consistency."This scenario directly tests understanding of CAP. Sarah's statement explicitly prioritizes availability, indicating a deliberate choice to accept eventual consistency. The key takeaway is that the CAP theorem dictates this trade-off; prioritizing one property necessitates sacrificing another. The incorrect options misunderstand the core concept by suggesting consistency *should* always be prioritized or failing to recognize the inherent trade-off.
27 / 30
Mark (API Developer) sends this Slack message after a service outage:
'Just noticed that read requests to the inventory service are returning stale data. The system automatically failed over to a secondary replica but it seems the cache hasn't been updated yet.' What does 'cache inconsistency' primarily relate to in the context of CAP and distributed systems?This question focuses on the practical implications of eventual consistency. Mark's message details a scenario where cached data is out-of-sync with the primary database after a failover. This demonstrates how reliance on caching can exacerbate eventual consistency challenges, directly relating to the CAP theorem's emphasis on data divergence during partitions.
28 / 30
David (Tech Lead) writes this comment in a code review:
'The API endpoint for order status should return the *most recent* version of the order data. We can't tolerate users seeing an old order if it's been updated.' What architectural principle is David primarily referencing when making this statement?David's comment centers around the need for strong consistency – guaranteeing users see the latest data. This directly relates to CAP's emphasis on consistency as a key property in distributed systems. The incorrect options misinterpret his statement by focusing on availability or efficiency without acknowledging the core architectural principle of ensuring data integrity.
29 / 30
Emily (Junior Developer) is discussing system design with her team:
'We need to ensure that when a user makes a payment, the confirmation is immediately visible on their account. We can't risk them thinking the transaction hasn't gone through.' What property of the CAP theorem *must* this system guarantee for that read path?This question directly tests understanding of the implications of strong consistency. Emily's statement highlights the critical need for immediate confirmation – this necessitates that the system guarantees strong consistency to avoid user confusion and potential issues. The other options misinterpret the requirements by focusing on availability or eventual consistency.
30 / 30
Ben (Architect) says during a meeting: 'We're building a globally distributed system. We need to consider not just CAP, but also PACELC – Properties, Availability, Consistency, Eventual, Latency, Cost.' What additional factor does the PACELC model bring to the discussion compared to just CAP?The PACELC model represents a more holistic approach to designing distributed systems. It acknowledges that CAP focuses primarily on consistency and availability but neglects other crucial dimensions like latency (response time), cost (infrastructure expenses), and the specific properties of the data being managed – all essential considerations for real-world system design beyond just the trade-off between C and A.
Frequently Asked Questions
What will I learn from the "CAP Theorem Language — Software Architecture Exercises" exercise?
Practice English for CAP theorem discussions: partition tolerance, CP vs. AP systems, PACELC model, strong consistency vs. linearizability, and correctly responding to CAP challenges in system design interviews. 5 advanced exercises.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 30 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Software Architecture exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss software architecture topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 30 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Software Architecture exercises?
See the full Software Architecture exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.