Atlas data federation concept in MongoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Atlas Data Federation?

Atlas Data Federation allows you to query data from multiple sources as if they were one. What is the main benefit of this feature?

A It automatically backs up your data to multiple regions for disaster recovery.

B It lets you combine data from different databases and cloud services without moving the data.

C It encrypts your data at rest and in transit for security compliance.

D It creates a single database instance that stores all your data physically in one place.

💡 Hint

Think about how you can access data without copying or moving it.

Atlas Data Federation lets you query data across multiple sources like Atlas clusters, S3 buckets, or other databases without physically moving the data. This simplifies data access and integration.

❓ query_result

intermediate

What is the output of this Atlas Data Federation query?

Assume you have two collections: users in Atlas cluster and orders in an S3 bucket. You run this query in Atlas Data Federation:

db.users.aggregate([
  { $lookup: {
      from: "orders",
      localField: "user_id",
      foreignField: "user_id",
      as: "user_orders"
  }},
  { $match: { "user_orders.0": { $exists: true } } }
])

What does this query return?

A An error because $lookup cannot join collections from different data sources.

B All orders that have a matching user, with user details included in each order document.

C All users, regardless of orders, with an empty user_orders array for those without orders.

D All users who have at least one order, with their orders included in the user_orders array.

💡 Hint

Look at the $match stage filtering on user_orders.0 existence.

The $lookup stage joins users with orders by user_id, creating an array user_orders. The $match stage filters to only users with at least one order (user_orders.0 exists). So the result is users who have orders, with those orders included.

📝 Syntax

advanced

Which option correctly defines a data source in Atlas Data Federation configuration?

You want to add an S3 bucket as a data source in Atlas Data Federation. Which JSON snippet is syntactically correct for this configuration?

A { name: "myS3Source", type: "s3", config: { "bucket": "my-bucket", "region": "us-east-1" } }

B { "name": "myS3Source", "type": "s3", "config": { bucket: "my-bucket", region: "us-east-1" } }

C { "name": "myS3Source", "type": "s3", "config": { "bucket": "my-bucket", "region": "us-east-1" } }

D { "name": "myS3Source", "type": "s3", "config": { "bucket": "my-bucket" "region": "us-east-1" } }

💡 Hint

Remember JSON keys and string values must be in double quotes and commas separate items.

Option C uses correct JSON syntax with double quotes around keys and string values, and commas separating key-value pairs. Option C and C miss quotes or use invalid JSON syntax. Option C misses a comma between bucket and region.

❓ optimization

advanced

How can you optimize queries in Atlas Data Federation when joining large datasets?

You have a query joining a large Atlas collection with a large S3 dataset using $lookup. What is the best way to improve query performance?

A Use $match before $lookup to reduce the number of documents processed in the join.

B Increase the Atlas cluster size to handle more data during the join.

C Use $project after $lookup to remove unwanted fields from the joined documents.

D Split the query into two separate queries and join results in application code.

💡 Hint

Filtering early reduces data processed in joins.

Applying $match before $lookup filters documents early, reducing the amount of data the join processes, which improves performance. Increasing cluster size helps but is costlier and less efficient. $project after $lookup reduces output size but doesn't reduce join workload. Splitting queries adds complexity and network overhead.

🔧 Debug

expert

Why does this Atlas Data Federation query fail with a 'NamespaceNotFound' error?

You run this query:

db.sales.aggregate([
  { $match: { amount: { $gt: 100 } } }
])

But get an error: NamespaceNotFound: sales not found. The 'sales' collection exists in your Atlas cluster but not in the S3 bucket data source. Your federation data source includes both Atlas and S3. What is the cause?

A The query is run against the federation view that does not include the 'sales' collection from Atlas cluster.

B The 'sales' collection name is misspelled in the query.

C Atlas Data Federation does not support $match on numeric fields.

D The user running the query lacks read permissions on the 'sales' collection.

💡 Hint

Check which data sources are included in your federation configuration.

The error means the 'sales' collection is not found in the data sources configured for the federation. If the federation view excludes the Atlas cluster or the 'sales' collection, the query fails. Misspelling or permissions would cause different errors. $match on numeric fields is supported.