C100DBA Exam Simulation 1 — 100 Questions

Question 1

A startup is building a content management system where the document structure varies significantly between blog posts, product pages, and user profiles. Which fundamental MongoDB philosophy best supports this requirement?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Flexible schema design allows documents in the same collection to have different fields.. MongoDB’s flexible schema design allows developers to store heterogeneous data types within the same collection. Unlike rigid relational schemas that necessitate complex migrations or NULL-heavy tables for varying attributes, document-oriented storage enables an agile development lifecycle. This philosophy prioritizes developer productivity and adaptability, allowing application code to dictate structure rather than being constrained by predefined table schemas that require frequent and disruptive database-level modifications.

Answer

Normalization ensures data integrity for varying document structures.

Answer

Strict schema validation enforces identical fields across all documents.

Answer

Fixed-length record storage improves indexing speed for variable data.

Question 2

Why does MongoDB choose the BSON format over JSON for storage?

Accepted Answer

BSON allows for faster traversal and efficient type identification.. BSON (Binary JSON) extends JSON to provide additional data types and efficient encoding for machine processing. By including length prefixes and type information, the database can traverse documents quickly without needing to parse the entire structure. This binary efficiency is crucial for database performance, allowing the storage engine to perform faster lookups, sorting, and field-level operations that would be significantly slower if it had to interpret raw text-based JSON during every query execution.

Answer

BSON is human-readable and easier to debug than JSON.

Answer

BSON supports fewer data types than standard JSON.

Answer

BSON is mandatory for communication with the shell only.

Question 3

In a three-node replica set with default write concerns, what occurs when the primary node experiences a network partition and cannot communicate with the majority of the set?

Accepted Answer

The primary steps down to secondary status, and the set elects a new primary.. When a primary loses connectivity to the majority of the replica set, it steps down to secondary status to prevent split-brain scenarios. This process ensures data consistency by requiring a majority of nodes to acknowledge writes. The remaining nodes will initiate an election to choose a new primary, maintaining the availability and integrity of the cluster during the temporary partition event.

Answer

The primary continues accepting writes until the partition is resolved.

Answer

The primary immediately crashes and shuts down the mongod process.

Answer

The secondary nodes force a rollback on the primary node.

Question 4

An administrator notices that the MongoDB balancer is actively migrating chunks during peak business hours, causing noticeable application latency spikes. What is the standard administrative approach to mitigate this performance impact?

Accepted Answer

Configure a balancer window by updating the settings collection in the config database to restrict migrations to specific off-peak hours.. Configuring a balancer window restricts chunk migrations to off-peak hours, preventing background balancing traffic from contending with production application workloads. Mastering balancer scheduling controls allows DBAs to maintain cluster health and optimal data distribution without disrupting user experience during critical business hours.

Answer

Permanently terminate the mongos process responsible for orchestrating chunk migrations across the cluster nodes.

Answer

Execute the dropDatabase command on every shard to purge unbalanced chunks instantly and reset the cluster.

Answer

Disable journaling across all shard replica set members to accelerate background data migration speeds.

Question 5

Which THREE of the following are core tenets of the MongoDB philosophy regarding data modeling?

Accepted Answer

Store data that is accessed together in the same document.. MongoDB's data modeling philosophy emphasizes placing data that is accessed together into the same document (embedding). It promotes flexibility by allowing schemas to be dynamic rather than rigid. Furthermore, it encourages developers to design schemas based on the application's specific query patterns, ensuring that the database layout directly supports the most frequent operations, which leads to optimal performance in high-scale environments where relational joins would otherwise create bottlenecks.

Answer

Normalize data to the third normal form.

Answer

Always prioritize write consistency over read performance.

Question 6

Why does MongoDB use a 'document' as its fundamental unit of data?

Accepted Answer

It maps naturally to application objects in code.. The document is the natural way to represent complex objects in code. By keeping related information together in one logical unit, MongoDB aligns the database structure with the application's object model. This eliminates the 'impedance mismatch' often found in relational databases, where developers spend significant time mapping objects to tables. The document model improves performance by allowing the database to retrieve all required data in a single disk read.

Answer

It forces the use of fixed-width records for performance.

Answer

It ensures that no data can ever be duplicated.

Answer

It prevents the database from using indexes on fields.

Question 7

A company is migrating from a monolithic SQL database to MongoDB. They want to maintain high availability. Which feature is most critical to their success?

Accepted Answer

Automatic failover via Replica Sets.. High availability in MongoDB is primarily achieved through Replica Sets. A replica set consists of multiple nodes that store the same data, providing redundancy and automatic failover. If the primary node becomes unavailable, the replica set automatically elects a new primary, ensuring the application remains accessible. This architecture is fundamental to MongoDB's design philosophy of providing a resilient system that can withstand infrastructure failures without impacting the client application's availability.

Answer

Horizontal sharding of the data.

Answer

The use of the Aggregation Framework.

Answer

Strict enforcement of ACID transactions.

Question 8

Refer to the exhibit. The MongoDB process has crashed due to a storage engine error. What is the most immediate administrative action required to restore service?

Accepted Answer

Expand the disk volume and restart the mongod process.. The error 'No space left on device' indicates that the disk partition hosting the 'dbPath' directory is completely full. This prevents WiredTiger from writing data, metadata, or logs, causing an immediate shutdown to prevent data corruption. Administrators must free up space on the disk or extend the partition before restarting the service, as the database cannot recover or accept new writes without sufficient storage capacity to manage its internal files.

Answer

Run 'db.repairDatabase()' via the shell to free up space.

Answer

Clear the 'journal' directory files to recover space.

Answer

Modify the 'storage.wiredTiger.engineConfig.cacheSizeGB' setting in the config file.

Question 9

An application is performing many updates to a document. Which strategy is most effective to avoid fragmentation in the data files?

Accepted Answer

Add padding to the documents to accommodate future growth.. Document growth is a primary cause of fragmentation in MongoDB collections. When a document grows and no longer fits in its current location on disk, it must be moved to a new location. By pre-allocating space or using an embedding strategy that keeps documents within a predictable size range, administrators can reduce the frequency of document moves, thereby minimizing disk fragmentation and maintaining long-term database performance.

Answer

Use the 'compact' command during peak traffic hours.

Answer

Disable the WiredTiger cache periodically.

Answer

Perform a collection scan after every update.

Question 10

When adding a new node to an existing replica set, what is the primary factor that determines how quickly the new member will be able to begin participating in elections?

Accepted Answer

The amount of data in the dataset and network bandwidth.. The speed at which a new replica set member becomes 'secondary' and ready to participate depends on the amount of data it must synchronize from an existing member. Initial sync involves cloning data and applying the oplog. Understanding this process is vital for capacity planning, as adding a large member can put significant I/O and network pressure on the current primary or secondaries, potentially impacting performance for existing application traffic during the synchronization process.

Answer

The memory limit set in the configuration file.

Answer

The number of users defined in the admin database.

Answer

The version of the MongoDB shell used.

Question 11

Which design principle explains why MongoDB uses a document-oriented model instead of a rigid tabular schema?

Accepted Answer

Aligning data storage with object-oriented application models.. MongoDB utilizes a document model to align data structures with how applications represent objects, promoting developer productivity and flexibility. By allowing nested structures, developers avoid complex joins required in relational systems, which significantly improves read performance for related data. This philosophy enables schemas to evolve organically as application requirements change, supporting agile development cycles where modifying a table's structure across millions of rows would otherwise impose significant operational overhead or downtime.

Answer

Normalization of data to reduce storage footprints.

Answer

Strict enforcement of data types via ACID compliance.

Answer

Ensuring all related data is stored in separate collections.

Question 12

During routine cluster maintenance, an administrator needs to remove an underperforming shard from a production MongoDB sharded cluster safely. What is the mandatory first step the administrator must execute?

Accepted Answer

Run the removeShard command on the admin database via a mongos connection to initiate the automated chunk draining process.. Removing a shard safely begins with executing the removeShard command, which initiates the draining process. The cluster balancer automatically migrates all chunks residing on the target shard to other available shards in the cluster, ensuring no user data is lost before the node is decommissioned.

Answer

Execute the dropDatabase command on every secondary member of the shard replica set to clear local storage blocks instantly.

Answer

Manually shut down all mongod processes associated with the target shard before notifying the config server replica set.

Answer

Run the reshardCollection command to merge all orphaned documents into a single backup file on the primary config server.

Question 13

Which TWO of the following are essential for maintaining performance in a sharded cluster?

Accepted Answer

Selecting a shard key with high cardinality.. A well-chosen shard key is the most critical factor for even data distribution, while monitoring chunks ensures that data remains balanced across the cluster. If the shard key is poorly chosen, some shards may become bottlenecks (hotspots), while others remain underutilized. Proper chunk management prevents excessive migration and ensures that query routers (mongos) efficiently route requests to the appropriate shards, maintaining overall system stability and throughput.

Answer

Hardcoding the shard primary in the application connection string.

Answer

Disabling the balancer during all business hours.

Answer

Using the same shard key for every collection in the database.

Question 14

Which design principle should guide the decision between embedding and referencing?

Accepted Answer

Model data based on the application's read and write patterns.. The primary principle for data modeling in MongoDB is the 'access pattern.' You should model data to match how your application queries it. If data is almost always retrieved together, it should be embedded. If the data is accessed independently or is extremely large, it should be referenced. This ensures that the system remains performant by minimizing the number of disk reads and network round-trips required to serve requests.

Answer

Always embed to prevent any possibility of data duplication.

Answer

Always reference to keep the database size as small as possible.

Answer

Use embedding for all data to ensure ACID compliance.

Question 15

When designing an application, what is the best practice for handling connection pools?

Accepted Answer

Maintain a long-lived, singleton instance of the MongoClient.. Maintaining a single, long-lived connection pool instance in the application is the most efficient way to manage database connections. Repeatedly creating and destroying connections is extremely expensive, introducing unnecessary latency and resource overhead on both the application server and the database. Proper pool management is a core application administration task that ensures the database handles traffic gracefully without exhausting its maximum configured connection limit due to unnecessary connection churn from the client side.

Answer

Create a new connection for every query.

Answer

Close the connection after every single write operation.

Answer

Set the connection pool size to zero.

Question 16

An application frequently queries a large collection using two fields: 'category' (equality) and 'timestamp' (range). Which index strategy provides the most efficient execution plan?

Accepted Answer

{ category: 1, timestamp: 1 }. The ESR (Equality, Sort, Range) rule dictates that equality fields should come first in a compound index, followed by sort fields, and finally range fields. By placing 'category' first, MongoDB eliminates most irrelevant documents immediately. The 'timestamp' field follows, allowing the engine to leverage the index for range filtering. This minimizes memory usage and prevents costly full collection scans, which is critical for maintaining performance as data volume scales.

Answer

{ timestamp: 1, category: 1 }

Answer

{ category: 1 }

Answer

{ timestamp: 1 }

Question 17

An application issues a find query against a sharded collection without including the shard key in the query filter. How does the mongos query router handle this operation?

Accepted Answer

It performs a scatter-gather query by sending the request to all shards in the cluster, merging the results before returning them to the client.. When a query lacks the shard key, the mongos query router cannot determine which specific shard holds the target document. Consequently, it executes a scatter-gather query, forwarding the request to every shard in the cluster, collecting the responses, and merging them before returning the result to the client.

Answer

It rejects the query immediately with an invalid operation exception to protect cluster performance from unindexed scans.

Answer

It routes the query exclusively to the primary shard of the database, bypassing all other shards in the infrastructure.

Answer

It broadcasts the query only to the config server primary, which evaluates the predicate against cached metadata documents.

Question 18

Which capability of MongoDB's document model most significantly distinguishes it from key-value stores?

Accepted Answer

The ability to index and query nested document fields.. While key-value stores are limited to looking up data by a single key, MongoDB allows for deep inspection and querying of the document content. MongoDB indexes fields within the document, enables complex aggregation pipelines, and supports ad-hoc queries on any field. This versatility transforms the database from a simple lookup engine into a powerful analytical and transactional system, allowing it to handle diverse workloads that require rich data exploration and complex filtering.

Answer

The ability to store binary data as BSON.

Answer

The use of a primary key for document retrieval.

Answer

The support for horizontal scaling across clusters.

Question 19

Refer to the exhibit. An administrator attempts to execute the shardCollection command but receives the displayed error message. What is the root cause of this failure?

Accepted Answer

The collection lacks a supporting index whose key pattern matches or starts with the fields specified in the shard key definition.. MongoDB requires an explicit index whose prefix matches the designated shard key before sharding a collection. The error indicates that no such index exists on the collection, preventing the query router from establishing the necessary routing boundaries. Creating the correct index prior to running shardCollection resolves this issue.

Answer

The target database has not been enabled for sharding using the enableSharding administrative command.

Answer

The specified shard key contains an unsupported array field that violates BSON multi-key index constraints.

Answer

The config server replica set is currently undergoing an election and cannot process metadata write operations.

Question 20

A sharded cluster experiences poor query performance because a targeted query targeting a specific shard key still results in a scatter-gather operation across all shards. What is the root cause?

Accepted Answer

The query predicate completely omitted the shard key or its valid prefix fields.. To target a specific shard directly, a query must include the exact shard key or a valid prefix of the shard key in its filter predicate. Omitting the shard key forces the mongos router to query every shard in the cluster to assemble the final result set.

Answer

The chunk migration threshold was set too low, causing frequent balancing cycles across shards.

Answer

The collection was created as unhashed, preventing the mongos router from hashing query inputs.

Answer

The balancer process was paused, leaving uneven document distribution across cluster shards.