Replication strategies in DBMS Theory - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the replication type where data is copied from one primary server to multiple secondary servers.

DBMS Theory

Replication type where data flows from one primary to many secondary servers is called [1] replication.

Drag options to blanks, or click blank then click option'

APeer-to-peer

BMaster-slave

CMulti-master

DSnapshot

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing master-slave with peer-to-peer replication.

Thinking multi-master means one primary server.

Master-slave replication means one primary (master) server sends data to one or more secondary (slave) servers.

2fill in blank

medium

Complete the sentence to describe the replication strategy where all nodes can accept writes and synchronize with each other.

DBMS Theory

In [1] replication, multiple servers act as equals and can all accept write operations.

Drag options to blanks, or click blank then click option'

ASnapshot

BLog shipping

CMulti-master

DMaster-slave

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing master-slave which only allows one write server.

Confusing snapshot with multi-master replication.

Multi-master replication allows all servers to accept writes and synchronize changes among themselves.

3fill in blank

hard

Fix the error in the description of replication where data is copied at specific points in time.

DBMS Theory

Replication that copies data at specific intervals is called [1] replication.

Drag options to blanks, or click blank then click option'

ASnapshot

BTransactional

CSynchronous

DAsynchronous

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing snapshot with transactional replication.

Mixing synchronous and asynchronous replication types.

Snapshot replication copies data at specific moments, creating a snapshot of the data.

4fill in blank

hard

Fill both blanks to complete the description of replication types based on timing.

DBMS Theory

In [1] replication, changes are applied immediately, while in [2] replication, changes are delayed.

Drag options to blanks, or click blank then click option'

ASynchronous

BAsynchronous

CSnapshot

DTransactional

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up synchronous and asynchronous terms.

Choosing snapshot or transactional which are different concepts.

Synchronous replication applies changes immediately to all nodes, ensuring consistency. Asynchronous replication applies changes with a delay, allowing some lag.

5fill in blank

hard

Fill all three blanks to complete the dictionary that maps replication types to their main characteristics.

DBMS Theory

replication_info = {'Master-slave': '[1]', 'Multi-master': '[2]', 'Snapshot': '[3]'}

Drag options to blanks, or click blank then click option'

ASingle primary server

BMultiple write servers

CData copied at intervals

DReal-time synchronization

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing characteristics between replication types.

Choosing 'Real-time synchronization' for snapshot replication.

This dictionary maps:
- Master-slave to 'Single primary server'
- Multi-master to 'Multiple write servers'
- Snapshot to 'Data copied at intervals'

Practice

1. Which replication strategy involves one main server handling all writes and one or more servers copying data from it?

easy

A. Master-Slave replication

B. Master-Master replication

C. Peer-to-Peer replication

D. Snapshot replication

Solution

1. Step 1: Understand Master-Slave replication

   In this strategy, one server (master) handles all write operations, and other servers (slaves) copy data from it.

2. Step 2: Compare with other strategies

   Master-Master allows multiple masters; Peer-to-Peer is decentralized; Snapshot copies data at intervals.

3. Final Answer:

   Master-Slave replication -> Option A

4. Quick Check:

   One main write server = Master-Slave [OK]

Hint: Master-Slave means one master writes, slaves copy [OK]

Common Mistakes:

• Confusing Master-Slave with Master-Master
• Thinking slaves can write data
• Mixing snapshot with continuous replication

2. Which of the following is the correct syntax to describe Master-Master replication?

easy

A. Two servers both accept writes and replicate changes to each other

B. One server writes, others read only

C. Data is copied only once at setup

D. Servers do not communicate

Solution

1. Step 1: Define Master-Master replication

   Both servers can accept writes and replicate changes to each other to keep data synchronized.

2. Step 2: Eliminate incorrect options

   Data is copied only once at setup describes snapshot; One server writes, others read only describes Master-Slave; Servers do not communicate is not replication.

3. Final Answer:

   Two servers both accept writes and replicate changes to each other -> Option A

4. Quick Check:

   Master-Master means both write and sync [OK]

Hint: Master-Master means both servers write and sync [OK]

Common Mistakes:

• Thinking only one server writes in Master-Master
• Confusing snapshot with replication
• Assuming no communication means replication

3. Consider a Master-Slave replication setup where the master server receives 100 write requests per second. If slaves replicate with a delay of 2 seconds, what is the expected delay in data consistency on slaves?

medium

A. Immediate consistency

B. No delay, slaves write directly

C. 2 seconds delay

D. 100 seconds delay

Solution

1. Step 1: Understand replication delay

   Slaves replicate data from master with a 2-second delay, so data on slaves lags behind master by 2 seconds.

2. Step 2: Analyze options

   Immediate consistency means no delay, which is incorrect. 100 seconds delay is unrelated to request rate. Slaves do not write directly.

3. Final Answer:

   2 seconds delay -> Option C

4. Quick Check:

   Replication delay = 2 seconds [OK]

Hint: Replication delay equals slave lag time [OK]

Common Mistakes:

• Confusing request rate with delay time
• Assuming slaves write directly
• Thinking slaves are always immediately consistent

4. A database administrator sets up Master-Master replication but notices data conflicts when both servers write the same record simultaneously. What is the best way to fix this?

medium

A. Allow only one server to write at a time without syncing

B. Switch to Master-Slave replication

C. Disable replication entirely

D. Implement conflict resolution rules or use timestamps

Solution

1. Step 1: Identify cause of conflicts

   Simultaneous writes cause conflicts in Master-Master replication because both servers can change the same data.

2. Step 2: Apply conflict resolution

   Using rules like timestamps or last-write-wins helps resolve conflicts automatically.

3. Final Answer:

   Implement conflict resolution rules or use timestamps -> Option D

4. Quick Check:

   Conflict resolution fixes simultaneous writes [OK]

Hint: Use conflict rules to fix Master-Master write clashes [OK]

Common Mistakes:

• Thinking disabling replication solves conflicts
• Switching to Master-Slave without need
• Ignoring conflict resolution mechanisms

5. You want a replication strategy that provides high availability and allows writes on multiple servers but can tolerate occasional conflicts. Which strategy fits best?

hard

A. Master-Slave replication

B. Master-Master replication

C. Snapshot replication

D. No replication

Solution

1. Step 1: Analyze requirements

   High availability and multiple write servers require a strategy where more than one server can accept writes.

2. Step 2: Match strategy to needs

   Master-Master replication allows multiple write servers but may have conflicts; Master-Slave does not allow multiple writes.

3. Final Answer:

   Master-Master replication -> Option B

4. Quick Check:

   Multiple writes + availability = Master-Master [OK]

Hint: Multiple write servers need Master-Master replication [OK]

Common Mistakes:

• Choosing Master-Slave for multiple writes
• Ignoring conflict tolerance
• Thinking snapshot replication supports writes