Practise vocabulary for real-time collaboration: presence indicators, live cursors, CRDTs, operational transformation, and conflict resolution strategies.
0 / 12 completed
1 / 12
A collaborative editor shows each user's cursor position in real time. What is this feature called and what is the key engineering challenge?
Live cursors are a presence feature: each client broadcasts its cursor position over a WebSocket channel; all other clients render the received positions as coloured cursors with the user's name. Key challenges: (1) throttling — broadcasting on every mouse-move event floods the server; typical approach is throttle to 50ms intervals. (2) Interpolation — smooth cursor movement on the receiver side despite network jitter. (3) Cleanup — removing a cursor when a user disconnects.
2 / 12
What are CRDTs (Conflict-free Replicated Data Types) in the context of real-time collaborative editing?
CRDTs (e.g., Yjs, Automerge) are algebraic data structures with a merge function that is commutative, associative, and idempotent — meaning any two states can be merged in any order and the result is always consistent. For collaborative text editing, a CRDT assigns each character a globally unique position so that concurrent inserts from two users always produce a deterministic merged result without a server making the decision. CRDTs enable fully distributed collaboration (peer-to-peer sync) and offline editing with eventual consistency.
3 / 12
What is Operational Transformation (OT) and how does it differ from CRDTs for collaborative editing?
Operational Transformation (the technology behind early Google Docs and Wave) works by transforming incoming operations against all concurrent operations that have already been applied locally. If user A inserts at position 5 while user B deletes at position 3, OT adjusts A's insert to position 4 before applying it. OT requires a central authority to serialize operations. CRDTs avoid this by using position identifiers that don't need transformation — enabling decentralized sync. Both produce correct results; CRDTs are generally considered simpler to implement correctly.
4 / 12
What does 'last write wins' (LWW) mean as a conflict resolution strategy, and when is it appropriate?
Last Write Wins (LWW) is used for eventually-consistent key-value data where losing a concurrent update is acceptable: cursor positions, presence status, user settings. It is NOT appropriate for collaborative text editing — if two users both edit a paragraph simultaneously, LWW would silently discard one user's changes. For text, CRDTs or OT are required. In distributed databases (Cassandra, Redis), LWW is a common default conflict resolution strategy with the understanding that data loss is possible under concurrent writes.
5 / 12
What is a 'presence indicator' in real-time collaboration vocabulary?
Presence indicators show awareness: 'Alice and Bob are also viewing this document right now.' Implementation: when a client connects, it broadcasts a 'joined' event with user metadata; the server tracks all connected users and broadcasts the current presence list to new joiners; on disconnect (or heartbeat timeout), a 'left' event is emitted. Tools like Liveblocks, PartyKit, and Ably provide managed presence channels. Presence data is ephemeral — not stored in the database, only in the connection layer.
6 / 12
Sarah from the Frontend team is currently editing a shared design document in Figma. You see her cursor blinking rapidly as she makes changes simultaneously with Mark from UX. What term best describes this visual representation of concurrent edits within the application?
This scenario describes the ability to see other users' edits happening in real time. The correct answer, Real-time synchronization, is a key term for this feature, highlighting how changes are propagated across connected devices and users almost instantly. The other options relate to different aspects of collaboration – OT is a technical approach, offline mode refers to working without internet connectivity.
7 / 12
David, the backend engineer, needs to explain to the frontend team why their changes aren't immediately reflected after they push a new commit. He mentions that the system uses 'CRDTs'. What is the primary function of CRDTs in this context?
CRDTs (Conflict-free Replicated Data Types) are designed specifically for collaborative editing scenarios. Their core function is to ensure that even if users make changes concurrently and independently, the final state of the data will be identical across all replicas – achieving eventual consistency without complex conflict resolution algorithms. The other options misrepresent CRDTs' role; they aren't databases or require a centralized server.
8 / 12
John is using a real-time collaborative document editor. He notices that when he makes a change, his teammates instantly see it, even though they haven't explicitly refreshed the page. What underlying technology is most likely responsible for this behavior?
WebSocket provides a persistent, full-duplex connection between the client and server, enabling real-time data exchange without the overhead of repeatedly establishing new connections. HTTP Long Polling and traditional AJAX rely on polling for updates, which is less efficient and introduces latency. SSE is primarily for unidirectional data streams.
9 / 12
Maria, a product manager, needs to quickly update the status of a feature request in a shared Jira board that multiple developers are simultaneously editing. The system automatically resolves conflicts when multiple users make changes. Which conflict resolution strategy is most likely being employed?
CRDTs are designed for collaborative systems where data can be replicated across multiple users without requiring a central authority to resolve conflicts. OT and LWW are specific algorithms for conflict resolution, but CRDTs represent the broader approach suitable for this scenario. Optimistic Locking is typically used within a single database transaction.
10 / 12
Ben, a senior engineer, is reviewing a pull request with several collaborators. One reviewer notices that a recent change introduced a potential race condition in the code. He uses the term 'presence indicators' to describe what he's observing. What does 'presence indicator' refer to in this context?
'Presence indicators' refer to visual signals – typically cursors or highlighting – that show which users are currently actively editing a shared resource. This helps reviewers understand the context of changes and quickly identify potential conflicts arising from simultaneous modifications. The other options describe different aspects of real-time collaboration technology.
11 / 12
Emily is explaining to a junior developer why changes made in one browser window aren't immediately reflected in another. She says: 'The system uses 'last write wins'.' What does this phrase mean in the context of real-time collaborative editing?
'Last Write Wins' (LWW) is a simple conflict resolution strategy where the most recent change to a resource overwrites any earlier changes. While straightforward, it can lead to data loss if not managed carefully and isn't suitable for all collaborative editing scenarios – particularly those requiring more sophisticated conflict management.
12 / 12
David is describing the architecture of a real-time collaborative document editor to a new team member. He mentions that the system uses 'Operational Transformation (OT)'. What is the core principle behind OT?
Operational Transformation (OT) is a technique where each change made by a user is transformed based on the changes that have already been made by all other users. This allows for real-time collaboration without requiring strict synchronization—though it's more complex to implement than CRDTs.
What does this WebRTC & Real-Time Language exercise cover?
This exercise, "Real-Time Collaboration Features Vocabulary", tests your understanding of webrtc & real-time language vocabulary and phrasing through 12 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 12 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this WebRTC & Real-Time Language exercise for?
It's designed for IT professionals and learners who want to sound natural discussing webrtc & real-time language topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more WebRTC & Real-Time Language exercises?
Browse the full WebRTC & Real-Time Language exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.