C100DBA Philosophy and Features Practice Test 3 — 15 Questions

Question 1

Which of these best describes MongoDB's approach to the CAP theorem?

Accepted Answer

It prioritizes consistency and partition tolerance (CP).. MongoDB is primarily a CP (Consistency and Partition Tolerance) system, though it allows flexible configuration. In the event of a network partition, the system prioritizes consistency by electing a new primary only if a majority can agree. By allowing clients to configure read/write concerns, MongoDB lets developers trade off between immediate consistency and availability, enabling them to tune the database to match the specific requirements of their application's workload and regional deployment.

Answer

It is an AP system that ignores consistency entirely.

Answer

It ignores the CAP theorem to improve performance.

Answer

It is a CA system that never allows partitions.

Question 2

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?

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 3

Which feature of MongoDB allows it to scale horizontally by distributing data across multiple physical servers?

Accepted Answer

Sharding to partition data across a cluster.. Sharding is the native MongoDB architecture for horizontal scaling, partitioning data into chunks across a cluster of shards. This strategy addresses storage limitations and throughput bottlenecks that single-node or replica set architectures cannot handle. By distributing read and write operations across multiple nodes, sharding maintains performance as datasets grow to terabyte or petabyte scales, fulfilling the philosophy of providing seamless, scalable infrastructure for global applications.

Answer

Vertical scaling via hardware upgrades.

Answer

Replica sets for high availability.

Answer

Index prefixing for faster query execution.

Question 4

A financial services team is designing a real-time fraud detection system. They need a database that can store alerts with flexible, evolving fields such as device fingerprint, geolocation, and transaction metadata, and that can scale horizontally across many nodes. Which MongoDB philosophy best supports this requirement?

Accepted Answer

A document-oriented model with dynamic schemas. MongoDB's document-oriented model with dynamic schemas lets each fraud alert carry different fields without migrations, while built-in sharding enables horizontal scale across nodes. Together, these features directly address the need for flexible, evolving data capture and distributed scalability in a real-time system.

Answer

Using a single-node in-memory cache with no persistence

Answer

A rigid normalized schema enforced by the database engine

Answer

Storing all alert data as large binary blobs outside the database

Question 5

A financial services firm is migrating its reporting application from a relational database to MongoDB. The lead architect argues that MongoDB's schema-less design will eliminate the need for data modeling. Which statement best describes MongoDB's philosophy regarding schema design?

Accepted Answer

Schema design is still essential but is driven by application access patterns rather than normalization rules.. MongoDB's schema flexibility does not eliminate the need for data modeling; instead, it shifts the focus to designing documents that align with how the application reads and writes data. Embedding and referencing are chosen based on access patterns, not normalization rules. This approach optimizes performance and scalability while still requiring careful planning to avoid pitfalls like unbounded document growth.

Answer

Schema design is optional because MongoDB automatically infers and enforces relationships between collections.

Answer

Schema design should follow third normal form to minimize data duplication and ensure consistency.

Answer

Schema design is unnecessary because MongoDB validates all documents against a collection schema by default.

Question 6

A logistics company is designing a MongoDB database for a real-time shipment tracking system. The operations team needs to frequently update shipment statuses and query the latest events. The development team is debating the trade-offs of embedding versus referencing for the shipment events. Which two considerations align with MongoDB's philosophy for this scenario? (Choose two.)

Accepted Answer

Embedding events within the shipment document ensures atomic updates and fast reads for the event history.. The correct considerations are that embedding provides atomic updates and fast reads for the event history, while referencing allows unlimited growth and avoids the 16 MB limit. These reflect MongoDB's flexible modeling philosophy: choose embedding when data is accessed together and atomicity is needed, but opt for referencing when data grows unbounded or is accessed independently. The decision hinges on access patterns and data lifecycle.

Answer

Embedding events is always preferred because it eliminates the need for multi-document transactions.

Answer

Referencing events requires using $lookup for every read, which is as fast as an embedded document read.

Answer

Embedding events ensures that the shipment document remains small and efficient for writes.

Question 7

A development team is building a real-time analytics dashboard that reads from a MongoDB replica set. The dashboard can tolerate slightly stale data but must never show data that could be rolled back. The team also wants to minimize read latency. Which read concern should they use?

Accepted Answer

read concern majority. Read concern majority guarantees that the data returned has been acknowledged by a majority of replica set members and is rollback-safe, while still allowing reads from secondaries to reduce latency. Since the dashboard tolerates slight staleness, this is the ideal balance between consistency and performance.

Answer

read concern linearizable

Answer

read concern snapshot

Answer

read concern local

Question 8

A healthcare provider is building a patient portal that must remain available even if a data center loses power. The operations team wants the database to continue accepting writes during a single-region outage. Which MongoDB philosophy directly enables this resilience?

Accepted Answer

Automatic failover through replica sets with majority write concern. Replica sets provide automatic failover by electing a new primary when the current one fails, and majority write concern ensures that acknowledged writes are durable across a majority of members. Together, they allow the portal to keep accepting writes during a single-region outage without manual intervention.

Answer

Relying on periodic logical backups to a cold standby server

Answer

Deploying a standalone mongod instance in each region with application-level conflict resolution

Answer

Storing all patient data on a single replicated node with manual failover

Question 9

A healthcare startup is evaluating MongoDB for a patient management system. The CTO asks how MongoDB ensures data durability and consistency across multiple servers without manual intervention. Which feature best describes MongoDB's built-in mechanism for automatic failover and data redundancy?

Accepted Answer

Replica sets. Replica sets are MongoDB's foundation for high availability, providing automatic failover and data redundancy across multiple nodes. When the primary becomes unavailable, the remaining nodes elect a new primary, allowing the system to continue operating. This built-in mechanism requires no manual intervention and is essential for production deployments that demand continuous uptime and data durability.

Answer

Write concern

Answer

Journaling

Answer

Sharding

Question 10

A media company stores articles with nested comments and tags. The development team wants to retrieve an article along with its comments in a single database round trip. Which MongoDB philosophy supports this design?

Accepted Answer

Embedding related data within a single document. Embedding related data such as comments and tags within the article document allows the application to retrieve everything in one query. This reduces round trips and latency, directly supporting the team's goal of a single database call to render an article page.

Answer

Using a relational foreign key constraint between articles and comments

Answer

Storing comments as a comma-separated string in a single field

Answer

Normalizing comments into a separate collection with manual joins

Question 11

A social media company is using MongoDB to store user posts and comments. The application needs to retrieve a post along with its most recent comments in a single query. Which data modeling approach best aligns with MongoDB's philosophy to optimize this access pattern?

Accepted Answer

Embed a subset of recent comments within the post document and store older comments separately.. The hybrid approach of embedding recent comments while storing older ones separately optimizes the common access pattern of fetching a post with its latest comments. It leverages MongoDB's flexible schema to keep frequently accessed data together, reducing query latency, while avoiding unbounded document growth. This reflects the core philosophy of modeling based on application access patterns rather than rigid normalization.

Answer

Store comments in a separate collection and use $lookup to join them when needed.

Answer

Store comments in a separate collection and use a manual application-level join to combine them with the post.

Answer

Embed all comments within the post document to ensure atomic updates and fast reads.

Question 12

A global IoT platform ingests sensor readings from millions of devices. The team must choose a database that can store semi-structured data, scale horizontally, and provide high write throughput. Which TWO MongoDB features directly support these requirements? (Choose two.)

Accepted Answer

Sharding with a well-chosen shard key. Sharding distributes data across shards for horizontal scale and high write throughput, while the dynamic schema accommodates heterogeneous sensor payloads without migrations. Together, these features address the platform's need to ingest semi-structured data from millions of devices and scale out as volume grows.

Answer

Mandatory multi-document ACID transactions for every insert

Answer

Strict table-level locking for all write operations

Answer

Automatic sharding based on the first field alphabetically

Question 13

A global e-commerce platform uses MongoDB with a replica set spanning three data centers. The company wants to ensure that a write is acknowledged by a majority of voting members before it is considered successful, even if one data center experiences a network partition. Which write concern should be configured to meet this requirement?

Accepted Answer

w: majority. w: majority ensures that a write is acknowledged by a majority of voting members in the replica set, providing strong durability guarantees even in the event of a network partition affecting one data center. This write concern is essential for applications that cannot tolerate data loss and need to maintain consistency across geographically distributed nodes.

Answer

w: 1

Answer

w: 2

Answer

w: 0

Question 14

A startup is building a mobile app backend. They want to iterate quickly on features without downtime for schema changes. Which MongoDB characteristic best supports this agile development approach?

Accepted Answer

The ability to store documents with varying fields without altering a centralized schema. MongoDB's document model lets developers add or modify fields per document without a centralized schema migration. This means new features can be deployed without database downtime, directly supporting the startup's need for rapid iteration and continuous delivery.

Answer

Schema validation rules that must be updated before any new field can be stored

Answer

Requiring all documents in a collection to have identical fields at all times

Answer

Using a fixed-width binary format that cannot represent new data types

Question 15

A healthcare analytics team stores patient records in MongoDB. Each record includes a nested array of vital sign readings, and the team frequently queries for patients whose latest blood pressure reading exceeds a threshold. They decide to store each reading as a separate document in a readings collection and reference the patient. Which MongoDB design philosophy does this decision contradict?

Accepted Answer

Data that is accessed together should be stored together.. The team's choice to reference readings instead of embedding them conflicts with the core MongoDB principle that related data accessed together should be stored together. Embedding the readings array within the patient document would allow a single query to retrieve the latest blood pressure without additional lookups, improving performance and simplifying application logic. This principle guides schema design for locality and efficiency.

Answer

Use server-side JavaScript for all data validation.

Answer

Store all data in a single collection to simplify sharding.

Answer

Normalize all data to the third normal form to eliminate redundancy.