- A
Eventual consistency is a bug — the system should be fixed to always show current data.
Why wrong: Eventual consistency is a deliberate design choice for distributed systems requiring high availability. It enables performance and availability benefits that strong consistency cannot provide at scale.
- B
Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously.
In eventually consistent systems, writes propagate asynchronously. All replicas converge to the same value within a short time window. This enables higher throughput and availability than strong consistency, which requires synchronous coordination across all nodes.
- C
Eventual consistency means data is eventually deleted, which reduces storage costs.
Why wrong: Eventual consistency describes replication propagation timing, not data lifecycle. Data is not deleted; it converges across replicas.
- D
Eventual consistency only applies to deleted data — new data always appears immediately.
Why wrong: Eventual consistency applies to all writes (inserts, updates, deletes). Newly written data may not appear immediately across all nodes — that's the nature of eventual (asynchronous) propagation.
Quick Answer
The answer is that eventual consistency trades immediate data accuracy for higher availability and better performance. This trade-off is correct because in distributed systems, the CAP theorem dictates that you can only guarantee two of Consistency, Availability, and Partition Tolerance simultaneously; by choosing eventual consistency, the system prioritizes availability and low-latency operations over seeing the most current data instantly, with updates propagating asynchronously to all nodes until they converge. On the Google Cloud Digital Leader exam, this concept tests your understanding of how cloud architects balance design constraints—a common trap is assuming "eventual" means unreliable, when it actually ensures all nodes will synchronize over time, just not immediately. Remember the mnemonic "E-A-P": Eventual consistency trades Accuracy for Availability and Performance.
Cloud Digital Leader Fundamental cloud concepts Practice Question
This GCDL practice question tests your understanding of fundamental cloud concepts. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company's cloud architect explains that their new system uses 'eventual consistency' for some data operations. A business stakeholder asks why the system won't always show the most up-to-date data immediately. What is the trade-off being made?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"always"Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
Clue:
"immediately / without restart"Why it matters: Time or reboot constraint — the correct answer must take effect right away without requiring a reboot or reload.
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
Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously.
Option B is correct because eventual consistency is a deliberate design choice in distributed systems (such as those using Amazon DynamoDB or Apache Cassandra) where the system prioritizes high availability and low-latency reads/writes over immediate consistency. Under the hood, data updates propagate asynchronously to replicas, and all nodes will eventually converge to the same value via mechanisms like gossip protocols or vector clocks, but there is a window where stale data may be returned. This trade-off is fundamental to the CAP theorem, which states that in a distributed data store, you can only guarantee two of Consistency, Availability, and Partition Tolerance simultaneously.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Eventual consistency is a bug — the system should be fixed to always show current data.
Why it's wrong here
Eventual consistency is a deliberate design choice for distributed systems requiring high availability. It enables performance and availability benefits that strong consistency cannot provide at scale.
- ✓
Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously.
Why this is correct
In eventually consistent systems, writes propagate asynchronously. All replicas converge to the same value within a short time window. This enables higher throughput and availability than strong consistency, which requires synchronous coordination across all nodes.
Clue confirmation
The clue words "always", "immediately / without restart" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Eventual consistency means data is eventually deleted, which reduces storage costs.
Why it's wrong here
Eventual consistency describes replication propagation timing, not data lifecycle. Data is not deleted; it converges across replicas.
- ✗
Eventual consistency only applies to deleted data — new data always appears immediately.
Why it's wrong here
Eventual consistency applies to all writes (inserts, updates, deletes). Newly written data may not appear immediately across all nodes — that's the nature of eventual (asynchronous) propagation.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that eventual consistency is a fault or a temporary bug, when in fact it is a deliberate design trade-off to achieve high availability and partition tolerance in distributed systems.
Detailed technical explanation
How to think about this question
Under the hood, eventual consistency relies on techniques such as read-repair, hinted handoffs, and Merkle trees to detect and resolve conflicts across replicas. For example, in Amazon DynamoDB, a write may be accepted by a single node and then asynchronously propagated to other nodes using a gossip protocol; a subsequent read from a different node may return stale data until the propagation completes. A real-world scenario where this matters is a social media feed: a user's new post may not appear immediately to all followers, but the system can handle millions of concurrent writes without downtime, which is more important than instant visibility.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Fundamental cloud concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Fundamental cloud concepts practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Fundamental cloud concepts — This question tests Fundamental cloud concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Eventual consistency trades immediate data accuracy for higher availability and better performance — all nodes will converge to the same value, just not instantaneously. — Option B is correct because eventual consistency is a deliberate design choice in distributed systems (such as those using Amazon DynamoDB or Apache Cassandra) where the system prioritizes high availability and low-latency reads/writes over immediate consistency. Under the hood, data updates propagate asynchronously to replicas, and all nodes will eventually converge to the same value via mechanisms like gossip protocols or vector clocks, but there is a window where stale data may be returned. This trade-off is fundamental to the CAP theorem, which states that in a distributed data store, you can only guarantee two of Consistency, Availability, and Partition Tolerance simultaneously.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "always", "immediately / without restart". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
This GCDL practice question is part of Courseiva's free Google Cloud 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 GCDL exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.