Why replication is needed in MongoDB - Quick Recap

Recall & Review

beginner

What is replication in MongoDB?

Replication in MongoDB is the process of copying data from one database server to another to ensure data availability and redundancy.

beginner

Why is replication important for data availability?

Replication helps keep data available even if one server fails, by having copies of the data on other servers ready to take over.

intermediate

How does replication help with disaster recovery?

Replication creates copies of data on multiple servers, so if one server is lost due to disaster, the data is still safe on others.

intermediate

What role does replication play in load balancing?

Replication allows read operations to be spread across multiple servers, reducing load on the primary server and improving performance.

intermediate

Can replication improve fault tolerance? How?

Yes, replication improves fault tolerance by having multiple copies of data, so if one server fails, others can continue serving data without interruption.

What is the main purpose of replication in MongoDB?

A To delete old data automatically

B To copy data across servers for availability

C To speed up data entry

D To encrypt data

Replication copies data to multiple servers to keep it available if one server fails.

How does replication help during a server failure?

A It backs up data to a USB drive

B It deletes the failed server's data

C It stops all database operations

D It switches to another server with the same data

Replication allows another server with the same data to take over, keeping the database running.

Which of these is NOT a benefit of replication?

A Faster data deletion

B Load balancing

C Disaster recovery

D Improved data availability

Replication does not speed up data deletion; it focuses on data copying and availability.

Replication can help with load balancing by:

A Allowing multiple servers to handle read requests

B Increasing write speed on one server

C Deleting duplicate data

D Encrypting data transfers

Multiple servers with replicated data can share read requests, reducing load on one server.

What happens if a disaster destroys the primary MongoDB server without replication?

A Replication creates new data

B Data automatically recovers

C Data is lost if no backup exists

D The server fixes itself

Without replication or backup, data on the destroyed server is lost.

Explain why replication is needed in MongoDB and how it helps keep data safe.

Think about what happens if one server stops working.

Describe how replication can improve performance and reliability in a MongoDB setup.

Consider how multiple copies of data can share work and handle failures.

Practice

1. Why is replication needed in MongoDB?

easy

A. To keep data safe by copying it to multiple servers

B. To speed up queries by using a single server

C. To delete old data automatically

D. To reduce the size of the database

Solution

1. Step 1: Understand replication purpose

   Replication copies data to multiple servers to protect against data loss.

2. Step 2: Identify the benefit in MongoDB

   This copying keeps data safe and available even if one server fails.

3. Final Answer:

   To keep data safe by copying it to multiple servers -> Option A

4. Quick Check:

   Replication = Data safety [OK]

Hint: Replication means copying data to protect it [OK]

Common Mistakes:

• Thinking replication speeds up queries only
• Believing replication deletes old data
• Assuming replication reduces database size

2. Which of the following is the correct way to define a replica set in MongoDB configuration?

easy

A. "replica": { "replSetName": "rs0" }

B. "replication": { "setName": "rs0" }

C. "replicaSet": { "name": "rs0" }

D. "replication": { "replSetName": "rs0" }

Solution

1. Step 1: Recall MongoDB replica set config syntax

   The correct key is "replication" with "replSetName" inside.

2. Step 2: Match options to syntax

   "replication": { "replSetName": "rs0" } matches the exact syntax used in MongoDB config files.

3. Final Answer:

   "replication": { "replSetName": "rs0" } -> Option D

4. Quick Check:

   Correct config key = "replication" + "replSetName" [OK]

Hint: Look for "replication" and "replSetName" keys [OK]

Common Mistakes:

• Using wrong key names like "replicaSet" or "replica"
• Mixing up "setName" instead of "replSetName"
• Incorrect nesting of configuration keys

3. Consider a MongoDB replica set with one primary and two secondary nodes. If the primary node fails, what happens next?

medium

A. The replica set stops working until the primary is fixed

B. One of the secondary nodes is automatically elected as the new primary

C. All data is lost because the primary is down

D. The secondary nodes become read-only and no writes are allowed

Solution

1. Step 1: Understand replica set failover

   When the primary fails, MongoDB automatically elects a new primary from secondaries.

2. Step 2: Identify the correct behavior

   This automatic election keeps the database available for writes.

3. Final Answer:

   One of the secondary nodes is automatically elected as the new primary -> Option B

4. Quick Check:

   Failover = Auto election of new primary [OK]

Hint: Primary failure triggers automatic new primary election [OK]

Common Mistakes:

• Thinking the replica set stops working
• Believing data is lost on primary failure
• Assuming secondaries become read-only only

4. You set up a MongoDB replica set but notice that data is not replicating to secondary nodes. What is the most likely cause?

medium

A. The secondary nodes have more storage than the primary

B. The primary node is overloaded with queries

C. The replica set name is different on the secondary nodes

D. The network speed between nodes is too fast

Solution

1. Step 1: Check replica set configuration consistency

   All nodes must have the same replica set name to replicate data.

2. Step 2: Identify the cause of no replication

   If secondary nodes have a different replica set name, they won't join the set or replicate.

3. Final Answer:

   The replica set name is different on the secondary nodes -> Option C

4. Quick Check:

   Replica set name mismatch blocks replication [OK]

Hint: Replica set names must match on all nodes [OK]

Common Mistakes:

• Blaming primary overload for replication failure
• Thinking storage size affects replication
• Assuming faster network causes issues

5. You want to ensure your MongoDB database stays available even if two servers fail at the same time. How many nodes should your replica set have at minimum?

hard

A. 5 nodes

B. 3 nodes

C. 4 nodes

D. 6 nodes

Solution

1. Step 1: Understand majority voting in replica sets

   MongoDB replica sets use majority voting to elect a primary and stay available.

2. Step 2: Calculate nodes needed to tolerate 2 failures

   To tolerate 2 failures, majority must still be available. Majority is more than half nodes.

3. Step 3: Find minimum nodes for majority after 2 failures

   With 5 nodes, majority is 3. Losing 2 nodes leaves 3 nodes, so availability remains.

4. Final Answer:

   5 nodes -> Option A

5. Quick Check:

   5 nodes tolerate 2 failures with majority [OK]

Hint: Majority = more than half nodes; 5 nodes tolerate 2 failures [OK]

Common Mistakes:

• Choosing 3 or 4 nodes which can't tolerate 2 failures
• Not understanding majority voting
• Assuming even number nodes are better