Automatic failover behavior in MongoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What triggers automatic failover in MongoDB replica sets?

In a MongoDB replica set, what event causes the automatic failover process to start?

A When a secondary node finishes syncing data

B When the primary node becomes unreachable or stops responding

C When a client disconnects from the database

D When the replica set configuration is changed manually

💡 Hint

Think about what happens if the main server stops working.

Automatic failover starts when the primary node is unreachable or stops responding, so a new primary can be elected to keep the database available.

❓ query_result

intermediate

Result of election after primary failure

Given a MongoDB replica set with 3 members: one primary and two secondaries, if the primary goes down, what will be the state of the replica set after automatic failover?

A The replica set becomes unavailable until manual intervention

B All members become secondary

C The original primary remains primary despite being down

D One of the secondaries becomes the new primary, and the other remains secondary

💡 Hint

Think about how MongoDB keeps the database available after failure.

When the primary fails, one of the secondaries is elected as the new primary to maintain availability.

📝 Syntax

advanced

Identify the correct command to check replica set status

Which MongoDB shell command correctly shows the current status of the replica set, including primary and secondaries?

A show replSet

B db.replicaSetStatus()

C rs.status()

D rs.showStatus()

💡 Hint

It is a method of the rs object.

The rs.status() command returns detailed information about the replica set's current state.

❓ optimization

advanced

Optimizing failover time in MongoDB replica sets

Which configuration change can reduce the time it takes for automatic failover to complete in a MongoDB replica set?

A Decrease the electionTimeoutMillis setting

B Disable write concern majority

C Increase the heartbeatIntervalMillis setting

D Increase the priority of secondary nodes to zero

💡 Hint

Failover speed depends on how quickly nodes detect primary failure.

Lowering electionTimeoutMillis makes secondaries detect primary failure faster, triggering quicker elections.

🔧 Debug

expert

Diagnosing failover failure in MongoDB replica set

A MongoDB replica set does not perform automatic failover when the primary node goes down. Which of the following is the most likely cause?

A The majority of voting members are not available to elect a new primary

B The replica set has more than 3 members

C The heartbeatIntervalMillis is set too low

D The primary node has a higher priority than secondaries

💡 Hint

Think about what is needed for an election to succeed.

Failover requires a majority of voting members to be available to elect a new primary. If the majority is not reachable, failover cannot occur.

Practice

1. What is the main purpose of automatic failover in MongoDB replica sets?

easy

A. To backup data to an external storage device

B. To manually restart the database server when it crashes

C. To increase the speed of database queries

D. To switch to a backup server automatically if the primary server fails

Solution

1. Step 1: Understand automatic failover concept

   Automatic failover means the system switches servers without manual help when the main server fails.

2. Step 2: Identify the correct purpose in MongoDB context

   MongoDB replica sets use automatic failover to keep the database available by switching to a backup server automatically.

3. Final Answer:

   To switch to a backup server automatically if the primary server fails -> Option D

4. Quick Check:

   Automatic failover = automatic switch to backup [OK]

Hint: Automatic failover means automatic switch on failure [OK]

Common Mistakes:

• Thinking failover requires manual intervention
• Confusing failover with backup speed improvements
• Assuming failover backs up data externally

2. Which of the following is the correct way to initiate a replica set in MongoDB shell for automatic failover?

easy

A. db.startReplica()

B. rs.initiate()

C. replicaSet.start()

D. mongo.startReplicaSet()

Solution

1. Step 1: Recall MongoDB replica set initiation command

   The correct command to start a replica set in MongoDB shell is rs.initiate().

2. Step 2: Verify other options are invalid

   Commands like db.startReplica(), replicaSet.start(), and mongo.startReplicaSet() do not exist in MongoDB shell.

3. Final Answer:

   rs.initiate() -> Option B

4. Quick Check:

   Replica set start = rs.initiate() [OK]

Hint: Replica sets start with rs.initiate() command [OK]

Common Mistakes:

• Using non-existent commands to start replica sets
• Confusing database commands with shell commands
• Assuming replica sets start automatically without command

3. Given a MongoDB replica set with three members: Primary, Secondary1, and Secondary2. If the Primary goes down, what will happen automatically?

medium

A. Secondary1 and Secondary2 will both become Primary simultaneously

B. The database will stop accepting writes until manual restart

C. Secondary1 or Secondary2 will be elected as the new Primary

D. The replica set will shut down completely

Solution

1. Step 1: Understand replica set election process

   When the Primary fails, MongoDB automatically elects one Secondary as the new Primary.

2. Step 2: Analyze options for failover behavior

   Only one Secondary becomes Primary; the database continues accepting writes. The other options describe incorrect or impossible behaviors.

3. Final Answer:

   Secondary1 or Secondary2 will be elected as the new Primary -> Option C

4. Quick Check:

   Failover elects one Secondary as Primary [OK]

Hint: Failover elects one Secondary as new Primary [OK]

Common Mistakes:

• Thinking multiple Primaries can exist simultaneously
• Assuming manual restart is needed after Primary failure
• Believing the replica set shuts down on failure

4. You configured a MongoDB replica set but automatic failover is not happening when the primary goes down. What is a likely cause?

medium

A. The replica set has only one member

B. The primary server has too much RAM

C. The secondary servers are running on different OS

D. The replica set was initiated with rs.initiate()

Solution

1. Step 1: Check replica set member count requirement

   Automatic failover requires at least one secondary member to elect a new primary.

2. Step 2: Analyze given options

   If there is only one member, no election can happen, so failover won't work. Other options do not prevent failover.

3. Final Answer:

   The replica set has only one member -> Option A

4. Quick Check:

   Failover needs multiple members [OK]

Hint: Failover needs multiple members, not just one [OK]

Common Mistakes:

• Ignoring the need for multiple replica set members
• Blaming hardware specs for failover issues
• Assuming OS differences block failover

5. In a MongoDB replica set with 5 members, including 3 voting members and 2 non-voting members, what is the minimum number of voting members that must be available to trigger automatic failover?

hard

A. 2 voting members

B. 3 voting members

C. 1 voting member

D. 4 voting members

Solution

1. Step 1: Understand voting majority in replica sets

   Automatic failover requires a majority of voting members to elect a new primary.

2. Step 2: Calculate majority of 3 voting members

   Majority means more than half, so for 3 voting members, majority is 2.

3. Final Answer:

   2 voting members -> Option A

4. Quick Check:

   Majority of 3 voters = 2 [OK]

Hint: Majority of voting members needed for failover [OK]

Common Mistakes:

• Confusing total members with voting members
• Thinking all members must be available
• Miscounting majority as all or one