C100DEV Drivers, Tools, Transactions, and Search Practice Question
A developer wants to run ad-hoc queries against a MongoDB Atlas cluster from a terminal, including commands like db.collection.find() and db.adminCommand({listDatabases: 1}). The developer has the connection string and wants the least additional setup. Which tool should be used?
⚠ Common exam trap
The trap here is equating any MongoDB client that can connect to Atlas with a terminal shell, when only mongosh provides interactive command-line querying without extra setup.
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
✓
mongosh with the connection string passed as an argument
mongosh is the official MongoDB Shell and is designed for interactive, terminal-based querying and administration. It connects directly with a connection string and supports both CRUD helpers and database commands, so it covers the developer's needs with minimal setup. GUI tools, backup utilities, and federation features serve different purposes and would require more configuration or would not run in a terminal.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
MongoDB Compass connected to the cluster
Why it's wrong here
Compass is a GUI, not a terminal tool, so it does not satisfy the requirement to run commands from a terminal. While it can execute queries and some administrative operations through its interface, it involves installing and launching a desktop application. For ad-hoc command-line querying with minimal setup, Compass is the wrong category of tool even though it can connect to the same Atlas cluster.
- ✓
mongosh with the connection string passed as an argument
Why this is correct
mongosh is the MongoDB Shell that connects to any deployment, including Atlas, using a standard connection string. It supports JavaScript execution, database commands, and helpers like db.collection.find(), and it requires no additional project scaffolding. Passing the connection string as an argument is the documented way to connect, making it the least-setup option for ad-hoc querying and administrative commands in a terminal.
- ✗
Atlas Data Federation with an S3 data source
Why it's wrong here
Atlas Data Federation is a feature for querying data across Atlas and external sources like S3, not a terminal client for ad-hoc queries against a cluster. Setting it up involves configuring federated database instances and storage mappings, which is far more than the least additional setup the scenario requires. It also does not replace mongosh for running db.collection.find() interactively.
- ✗
mongodump with the --uri option
Why it's wrong here
mongodump creates binary backups of a deployment; it does not provide an interactive shell for running find() queries or adminCommand calls. Using it against Atlas would produce a dump rather than the ad-hoc query capability the developer needs. Although it accepts a URI, its purpose is data extraction for backup and restore workflows, not interactive command execution, so it is not suitable here.
About these practice questions
This C100DEV question is part of Courseiva's 259-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.