Denormalization trade-offs in MongoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Denormalization Benefits

Which of the following is a primary benefit of denormalization in MongoDB?

A Improves read performance by reducing the need for joins

B Eliminates data duplication completely

C Ensures strict data consistency without extra effort

D Automatically normalizes data during writes

💡 Hint

Think about how denormalization affects data retrieval speed.

Denormalization stores related data together, reducing the need for joins and improving read speed. However, it can increase data duplication and complicate consistency.

❓ query_result

intermediate

Result of a Denormalized Query

Given a MongoDB collection orders where each document embeds customer info, what will this query return?

db.orders.find({"customer.name": "Alice"})

MongoDB

db.orders.find({"customer.name": "Alice"})

A All customers named 'Alice' from a separate customers collection

B An error because embedded fields cannot be queried

C All orders where the embedded customer name is 'Alice'

D Only orders with a customer field missing

💡 Hint

Remember how embedded documents are queried in MongoDB.

MongoDB allows querying inside embedded documents using dot notation. This query returns orders where the embedded customer name is 'Alice'.

❓ optimization

advanced

Optimizing Updates in Denormalized Data

You have denormalized customer address data embedded in many order documents. Which approach best minimizes update complexity when a customer changes address?

A Update the address in every order document where it appears

B Store address only in a separate collection and reference it in orders

C Remove the address field from orders and never update it

D Duplicate the address in orders and ignore updates

💡 Hint

Consider how references affect update operations.

Storing address in a separate collection and referencing it avoids multiple updates. Denormalization improves reads but complicates writes when data is duplicated.

🔧 Debug

advanced

Identifying Consistency Issues in Denormalized Data

Consider this scenario: customer phone numbers are embedded in orders. After updating a customer's phone number in the customers collection, some orders still show the old number. What is the cause?

A Orders collection does not support embedded documents

B MongoDB automatically syncs embedded data, so this is impossible

C The update query was incorrect and did not change the customers collection

D Denormalized phone numbers in orders were not updated, causing inconsistency

💡 Hint

Think about how denormalization affects data duplication and consistency.

Denormalization duplicates data. Updating the original source does not automatically update embedded copies, causing stale data in orders.

🧠 Conceptual

expert

Trade-offs of Denormalization in MongoDB

Which statement best describes a key trade-off when choosing denormalization over normalization in MongoDB?

A Denormalization improves read speed but increases complexity of write operations and data consistency management

B Denormalization eliminates the need for indexes, simplifying queries

C Normalization always results in faster queries than denormalization

D Denormalization guarantees zero data duplication and easier backups

💡 Hint

Consider how denormalization affects reads, writes, and data duplication.

Denormalization speeds up reads by embedding data but requires careful handling of writes and consistency due to duplicated data.

Practice

1. What is a main advantage of denormalization in MongoDB?

easy

A. Faster read operations by storing related data together

B. Simpler updates with no data duplication

C. Reduced storage space by avoiding repeated data

D. Automatic data consistency without extra effort

Solution

1. Step 1: Understand denormalization purpose

   Denormalization stores related data together to speed up reading.

2. Step 2: Compare options with this purpose

   Only Faster read operations by storing related data together mentions faster reads by storing data together, which matches denormalization benefits.

3. Final Answer:

   Faster read operations by storing related data together -> Option A

4. Quick Check:

   Denormalization = Faster reads [OK]

Hint: Denormalization speeds up reads by grouping data [OK]

Common Mistakes:

• Confusing denormalization with normalization benefits
• Thinking denormalization reduces storage space
• Assuming denormalization simplifies updates

2. Which MongoDB document structure shows denormalization?

easy

A. { _id: 1, name: 'Alice' }, { _id: 101, total: 50 }

B. { _id: 1, name: 'Alice', orders: [{id: 101, total: 50}] }

C. { _id: 1, name: 'Alice' }, orders: 101

D. { _id: 1, orders: [101] }

Solution

1. Step 1: Identify denormalized data structure

   Denormalization stores related data inside one document, like embedding orders inside a user document.

2. Step 2: Check options for embedded data

   { _id: 1, name: 'Alice', orders: [{id: 101, total: 50}] } embeds orders array inside user document, showing denormalization.

3. Final Answer:

   { _id: 1, name: 'Alice', orders: [{id: 101, total: 50}] } -> Option B

4. Quick Check:

   Embedded orders = Denormalization [OK]

Hint: Look for embedded arrays inside documents [OK]

Common Mistakes:

• Choosing separate documents as denormalized
• Confusing references with embedded data
• Ignoring array embedding as denormalization

3. Given this denormalized document:

{ _id: 1, name: 'Bob', address: { city: 'NY', zip: '10001' } }

What happens if Bob moves to 'LA' and you update only the city in this document?

medium

A. Update fails due to embedded document structure

B. All references to Bob's city update automatically

C. Only this document's city changes; duplicates elsewhere stay old

D. MongoDB merges old and new city values

Solution

1. Step 1: Understand update impact in denormalization

   Denormalization duplicates data, so updating one copy doesn't affect others.

2. Step 2: Analyze update effect on embedded address

   Updating city in one document changes only that document; duplicates elsewhere remain unchanged.

3. Final Answer:

   Only this document's city changes; duplicates elsewhere stay old -> Option C

4. Quick Check:

   Update one copy, duplicates unchanged [OK]

Hint: Updates affect only one copy in denormalized data [OK]

Common Mistakes:

• Assuming all duplicates update automatically
• Thinking embedded documents prevent updates
• Believing MongoDB merges conflicting values

4. You have duplicated user phone numbers in multiple documents due to denormalization. Which is a common problem you might face?

medium

A. Updating phone number requires changing all documents manually

B. MongoDB automatically syncs all duplicates on update

C. Phone numbers cannot be stored in embedded documents

D. Denormalization prevents querying phone numbers

Solution

1. Step 1: Identify update challenges with duplicated data

   Duplicated data means updates must be applied to every copy to keep consistency.

2. Step 2: Evaluate options about update behavior

   Only Updating phone number requires changing all documents manually correctly states that manual updates to all duplicates are needed.

3. Final Answer:

   Updating phone number requires changing all documents manually -> Option A

4. Quick Check:

   Manual update needed for duplicates [OK]

Hint: Duplicates need manual updates to stay consistent [OK]

Common Mistakes:

• Believing MongoDB auto-syncs duplicates
• Thinking denormalization forbids embedded fields
• Assuming denormalization blocks queries

5. You want to design a MongoDB schema for a blog where posts have many comments. You expect many reads but few comment edits. Which denormalization approach is best?

hard

A. Duplicate comments in both posts and a separate collection

B. Store comments in a separate collection and reference post IDs

C. Store only comment IDs inside posts without comment data

D. Embed all comments inside each post document

Solution

1. Step 1: Analyze read vs update frequency

   Many reads and few updates favor denormalization to speed up reads.

2. Step 2: Choose schema matching denormalization benefits

   Embedding comments inside posts (Embed all comments inside each post document) stores related data together for fast reads.

3. Step 3: Consider update cost

   Few comment edits mean duplicated data update cost is low, so embedding is suitable.

4. Final Answer:

   Embed all comments inside each post document -> Option D

5. Quick Check:

   Many reads + few updates = Embed data [OK]

Hint: Embed when reads >> updates for faster access [OK]

Common Mistakes:

• Choosing references despite many reads
• Duplicating data unnecessarily increasing update cost
• Ignoring update frequency in design