Why the paradigm shift matters in MongoDB - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is MongoDB considered a paradigm shift from traditional relational databases?

Choose the best explanation for why MongoDB represents a paradigm shift compared to relational databases.

A MongoDB stores data in flexible JSON-like documents instead of fixed tables, allowing easier handling of varied data.

B MongoDB requires strict schemas and joins like relational databases, making it similar in design.

C MongoDB uses SQL queries exclusively, which is the same as relational databases.

D MongoDB only supports storing data in flat files without indexing.

💡 Hint

Think about how data is stored and structured differently in MongoDB.

MongoDB stores data as flexible documents, unlike relational databases that use fixed tables. This flexibility allows easier changes and varied data types.

❓ query_result

intermediate

What is the output of this MongoDB query?

Given a collection 'users' with documents: {name: 'Alice', age: 30}, {name: 'Bob', age: 25}, {name: 'Carol', age: 30}, what does this query return?

db.users.find({age: 30})

MongoDB

db.users.find({age: 30})

A [{name: 'Bob', age: 25}]

B [{name: 'Alice', age: 30}, {name: 'Carol', age: 30}]

C []

D SyntaxError

💡 Hint

The query filters documents where age equals 30.

The query finds all documents where the 'age' field is 30, so it returns Alice and Carol's documents.

📝 Syntax

advanced

Which MongoDB query syntax correctly updates a user's age?

You want to update the age of the user named 'Bob' to 28. Which query is correct?

A db.users.updateOne({name: 'Bob'}, {$set: {age: 28}})

B db.users.update({name: 'Bob'}, {age: 28})

C db.users.updateOne({name: 'Bob'}, {age: 28})

D db.users.updateOne({name: 'Bob'}, {$age: 28})

💡 Hint

Remember that updates require an operator like $set to modify fields.

The correct syntax uses updateOne with a filter and the $set operator to change the age field.

❓ optimization

advanced

How can you optimize queries on a large MongoDB collection for the 'email' field?

You have a large collection of users and often query by 'email'. What is the best way to optimize these queries?

A Avoid querying by 'email' and scan all documents instead.

B Store emails in a separate collection to reduce size.

C Use a text search on the 'email' field without indexing.

D Create an index on the 'email' field to speed up lookups.

💡 Hint

Indexes help databases find data faster.

Creating an index on the 'email' field allows MongoDB to quickly locate documents without scanning the entire collection.

🔧 Debug

expert

What error does this MongoDB aggregation pipeline produce?

Consider this aggregation pipeline:

db.orders.aggregate([ {$match: {status: 'shipped'}}, {$group: {_id: '$customerId', total: {$sum: '$amount'}}}, {$sort: {total: -1}}, {$project: {customerId: '$_id', total: 1, _id: 0}} ])

What error will this pipeline cause?

A Runtime error because $project references '$_id' incorrectly.

B SyntaxError due to missing commas between stages.

C No error; it returns total amounts per customer sorted descending.

D Aggregation error because $sum cannot be used inside $group.

💡 Hint

Check each stage for correct syntax and usage.

The pipeline correctly matches shipped orders, groups by customerId summing amounts, sorts descending, and projects the fields properly. No error occurs.