Atlas data federation concept in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the data source for Atlas Data Federation.

MongoDB

db.[1].find()

Drag options to blanks, or click blank then click option'

AtempCollection

BlocalCollection

CexternalDB

DfederatedCollection

Attempts:

3 left

💡 Hint

Common Mistakes

Using a local collection name instead of the federated one.

Atlas Data Federation uses a federated collection name to query data across multiple sources.

2fill in blank

medium

Complete the code to filter documents where the field 'status' equals 'active' in Atlas Data Federation.

MongoDB

db.federatedCollection.find({ 'status': [1] })

Drag options to blanks, or click blank then click option'

A'active'

Bactive

C"active"

Dactive"

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted strings which are invalid.

In MongoDB queries, string values must be enclosed in quotes. Single or double quotes are acceptable in JavaScript, but in JSON-like query objects, single quotes are not valid JSON. However, in MongoDB shell, single quotes are acceptable. Therefore, 'active' is the correct choice here.

3fill in blank

hard

Fix the error in the aggregation pipeline to group documents by 'category' in Atlas Data Federation.

MongoDB

db.federatedCollection.aggregate([ { $group: { _id: [1], count: { $sum: 1 } } } ])

Drag options to blanks, or click blank then click option'

A"$category"

Bcategory

C"category"

D{category}

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the $ prefix, using unquoted field names, or literal strings without $.

The _id field in $group stage must use the field path "$category" to group documents by the category field.

4fill in blank

hard

Fill both blanks to project only 'name' and 'email' fields in the Atlas Data Federation query.

MongoDB

db.federatedCollection.find({}, { [1]: 1, [2]: 1 })

Drag options to blanks, or click blank then click option'

Aname

Bemail

Cstatus

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Including wrong fields or forgetting to set fields to 1.

Projection specifies which fields to include by setting them to 1 in the second argument of find().

5fill in blank

hard

Fill all three blanks to sort the federated data by 'createdAt' descending and limit results to 5.

MongoDB

db.federatedCollection.find().sort({ [1]: [2] }).limit([3])

Drag options to blanks, or click blank then click option'

AcreatedAt

B-1

C5

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1 instead of -1 for descending or wrong limit number.

Sorting by 'createdAt' descending uses -1, and limit specifies how many documents to return.

Practice

1. What is the main purpose of MongoDB Atlas Data Federation?

easy

A. To query data from multiple sources as if they were one database

B. To create backups of MongoDB databases automatically

C. To optimize single-node MongoDB performance

D. To convert SQL queries into MongoDB queries

Solution

1. Step 1: Understand the concept of Atlas Data Federation

   Atlas Data Federation allows querying data from different sources like cloud object stores and databases as a single database.

2. Step 2: Identify the main purpose

   The main goal is to simplify querying distributed data by treating it as one unified database.

3. Final Answer:

   To query data from multiple sources as if they were one database -> Option A

4. Quick Check:

   Atlas Data Federation = Unified querying [OK]

Hint: Think 'one query, many sources' for Atlas Federation [OK]

Common Mistakes:

• Confusing federation with backup features
• Thinking it only optimizes single-node performance
• Assuming it translates SQL queries automatically

2. Which of the following is the correct way to create a federated database in MongoDB Atlas Data Federation?

easy

A. Run a MongoDB shell command: createFederatedDB()

B. Use the Atlas UI to define data sources and create a federated database

C. Install a special MongoDB plugin on your local machine

D. Write a SQL script to link data sources

Solution

1. Step 1: Recall how federated databases are created

   Atlas Data Federation uses the Atlas web interface to configure data sources and create federated databases.

2. Step 2: Evaluate the options

   Only the Atlas UI method is correct; there is no shell command or plugin for this, nor SQL scripts.

3. Final Answer:

   Use the Atlas UI to define data sources and create a federated database -> Option B

4. Quick Check:

   Federated DB creation = Atlas UI [OK]

Hint: Atlas UI is your tool for federation setup [OK]

Common Mistakes:

• Trying to create federated DB via shell commands
• Looking for local plugins instead of cloud setup
• Using SQL scripts which are not supported

3. Given a federated database combining a MongoDB collection and an S3 bucket, what will the following query return?

db.federatedCollection.find({"type": "image"})

medium

A. Only files from S3 bucket with type 'image'

B. Only documents from MongoDB collection with type 'image'

C. Documents from MongoDB collection and files from S3 with type 'image'

D. An error because S3 data cannot be queried

Solution

1. Step 1: Understand federated query behavior

   Atlas Data Federation allows querying multiple sources like MongoDB and S3 as one collection.

2. Step 2: Analyze the query

   The query filters documents/files where the field "type" equals "image" across all federated sources.

3. Final Answer:

   Documents from MongoDB collection and files from S3 with type 'image' -> Option C

4. Quick Check:

   Federated query returns combined matching data [OK]

Hint: Federated queries combine all sources transparently [OK]

Common Mistakes:

• Assuming only MongoDB data is returned
• Thinking S3 data cannot be queried
• Expecting an error due to mixed sources

4. You wrote this query on a federated database:

db.federatedCollection.find({"status": "active"})

But it returns no results, even though you know some data has status 'active'. What could be the problem?

medium

A. You must use SQL syntax instead of MongoDB queries

B. The query syntax is invalid for federated databases

C. MongoDB Atlas does not support filtering on 'status' field

D. The federated database was not properly linked to all data sources

Solution

1. Step 1: Check query correctness

   The query syntax is valid MongoDB syntax and filtering on 'status' is supported.

2. Step 2: Consider federation setup

   If no results appear, likely the federated database is missing some data sources or not linked properly.

3. Final Answer:

   The federated database was not properly linked to all data sources -> Option D

4. Quick Check:

   Missing data sources cause empty results [OK]

Hint: Check federation links if queries return no data [OK]

Common Mistakes:

• Blaming query syntax instead of setup
• Thinking Atlas forbids filtering on fields
• Trying to use SQL syntax in MongoDB queries

5. You want to create a federated database that combines a MongoDB Atlas cluster, an S3 bucket, and a Google Cloud Storage bucket. Which of the following is true about querying this federated database?

hard

A. You can run a single MongoDB query that returns matching data from all three sources

B. You must query each source separately and merge results manually

C. Federation supports only two sources at a time, so you must create two federated databases

D. You can only query MongoDB Atlas data; cloud storage buckets are read-only

Solution

1. Step 1: Understand multi-source federation

   Atlas Data Federation supports combining multiple data sources including MongoDB Atlas and various cloud storage buckets.

2. Step 2: Query behavior on federated database

   A single MongoDB query can access and return matching data from all linked sources transparently.

3. Final Answer:

   You can run a single MongoDB query that returns matching data from all three sources -> Option A

4. Quick Check:

   Federation = unified multi-source queries [OK]

Hint: Federation lets one query cover many sources [OK]

Common Mistakes:

• Thinking you must query sources separately
• Believing federation limits to two sources
• Assuming cloud buckets are read-only and not queryable