Atlas triggers overview in MongoDB - Mini Project: Build & Apply

Atlas Triggers Overview

📖 Scenario: You are managing a MongoDB Atlas database for an online bookstore. You want to automate some tasks when data changes happen in your collections.

🎯 Goal: Build a simple Atlas trigger setup that reacts to changes in the books collection and logs the changed document's title.

📋 What You'll Learn

Create a books collection with sample documents

Define a trigger configuration variable for the collection name

Write a trigger function that logs the title of the changed book document

Complete the trigger setup with event type and full function code

💡 Why This Matters

🌍 Real World

Atlas triggers automate actions in MongoDB Atlas when data changes, such as sending notifications or updating related data.

💼 Career

Understanding Atlas triggers is useful for database administrators and backend developers who want to automate workflows and maintain data integrity.

1

Create the books collection with sample documents

Create a variable called books that is a list of dictionaries. Add these exact entries: {'_id': 1, 'title': 'The Great Gatsby', 'author': 'F. Scott Fitzgerald'} and {'_id': 2, 'title': '1984', 'author': 'George Orwell'}.

MongoDB

# Create the books collection with two documents
# Your code here

Hint

Use a list with two dictionaries exactly as shown.

2

Define a trigger configuration variable

Create a variable called trigger_config and set it to a dictionary with the key collection and value 'books'.

MongoDB

books = [
    {'_id': 1, 'title': 'The Great Gatsby', 'author': 'F. Scott Fitzgerald'},
    {'_id': 2, 'title': '1984', 'author': 'George Orwell'}
]
# Define trigger configuration
# Your code here

Hint

Use a dictionary with key 'collection' and value 'books'.

3

Write the trigger function to log changed book titles

Define a function called log_changed_title that takes one parameter change_event. Inside, assign the variable title to change_event['fullDocument']['title'].

MongoDB

books = [
    {'_id': 1, 'title': 'The Great Gatsby', 'author': 'F. Scott Fitzgerald'},
    {'_id': 2, 'title': '1984', 'author': 'George Orwell'}
]

trigger_config = {'collection': 'books'}

# Define the trigger function
# Your code here

Hint

Define a function with the exact name and parameter, then assign the title from the change event.

4

Complete the trigger setup with event type and function body

Add a line inside log_changed_title that logs the title by assigning log_message = f"Changed book title: {title}". Then create a variable trigger as a dictionary with keys event set to 'change', collection set to trigger_config['collection'], and function set to log_changed_title.

MongoDB

books = [
    {'_id': 1, 'title': 'The Great Gatsby', 'author': 'F. Scott Fitzgerald'},
    {'_id': 2, 'title': '1984', 'author': 'George Orwell'}
]

trigger_config = {'collection': 'books'}

def log_changed_title(change_event):
    title = change_event['fullDocument']['title']
    # Add log message assignment here

# Define the trigger dictionary
# Your code here

Hint

Assign the log message inside the function and create the trigger dictionary with the specified keys and values.

Practice

1. What is the main purpose of an Atlas trigger in MongoDB?

easy

A. To create new collections in the database

B. To manually update documents in a collection

C. To backup the database automatically

D. To automatically run code when certain database events happen

Solution

1. Step 1: Understand what triggers do

   Atlas triggers run code automatically when specific events occur in the database, like inserts or updates.

2. Step 2: Compare options with this purpose

   Only To automatically run code when certain database events happen describes automatic code running on database events, which matches the trigger's purpose.

3. Final Answer:

   To automatically run code when certain database events happen -> Option D

4. Quick Check:

   Atlas triggers = automatic code on events [OK]

Hint: Triggers run code automatically on database events [OK]

Common Mistakes:

• Thinking triggers are for manual updates
• Confusing triggers with backups
• Assuming triggers create collections

2. Which of the following is the correct way to define a function for an Atlas trigger?

easy

A. function triggerFunction() { console.log('Triggered'); }

B. def triggerFunction(): print('Triggered')

C. triggerFunction() => { console.log('Triggered'); }

D. func triggerFunction() { print('Triggered') }

Solution

1. Step 1: Identify the language used in Atlas triggers

   Atlas triggers use JavaScript functions to define actions.

2. Step 2: Check which option is valid JavaScript function syntax

   function triggerFunction() { console.log('Triggered'); } uses standard JavaScript function syntax. Options A and D use Python and Go syntax, and C is invalid arrow function syntax.

3. Final Answer:

   function triggerFunction() { console.log('Triggered'); } -> Option A

4. Quick Check:

   Atlas triggers use JavaScript functions [OK]

Hint: Atlas triggers use JavaScript function syntax [OK]

Common Mistakes:

• Using Python or other language syntax
• Incorrect arrow function syntax
• Missing function keyword in JavaScript

3. Given this Atlas trigger function, what will be logged when a new document is inserted?

exports = function(changeEvent) {
  console.log('Document inserted with _id:', changeEvent.fullDocument._id);
};

medium

A. Document inserted with _id: [actual document _id]

B. No output because console.log is not supported

C. Error: changeEvent is not defined

D. Document inserted with _id: undefined

Solution

1. Step 1: Understand the changeEvent object in insert triggers

   When a document is inserted, changeEvent.fullDocument contains the new document, including its _id.

2. Step 2: Analyze the console.log statement

   The function logs the string plus the _id from the inserted document, so it outputs the actual _id value.

3. Final Answer:

   Document inserted with _id: [actual document _id] -> Option A

4. Quick Check:

   changeEvent.fullDocument._id logs inserted document ID [OK]

Hint: Insert triggers have fullDocument with new data [OK]

Common Mistakes:

• Assuming _id is undefined
• Thinking changeEvent is undefined
• Believing console.log doesn't work in triggers

4. You wrote this Atlas trigger function but it does not run as expected:

exports = function(changeEvent) {
  console.log('Change detected');
}

What is a likely reason it does not trigger?

medium

A. console.log is not allowed in triggers

B. The function syntax is invalid

C. The trigger is not linked to any database event

D. changeEvent parameter is missing

Solution

1. Step 1: Check function syntax and parameters

   The function syntax is correct and the changeEvent parameter is present, so no syntax error.

2. Step 2: Consider trigger configuration

   If the trigger is not linked to any database event or schedule, it will not run despite correct code.

3. Final Answer:

   The trigger is not linked to any database event -> Option C

4. Quick Check:

   Triggers must be linked to events to run [OK]

Hint: Check trigger event linkage if function doesn't run [OK]

Common Mistakes:

• Assuming console.log is disallowed
• Thinking syntax error causes no run
• Ignoring trigger event configuration

5. You want to create an Atlas trigger that runs every day at midnight to archive old documents. Which trigger type should you choose?

hard

A. Database trigger on insert event

B. Scheduled trigger with a cron expression

C. Database trigger on update event

D. Manual trigger run from the UI

Solution

1. Step 1: Identify trigger types for scheduled tasks

   Atlas supports scheduled triggers that run based on time using cron expressions.

2. Step 2: Match the requirement to trigger type

   To run daily at midnight, a scheduled trigger with a cron expression is the correct choice.

3. Final Answer:

   Scheduled trigger with a cron expression -> Option B

4. Quick Check:

   Scheduled triggers = run code on time schedule [OK]

Hint: Use scheduled triggers for time-based automation [OK]

Common Mistakes:

• Choosing database triggers for time schedules
• Thinking manual triggers run automatically
• Confusing insert/update triggers with scheduled