Election process concept in MongoDB - Step-by-Step Execution

Concept Flow - Election process concept

Start Election

↓

Candidates Register

↓

Voters Cast Votes

↓

Count Votes

↓

Determine Winner

↓

Announce Results

↓

End Election

This flow shows the steps in an election: candidates register, voters vote, votes are counted, winner is determined, and results announced.

Execution Sample

MongoDB

db.votes.insertMany([
  { voter: "Alice", candidate: "John" },
  { voter: "Bob", candidate: "Mary" },
  { voter: "Carol", candidate: "John" }
])

// Count votes per candidate

db.votes.aggregate([
  { $group: { _id: "$candidate", totalVotes: { $sum: 1 } } },
  { $sort: { totalVotes: -1 } }
])

This code records votes and counts how many votes each candidate received, sorting from most to least.

Execution Table

Step	Action	Data State	Result
1	Insert vote {voter: 'Alice', candidate: 'John'}	votes collection empty	votes collection has 1 document
2	Insert vote {voter: 'Bob', candidate: 'Mary'}	votes collection has 1 document	votes collection has 2 documents
3	Insert vote {voter: 'Carol', candidate: 'John'}	votes collection has 2 documents	votes collection has 3 documents
4	Aggregate votes by candidate	votes collection has 3 documents	John: 2 votes, Mary: 1 vote
5	Sort candidates by votes descending	Aggregated result	John first, Mary second
6	Determine winner	Sorted result	John is winner with 2 votes
7	Announce results	Winner determined	Election results published
8	End election	Results announced	Election process complete

💡 All votes counted and winner determined, election process ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
votes collection	empty	1 document	2 documents	3 documents	3 documents	3 documents	3 documents	3 documents
aggregated result	none	none	none	none	{John:2, Mary:1}	{John:2, Mary:1}	{John:2, Mary:1}	{John:2, Mary:1}
winner	none	none	none	none	none	none	John	John

Key Moments - 3 Insights

Why do we group votes by candidate in the aggregation?

Grouping by candidate (see Step 4 in execution_table) counts all votes per candidate, which is necessary to find who has the most votes.

Why sort the aggregated results by total votes?

Sorting (Step 5) puts the candidate with the highest votes first, making it easy to pick the winner (Step 6).

What happens if two candidates have the same number of votes?

The current process does not handle ties explicitly; additional logic would be needed after Step 5 to check for ties.

Visual Quiz - 3 Questions

Look at the execution_table, how many votes does 'John' have after Step 4?

A 1

B 3

C 2

D 0

💡 Hint

Check the 'Data State' and 'Result' columns at Step 4 in execution_table.

At which step is the winner determined?

A Step 6

B Step 5

C Step 4

D Step 7

💡 Hint

Look for the 'Determine winner' action in the execution_table.

If a new vote for 'Mary' is added after Step 3, how would the aggregated votes for 'Mary' change at Step 4?

A Mary would have 1 vote

B Mary would have 2 votes

C Mary would have 3 votes

D Mary would have 0 votes

💡 Hint

Refer to variable_tracker for votes collection size and aggregation logic at Step 4.

Concept Snapshot

Election process in MongoDB:
1. Insert votes as documents with voter and candidate fields.
2. Use aggregation to group votes by candidate.
3. Sort candidates by total votes descending.
4. The top candidate is the winner.
5. Announce results and end election.
This process counts votes and finds the winner efficiently.

Full Transcript

The election process in MongoDB starts by inserting votes as documents into a collection. Each vote records the voter and their chosen candidate. After all votes are inserted, an aggregation groups votes by candidate to count how many votes each received. The results are sorted so the candidate with the most votes is first. This candidate is declared the winner. Finally, the results are announced and the election ends. This step-by-step process ensures votes are counted correctly and the winner is determined fairly.

Practice

1. What is the main purpose of an election in a MongoDB replica set?

easy

A. To select a primary server that manages writes

B. To delete old data from the database

C. To backup the database automatically

D. To create new collections in the database

Solution

1. Step 1: Understand the role of election in MongoDB

   In a replica set, election chooses a primary server to handle write operations.

2. Step 2: Identify the correct purpose

   The primary server manages writes and coordinates data replication.

3. Final Answer:

   To select a primary server that manages writes -> Option A

4. Quick Check:

   Election = select primary server [OK]

Hint: Election picks the primary server for writes [OK]

Common Mistakes:

• Thinking election deletes data
• Confusing election with backup process
• Believing election creates collections

2. Which MongoDB command shows the current election status in a replica set?

easy

A. db.showElection()

B. db.electionStatus()

C. rs.status()

D. rs.election()

Solution

1. Step 1: Recall the command to check replica set status

   The command rs.status() shows detailed replica set info including election status.

2. Step 2: Verify other options

   Other commands like db.showElection() or rs.election() do not exist in MongoDB.

3. Final Answer:

   rs.status() -> Option C

4. Quick Check:

   Check election with rs.status() [OK]

Hint: Use rs.status() to see election info [OK]

Common Mistakes:

• Using non-existent commands
• Confusing db commands with rs commands
• Trying to use election-specific commands that don't exist

3. Given the following output from rs.status(), which member is currently the primary?

{
  "members": [
    {"_id": 0, "stateStr": "SECONDARY"},
    {"_id": 1, "stateStr": "PRIMARY"},
    {"_id": 2, "stateStr": "SECONDARY"}
  ]
}

medium

A. Member with _id 0

B. No primary elected yet

C. Member with _id 2

D. Member with _id 1

Solution

1. Step 1: Read the stateStr values for each member

   Member with _id 1 has stateStr "PRIMARY", others are "SECONDARY".

2. Step 2: Identify the primary member

   The member with stateStr "PRIMARY" is the current primary server.

3. Final Answer:

   Member with _id 1 -> Option D

4. Quick Check:

   Primary = stateStr "PRIMARY" member [OK]

Hint: Primary member has stateStr 'PRIMARY' in rs.status() [OK]

Common Mistakes:

• Choosing a secondary member
• Assuming no primary if unsure
• Ignoring the stateStr field

4. You run rs.status() but get an error: not authorized on admin to execute command. What is the likely cause?

medium

A. You lack proper user permissions to run rs.status()

B. You are not connected to the primary server

C. The replica set is not initialized

D. The command rs.status() is misspelled

Solution

1. Step 1: Understand the error message

   The error says 'not authorized', meaning permission is denied.

2. Step 2: Match error to cause

   Lack of user permissions to run the command causes this error, not connection or spelling issues.

3. Final Answer:

   You lack proper user permissions to run rs.status() -> Option A

4. Quick Check:

   Authorization error = permission issue [OK]

Hint: Authorization errors mean missing user permissions [OK]

Common Mistakes:

• Assuming connection problem
• Thinking replica set not initialized
• Blaming command spelling

5. In a MongoDB replica set with 5 members, what minimum number of votes is needed to elect a primary during an election?

hard

A. 2 votes

B. 3 votes

C. 4 votes

D. 5 votes

Solution

1. Step 1: Recall election voting rules in MongoDB

   Primary election requires a majority of votes from members.

2. Step 2: Calculate majority for 5 members

   Majority is more than half, so 3 out of 5 votes are needed.

3. Final Answer:

   3 votes -> Option B

4. Quick Check:

   Majority of 5 = 3 votes [OK]

Hint: Majority votes needed: half members + 1 [OK]

Common Mistakes:

• Choosing half votes instead of majority
• Thinking all members must vote
• Confusing votes with number of members