← GCDL·Google Cloud

Question 106 of 507

Fundamental cloud concepts →mediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is strong consistency, because real-time collaborative document editing demands that all users see the same document state simultaneously, and this requirement directly rules out eventually consistent NoSQL stores like default-mode Amazon DynamoDB. The core technical concept here is that without strong consistency, users would observe conflicting or stale edits, breaking the illusion of a shared live document. On the Google Cloud Digital Leader exam, this question tests your ability to map application requirements to database trade-offs—specifically, that real-time collaboration pushes you toward strongly consistent databases such as Google Cloud Spanner or toward specialized protocols like Operational Transformation (OT) and CRDTs that guarantee convergence. A common trap is assuming any NoSQL database works for all real-time apps; remember that “eventual” is the enemy of “instant.” Memory tip: for live collaboration, think “Strong or Sync—no eventual link.”

Cloud Digital Leader Fundamental cloud concepts Practice Question

This GCDL practice question tests your understanding of fundamental cloud concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 developer is building a real-time collaborative document editing application (similar to Google Docs). Users must see each other's edits instantly. Which data consistency model is required for this use case, and what is the implication for the database choice?

Question 1mediummultiple choice

Full question →

A
Eventual consistency is acceptable because users will eventually see each other's edits after a short delay, and this enables higher performance
Why wrong: For collaborative document editing, eventual consistency causes visible conflicts — User A sees 'Hello World' while User B sees 'Hello' simultaneously. This is unacceptable UX. Real-time collaboration requires tight consistency guarantees or specialized sync mechanisms.
B
Strong consistency or real-time synchronization is required so all users see the same document state simultaneously; this rules out eventually consistent NoSQL stores and pushes toward strongly consistent databases or specialized collaboration protocols
Real-time collaboration requires that edits are applied in a consistent order visible to all users simultaneously. Eventually consistent databases (like Cassandra in default mode) would show different users different states of the document. This workload requires either strongly consistent storage or specialized real-time sync protocols (Operational Transformation, CRDTs) that handle concurrent edits correctly.
C
Consistency doesn't matter for this use case because each user edits different parts of the document
Why wrong: In collaborative editing, users actively edit the same content. Cursor positions, text insertions, and deletions from multiple users must be merged consistently. Consistency is critical, not irrelevant.
D
This workload requires a relational database because only SQL can handle concurrent user edits correctly
Why wrong: Relational databases are not the only option. Specialized real-time databases (Firestore, Supabase Realtime) and synchronization protocols (CRDTs) can handle concurrent collaborative editing without traditional SQL.

Full breakdown with real-world context →

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

✓

Strong consistency or real-time synchronization is required so all users see the same document state simultaneously; this rules out eventually consistent NoSQL stores and pushes toward strongly consistent databases or specialized collaboration protocols

Option B is correct because real-time collaborative editing requires all users to see the same document state simultaneously, which demands strong consistency or real-time synchronization. This rules out eventually consistent NoSQL stores (e.g., Amazon DynamoDB in default mode) and pushes toward strongly consistent databases (e.g., Google Cloud Spanner, CockroachDB) or specialized collaboration protocols like Operational Transformation (OT) or Conflict-Free Replicated Data Types (CRDTs) that provide convergence guarantees.

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 acceptable because users will eventually see each other's edits after a short delay, and this enables higher performance
Why it's wrong here
For collaborative document editing, eventual consistency causes visible conflicts — User A sees 'Hello World' while User B sees 'Hello' simultaneously. This is unacceptable UX. Real-time collaboration requires tight consistency guarantees or specialized sync mechanisms.
✓
Strong consistency or real-time synchronization is required so all users see the same document state simultaneously; this rules out eventually consistent NoSQL stores and pushes toward strongly consistent databases or specialized collaboration protocols
Why this is correct
Real-time collaboration requires that edits are applied in a consistent order visible to all users simultaneously. Eventually consistent databases (like Cassandra in default mode) would show different users different states of the document. This workload requires either strongly consistent storage or specialized real-time sync protocols (Operational Transformation, CRDTs) that handle concurrent edits correctly.
Related concept
Read the scenario before looking for a memorised answer.
✗
Consistency doesn't matter for this use case because each user edits different parts of the document
Why it's wrong here
In collaborative editing, users actively edit the same content. Cursor positions, text insertions, and deletions from multiple users must be merged consistently. Consistency is critical, not irrelevant.
✗
This workload requires a relational database because only SQL can handle concurrent user edits correctly
Why it's wrong here
Relational databases are not the only option. Specialized real-time databases (Firestore, Supabase Realtime) and synchronization protocols (CRDTs) can handle concurrent collaborative editing without traditional SQL.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that eventual consistency is sufficient for real-time applications, but the trap here is that users expect instant, conflict-free updates, which only strong consistency or specialized synchronization protocols can guarantee.

Detailed technical explanation

How to think about this question

Under the hood, real-time collaborative editing typically uses Operational Transformation (OT) or CRDTs to resolve conflicts without requiring a central lock. OT transforms operations against each other to maintain consistency, while CRDTs use commutative, associative, and idempotent operations to merge edits automatically. In a real-world scenario, Google Docs uses OT with a central server to order operations, ensuring all clients converge to the same state even with network latency.

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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

GCDL practice-test guide →Study guide →Browse all practice tests

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: Strong consistency or real-time synchronization is required so all users see the same document state simultaneously; this rules out eventually consistent NoSQL stores and pushes toward strongly consistent databases or specialized collaboration protocols — Option B is correct because real-time collaborative editing requires all users to see the same document state simultaneously, which demands strong consistency or real-time synchronization. This rules out eventually consistent NoSQL stores (e.g., Amazon DynamoDB in default mode) and pushes toward strongly consistent databases (e.g., Google Cloud Spanner, CockroachDB) or specialized collaboration protocols like Operational Transformation (OT) or Conflict-Free Replicated Data Types (CRDTs) that provide convergence guarantees.

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.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on GCDL

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A startup is building a gaming application where players must see each other's moves in real time. The database storing game state must guarantee that all players see the same state simultaneously. Which consistency requirement does this impose and why does it matter for database selection?

medium

A.Eventual consistency is sufficient; the game can show slightly stale state to some players without impact on gameplay
✓ B.Strong consistency is required so all players simultaneously read the same current game state; eventual consistency would create conflicting game states visible to different players
C.Consistency doesn't matter for gaming databases because games update state so frequently that any inconsistency resolves within milliseconds
D.The game should avoid databases entirely and use local storage on each player's device to ensure fast, consistent state access

Why B: B is correct because real-time multiplayer gaming requires strong consistency to ensure all players see the identical game state simultaneously. In a GCDL context, this means the database must support ACID transactions or linearizable reads (e.g., using Google Cloud Spanner or a strongly consistent NoSQL system like Cloud Firestore in strong consistency mode). Eventual consistency would allow different players to observe different board positions, breaking the game's core requirement of a shared, current state.

Keep practising

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.

Loading comments…

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.