C100DEV Drivers, Tools, Transactions, and Search Practice Question
Which TWO of the following are common use cases for using the 'mongosh' shell in a production environment?
⚠ Common exam trap
Candidates incorrectly select heavy application-level automation tasks or high-throughput transaction routing as primary use cases for the interactive shell.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Querying and troubleshooting live collection data.
mongosh is the modern shell for MongoDB, offering a rich environment for database administration and scripting. Beyond simple CRUD, it is essential for checking cluster health, managing indexes, and performing emergency administrative tasks directly on the server. Because it provides full access to the MongoDB driver API, it is an indispensable tool for developers and DBAs to troubleshoot production issues and perform ad-hoc data investigations effectively.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Querying and troubleshooting live collection data.
Why this is correct
mongosh is the primary tool for executing ad-hoc queries, viewing document structures, and diagnosing data issues in production. Its ability to run standard CRUD operations and aggregation pipelines makes it the go-to tool for developers to inspect the state of the database when investigating reported bugs or inconsistencies.
- ✗
Developing the entirety of a high-concurrency Node.js application.
Why it's wrong here
While mongosh is excellent for database interaction, it is not an application development framework. Building a high-concurrency application requires proper IDEs, version control, build pipelines, and robust testing frameworks. Using mongosh for core application development would lack the necessary structure, security, and scalability required for modern software engineering.
- ✓
Performing administrative tasks like index creation and collection management.
Why this is correct
mongosh is the standard tool for database administration. Commands like db.collection.createIndex() are run directly in the shell. Managing schemas, indexes, and users via mongosh provides a direct, scriptable interface that is essential for maintaining database performance and security during the lifecycle of a production application deployment.
- ✗
Replacing the driver for all production database traffic.
Why it's wrong here
The shell is a client tool for humans and administrative scripts. It is not designed to handle the connection pooling, load balancing, or request routing required for high-traffic production application traffic. Using the shell for application database traffic would result in severe performance bottlenecks and lack of necessary error handling.
- ✗
Automatically scaling the number of nodes in an Atlas cluster.
Why it's wrong here
Scaling an Atlas cluster is an infrastructure operation handled through the Atlas UI or the Atlas API/CLI. While mongosh can query the database status, it does not have the administrative privileges or the architectural control to provision new nodes or modify the cluster tier settings directly from the console.
About these practice questions
One of 259 original C100DEV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official MongoDB exam blueprint
This C100DEV practice question is part of Courseiva's free MongoDB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C100DEV exam.