CHAP1: PREPARE DATABASE ENVIRONMENT

 Identifying Database  Indexing

requirements  Optimistic Locking
 key terms to discuss on  Relationships
 NoSQL  Data model
 MongoDB  Schema
 Availability  Mongosh
 Documents
 Collection
Lets start………..
 NoSQL stands for "Not Only SQL." It refers to a variety of
database technologies designed to store, retrieve, and
manage data that is not structured in traditional relational
databases.
o Instead of using tables with rows and columns (as in
relational databases), NoSQL databases can store data in
various formats like key-value pairs, documents, wide-
column stores, or graphs.
 MongoDB is a document database. It stores data in a type
of JSON format called BSON.
 or
 MongoDB is a popular NoSQL document database that
stores data in flexible, JSON-like documents.
o It allows for a flexible schema design, making it easy to
accommodate changing requirements and store
unstructured or semi-structured data.
o MongoDB is known for its horizontal scalability, making it
suitable for large-scale applications with growing data.
 JSON stands for JavaScript Object Notation
Example of json format

 {
"employees":[
{"firstName":"John", "lastName":"Doe"},
{"firstName":"Anna", "lastName":"Smith"},
{"firstName":"Peter", "lastName":"Jones"}
]
}
 Availability
o In the context of databases, availability refers to the
system's ability to remain operational and accessible, even
during failures or high demand.
o In NoSQL databases, availability is often prioritized over
consistency in distributed systems
o MongoDB uses replication and sharding to ensure high
availability.
o Replication involves copying data from one database
server to multiple servers. This ensures that the system can
continue to operate even if one server fails.
 In MongoDB, replication is achieved through replica sets,
where one server (primary) accepts write operations, and
multiple secondary servers maintain copies of the data.
 If the primary server fails, one of the secondaries can
automatically take over as the new primary, ensuring no
downtime.
 Sharding is a horizontal scaling method that divides large
datasets across multiple servers, or shards.
o Each shard contains a portion of the data, allowing the
system to handle massive amounts of data and traffic by
distributing the load.
o Sharding is particularly useful when a single server can no
longer store or process all the data due to resource
limitations (e.g., CPU, memory, storage).
 Example: In MongoDB, a collection can be divided
(sharded) across multiple servers based on a shard key (a
field in the document).
 For instance, a large e-commerce dataset could be sharded
across three servers based on a customerID , field, where
each shard holds a subset of customers.
 [ Shard1 ] [ Shard2 ] [ Shard 3 ]
 customerID 1-100K customerID 100K-200K customerID 200K-300K
 Documents
o In MongoDB, a document is the basic unit of data, similar
to a row in a relational database.
o Documents are represented in a JSON-like format (BSON in
MongoDB, a binary version of JSON).
 What is BSON?
 BSON stands for Binary JSON. It is a binary-encoded
serialization format used to store and transport data.
MongoDB, a NoSQL database, uses BSON to store
documents on disk and transfer data over the network.
o Each document can store key-value pairs, and the structure
of each document can vary within the same collection.
 Example:
 {
 "_id": "123",
 "name": "Alice",
 "age": 25,
 "address": {
 "street": "123 Main St",
 "city": "New York"
 }
 }
 Collection
o A collection is the equivalent of a table in a relational
database system.
o It is a group of documents. Unlike a table, there is no
enforced schema, so documents in a collection can have
different structures.
o Collections organize documents into logical groups for
querying and managing.
 Example: A collection called users might store documents
representing individual user data.
 Indexing
o Indexing in MongoDB helps to improve query
performance.
o It allows the database to quickly locate documents in a
collection by creating special data structures (indexes) that
store a small portion of the document's data in an efficient
way.
o Without indexes, MongoDB must scan every document in
a collection, leading to slow query performance.
 Example: An index on the name field in the users collection
will speed up queries searching for users by name.
 Optimistic Locking
o Optimistic locking is a concurrency control mechanism
where a system assumes that multiple transactions can
complete without affecting each other.
o In MongoDB, optimistic locking can be implemented using
a field such as a version number (v field) that is
incremented with every document update.
o If two updates attempt to modify the same document at the
same time, one will fail, ensuring that no conflicting
changes are applied.
o Use Case: Optimistic locking is useful in distributed
systems where locking mechanisms should be avoided to
maintain high performance and availability.
 Relationships
o In NoSQL databases like MongoDB, relationships between
data are not as strictly enforced as in relational databases.
However, relationships can still be modeled.
o There are two types of relationships:
 Embedding: Storing related data in the same document.
 Referencing: Storing related data in separate
documents, using references (similar to foreign keys in
relational databases).
o Example: An order document may embed product details
directly, or it may reference products stored in a separate
collection.
 Data Model
o The data model defines how data is structured, stored, and
accessed in a database.
o In MongoDB, the data model is flexible and can adapt to
the application's needs. Unlike rigid schemas in SQL
databases, MongoDB’s data model allows for varied
document structures within a collection.
o Example: In MongoDB, one user document might have
fields like email, address and phone, while another user
document might have only an email and phone
 Schema
o A schema defines the structure of data.
o In traditional relational databases, schemas are strict,
defining the fields and data types for each table.
o In MongoDB, schema is flexible, meaning there is no
enforced structure by default, but schema validation can be
added if needed to impose constraints on the data.
o Example: MongoDB allows documents in the same
collection to have different fields, but you can enforce
schema validation rules using JSON Schema.
 Mongosh
o Mongosh is the MongoDB shell, a command-line interface
for interacting with MongoDB databases.
o It allows users to execute queries, manipulate data, and
perform administrative tasks directly from the terminal.
o Mongosh provides a JavaScript-based environment to work
with MongoDB.
o Usage: You can use Mongosh to connect to a MongoDB
instance, insert or query documents, and perform database
management tasks like creating indexes or viewing
collection statistics.
1.Characteristics of Collections in MongoDB
 Schema-Less Nature:
o Unlike traditional relational databases, MongoDB
collections don’t enforce a fixed schema. Each document
can have different fields and structures.
 Document Storage:
o Documents are stored inside collections. Each document
represents a piece of data.
 Explicit Creation:
o If a collection does not exist, MongoDB creates it
automatically when you first store data in that collection.
 Document Validation:
o By default, MongoDB collections do not enforce a strict
schema.
o However, you can set up document validation rules
during update and insert operations.
o Schema validation ensures that documents meet specific
criteria (e.g., required fields, data types) within a collection.
 Unique Identifiers:
o Each collection is assigned an immutable UUID
(Universally Unique Identifier).
o The collection UUID remains the same across all
members of a replica set and shards in a sharded cluster.
 Sharding and Replication:
o Collections can be sharded (distributed across multiple
servers) and replicated (duplicated across servers) to
ensure high availability and scalability.
2. Features of NoSQL Databases

 NoSQL databases have distinct features that make them

suitable for certain use cases, particularly those involving
large-scale, unstructured, or semi-structured data:
 Flexible Data Structures:
o Unlike traditional relational databases, NoSQL
databases don’t enforce fixed tabular relationships.
o Instead, they allow flexible data structures. This
flexibility is essential for handling diverse data formats,
whether structured, semi-structured, or unstructured.
 Low Latency:
o NoSQL databases prioritize low-latency operations.
They excel at quickly retrieving and storing data,
making them suitable for real-time applications.
 Horizontal Scalability:
o NoSQL databases are designed for scalability. As
your data grows, you can easily distribute the
workload across multiple servers or nodes.
o This horizontal scaling ensures performance
remains consistent even under heavy loads.
 Large Number of Concurrent Users:
o NoSQL databases handle concurrent access efficiently.
Whether it’s thousands of users querying the database
simultaneously or a high-throughput workload, NoSQL
systems can cope effectively.
 Optimized for Large Data Volumes:
o NoSQL databases accommodate large datasets,
regardless of whether the data is structured (like JSON),
semi-structured, or completely unstructured.

 Distributed Architecture:
o NoSQL databases distribute data across nodes, allowing
them to handle massive amounts of information. This
architecture enhances fault tolerance and resilience.
 Varied Data Models:
o They support different data models, including key-value
pairs, documents, wide-columns, and graphs, catering to
various types of data and use cases.
 Types of NoSQL Databases
 NoSQL databases are categorized based on their data
models:
 Document Stores:
o Store data in document format, usually JSON or BSON.
Each document is a self-contained unit of data.
o Examples: MongoDB, CouchDB
o Use Cases: Content management systems, real-time
analytics, user profiles
 Key-Value Stores:
o Store data as a collection of key-value pairs. Keys are
unique identifiers for the data, and values can be strings,
numbers, or more complex data structures.
o Examples: Redis, Amazon DynamoDB
o Use Cases: Caching, session management, simple
lookup operations
 Column-Family Stores:
o Store data in columns rather than rows.
o Data is organized into column families, which group related columns.
o Examples: Apache Cassandra, HBase
o Use Cases: Big data analytics, time-series data, write-heavy
applications
 Graph Databases:
o Store data in graph structures,
o Efficient for navigating complex relationships.
o Represent data as nodes, edges, and properties.
o Useful for social networks, recommendation engines, and
fraud detection.
o Examples: Neo4j, ArangoDB
o Use Cases: Social networks, recommendation engines, fraud
detection
4. Data Types in NoSQL Databases

 Different NoSQL databases support various data types, but

common data types include:
 String: Text data.
 Integer/Float: Numeric data for whole numbers and
floating-point numbers.
 Boolean: True or false values.
 Date/Time: Timestamp or date values.
 Binary Data: Raw binary data (e.g., files, images).
 Array: A list of elements, which can be of any data type.
 Object/Document: Nested data structures, similar to JSON
objects.
 Set: A collection of unique elements (e.g., Redis sets).
 Geospatial Data: Data representing geographic locations
and shapes
common use cases for NoSQL databases:
 Big Data: NoSQL databases are well-suited for handling
large amounts of unstructured or semi-structured data.
 Real-time Web Applications: NoSQL databases provide
high performance and low latency, making them suitable
for real-time web applications.
 Mobile and IoT Applications: NoSQL databases are often
used in mobile and IoT applications due to their ability to
handle large amounts of data and scale horizontally.
 Content Management: NoSQL databases are used in
content management systems to store and manage large
amounts of unstructured data, such as images and videos.
 Analysing NoSQL Database
Analyzing NoSQL Database Requirements
 The requirements analysis process is a crucial step in
designing a NoSQL database that meets the needs of its
users. Here's an overview of the process:
o Describe Requirements Analysis Process
 The requirements analysis process involves a systematic
approach to identifying, capturing, and documenting the
requirements of a NoSQL database.
 The goal is to understand the needs of the stakeholders and
end-users, and to define a clear set of requirements that can
guide the design and development of the database.
Stakeholders: Who Are They?
 In the context of a NoSQL database project, stakeholders refer to
individuals or groups who have a vested interest in the project's success or
failure.
 They can be impacted by the project, or they can influence the project's
outcome.
 examples of stakeholders who may be involved in a NoSQL database
project:
 Internal Stakeholders:
 Project managers: Responsible for overseeing the project and ensuring it is
completed on time, within budget, and to the required quality standards.
 Developers: Responsible for designing, developing, and testing the NoSQL
database.
 Architects: Responsible for designing the overall architecture of the system
and ensuring that the NoSQL database fits into that architecture.
 Quality assurance (QA) team: Responsible for testing the NoSQL database
to ensure it meets the required quality standards.
 Business analysts: Responsible for understanding the business
requirements and ensuring that the NoSQL database meets those
requirements.
 External Stakeholders:
 End-users: The people who will be using the NoSQL database on
a daily basis, such as data analysts, data scientists, and business
users.
 Customers: If the NoSQL database is being developed for a
customer, they may have specific requirements and expectations
that need to be met.
 Partners: If the NoSQL database is being developed in
partnership with other organizations, they may have a vested
interest in the project's success.
 Other Stakeholders:
 Sponsors: The people or organizations providing funding for the
project.
 Vendors: If the project involves purchasing hardware, software,
or services from external vendors, they may be stakeholders.
 Industry experts: If the project involves emerging technologies
or innovative approaches, industry experts may be stakeholders
who can provide guidance and advice.
o requirements analysis process
 1. Identify Key Stakeholders and End-Users
 The first step is to identify the key stakeholders and end-
users who will be impacted by the NoSQL database. These
may include:
 Business stakeholders: Product owners, project managers,
and business leaders who will be using the database to
drive business decisions.
 Technical stakeholders: Developers, architects, and
engineers who will be designing and implementing the
database.
 End-users: The people who will be interacting with the
database on a daily basis, such as data analysts, data
scientists, and business users.
 2.Capture Requirements
 Once the stakeholders and end-users have been identified, the
next step is to capture their requirements. This can be done
through a variety of techniques, including:
 Interviews: One-on-one interviews with stakeholders and end-
users to gather information about their needs and expectations.
 Surveys: Online or paper-based surveys to gather information
from a larger group of stakeholders and end-users.
 Workshops: Collaborative workshops to gather requirements
and facilitate discussion among stakeholders and end-users.
 Documentation review: Review of existing documentation, such
as business requirements documents, technical specifications,
and user manuals.
 3.Categorize Requirements
 The captured requirements should be categorized into
different types, such as:
 Functional requirements: Describe the features and
functions of the NoSQL database, such as data storage,
retrieval, and querying.
 Non-functional requirements: Describe the performance,
security, and scalability requirements of the NoSQL
database.
 User interface requirements: Describe the user interface
and user experience requirements of the NoSQL database.
 4.Interpret and Record Requirements
 The captured and categorized requirements should be
interpreted and recorded in a clear and concise manner.
This can be done using a variety of tools and techniques,
such as:
 Requirements management tools: Tools like JIRA, Trello,
or Asana to manage and track requirements.
 Use cases: Written descriptions of how the NoSQL
database will be used by end-users.
 User stories: Brief descriptions of the features and
functions of the NoSQL database from the end-user's
perspective.
 5.Validate Requirements
 The final step is to validate the requirements to ensure that
they are complete, accurate. This can be done through a
variety of techniques, including:
 Reviews: Peer reviews of the requirements documentation
to ensure that it is complete and accurate.
 Prototyping: Building a prototype of the NoSQL database
to test and validate the requirements.
 Testing: Testing the NoSQL database against the
requirements to ensure that it meets the needs of the
stakeholders and end-users.
 Performing Data Analysis and Implementing
Data Validation for a NoSQL Database
 Performing Data Analysis
 Data analysis is a crucial step in designing a NoSQL
database that meets the needs of its users.
 The goal of data analysis is to understand the structure,
relationships, and patterns in the data, and to identify the
requirements for storing and processing that data.
 Here are some steps involved in performing data analysis
for a NoSQL database:
 Data Profiling
 Data type analysis: Identify the data types of each
attribute, such as strings, integers, dates, etc.
 Data distribution analysis: Analyze the distribution of
data values, such as the frequency of each value, the range
of values, etc.
 Data relationship analysis: Identify the relationships
between different attributes, such as one-to-one, one-to-
many, many-to-many, etc.
 Data Quality Analysis
 Data cleanliness analysis: Identify any errors,
inconsistencies, or missing values in the data.
 Data redundancy analysis: Identify any duplicate or
redundant data.
 Data integrity analysis: Identify any data that is
inconsistent or contradictory.
 Data Modeling
 Entity-relationship modeling: Identify the entities,
attributes, and relationships in the data.
 Document-oriented modeling: Identify the documents,
fields, and relationships in the data.
 Graph modeling: Identify the nodes, edges, and
relationships in the data.
 Graph modeling is a technique used to represent complex
relationships between data entities in a NoSQL database.
 In a graph, nodes represent individual data entities, such as
people, places, things, or concepts.
 Edges represent the relationships between nodes in the
graph.
 Edges can be directed (i.e., they have a direction from one
node to another) or undirected (i.e., they do not have a
direction).
 Implementing Data Validation
 Data validation is an essential step in ensuring the quality
and integrity of the data in a NoSQL database.
 The goal of data validation is to ensure that the data is
accurate, complete, and consistent.
o Here are some steps involved in implementing data
validation for a NoSQL database:
 Data Validation Rules
 Data type validation: Validate the data type of each
attribute, such as strings, integers, dates, etc.
 Data range validation: Validate the range of values for
each attribute, such as minimum and maximum values.
 Data format validation: Validate the format of each
attribute, such as date formats, phone number formats, etc.
 Data Validation Techniques
 Client-side validation: Validate data on the client-side
before sending it to the server.
 Server-side validation: Validate data on the server-side
before storing it in the database.
 Database-level validation: Validate data at the database
level using constraints, triggers, and stored procedures.
 Data Quality Checks
 Data normalization: Normalize the data to ensure
consistency and reduce redundancy.
 Data standardization: Standardize the data to ensure
consistency and accuracy.
 Data cleansing: Cleanse the data to remove errors,
inconsistencies, and missing values.
 By performing data analysis and implementing data
validation, you can ensure that the data in your NoSQL
database is accurate, complete, and consistent, and that it
meets the needs of its users.
 Preparing Database Environment and
Identifying MongoDB Scalability
 1.Preparing Database Environment
 Preparing a database environment involves setting up the
necessary infrastructure and tools to support the
development, testing, and deployment of a database-driven
application.
 Here are some steps involved in preparing a database
environment:
o 1.Hardware and Software Requirements
 Server hardware: Ensure that the server has sufficient
processing power, memory, and storage to handle the
expected workload.
 Database software: Install and configure the chosen
database management system, such as MongoDB.
 Operating system: Ensure that the operating system is
compatible with the database software and has the
necessary dependencies installed.
o 2.Database Configuration
 Database instance: Create a new database instance or
configure an existing one to meet the application's
requirements.
 Database schema: Design and implement the database
schema, including the structure of collections, documents,
and fields.
 Database security: Configure user authentication,
authorization, and access control to ensure data security.
o 3.Development and Testing Tools
 IDE or code editor: Set up an integrated development
environment (IDE) or code editor to write, test, and debug
database-related code.
 Database client tools: Install and configure database client
tools, such as MongoDB Compass or MongoDB Shell, to
interact with the database.
 Identifying MongoDB Scalability
 MongoDB is a scalable NoSQL database that can handle
large amounts of data and high traffic.
 Here are some factors that contribute to MongoDB's
scalability:
 1.Horizontal Scaling
 Sharding: MongoDB allows you to split data across
multiple servers, known as shards, to distribute the load
and improve performance.
 Replication: MongoDB supports replication, which allows
you to create multiple copies of data across different
servers to ensure high availability and fault tolerance.
 2.Vertical Scaling
 Increasing resources: MongoDB can take advantage of
increased resources, such as CPU, memory, and storage,
to improve performance.
 Optimization: MongoDB provides various optimization
techniques, such as indexing and caching, to improve
query performance.
 Scalability Features
 Auto-sharding: MongoDB can automatically split data
across multiple shards as the dataset grows.
 Load balancing: MongoDB supports load balancing, which
distributes incoming traffic across multiple servers to
improve performance and availability.
 GridFS: MongoDB's GridFS allows you to store large files
and scale horizontally to handle high traffic.
 Scalability Considerations
 Data growth: Plan for data growth and ensure that the
database can handle increasing amounts of data.
 Traffic patterns: Analyze traffic patterns and ensure that
the database can handle peak traffic and sudden spikes.
 Resource utilization: Monitor resource utilization and
ensure that the database is optimized for performance and
efficiency.
 Setting up MongoDB Environment: Shell,
Compass, and Atlas

 Setting up a MongoDB environment involves installing and

configuring the necessary tools and services to interact with
a MongoDB database. Here's a breakdown of the three
environments mentioned:
o MongoDB Shell: The MongoDB Shell, also known as the
“mongo” shell, is a command-line interface for interacting
with a MongoDB database.
o Installation: To set up a shell environment, you need to install MongoDB on
your local machine or remote server. You can download the MongoDB
Community Server from the official MongoDB website.
o Basic Commands: Once installed, you can access the MongoDB Shell by
running the “mongo” command in your terminal or command prompt.
 Basic commands include:
o show dbs:Lists all databases in the MongoDB instance.
o use <database_name>:Switches to a specific database.
o show collections:Lists all collections in the current database.
o db.collection.find():Retrieves data from a collection.
 Compass Environment
o MongoDB Compass: MongoDB Compass is a graphical
user interface (GUI) for MongoDB that provides a visual
representation of your database and allows you to interact
with it.
o Installation: To set up a Compass environment, you need
to download and install MongoDB Compass from the
official MongoDB website.
 Features: Compass provides features such as:
o Visualizing database structure and data
o Creating and editing documents
o Running queries and aggregations
o Index management
o Data validation and quality checks
 Atlas Environment
o MongoDB Atlas: MongoDB Atlas is a cloud-based
MongoDB service that provides a fully managed database-
as-a-service (DBaaS) solution.
o Setup: To set up an Atlas environment, you need to create
a MongoDB Atlas account and provision a new cluster.
 Features: Atlas provides features such as:
o Automated provisioning and patching
o Scalability and high availability
o Security and access control
o Performance monitoring and optimization
o Integration with other MongoDB tools and services
 Additional Tips
o Version Compatibility: Ensure that your MongoDB
version is compatible with the Shell, Compass, and Atlas
environments you are using.
o Authentication and Authorization: Configure
authentication and authorization mechanisms to secure
access to your MongoDB database.
o Data Modeling: Design a data model that aligns with your
application's requirements and takes advantage of
MongoDB's flexible schema.
QUESTIONS
Q1.What is the primary advantage of using a NoSQL database
like MongoDB?
ANS:The primary advantage of using a NoSQL database like
MongoDB is its ability to handle large amounts of
unstructured or semi-structured data with flexible schema
designs.
Q2.How do you create a new database in MongoDB using the
MongoDB Shell?
ANS: You can create a new database in MongoDB using the
MongoDB Shell by running the command use mydatabase
Q3.What is the purpose of indexing in MongoDB?
Ans:The purpose of indexing in MongoDB is to improve query
performance by allowing MongoDB to quickly locate specific data
without having to scan the entire collection.

Q4.How do you establish relationships between documents in

MongoDB?
ans: You can establish relationships between documents in
MongoDB using references or embedded documents.

Q5.What is the difference between a collection and a document in

MongoDB?
ans:A collection is a group of documents, while a document is a
single record or entry in a collection.
Q6.How do you ensure data consistency in a distributed MongoDB cluster?
Ans:You can ensure data consistency in a distributed MongoDB cluster by using
replication and distributed transactions.

Q7What is optimistic locking, and how is it used in MongoDB?

Ans:Optimistic locking is a concurrency control mechanism that assumes multiple
transactions can complete without conflicts, and only checks for conflicts when a
transaction is about to commit.

Q8.What is the role of the mongod process in a MongoDB environment?

Ans:You can scale a MongoDB cluster horizontally by adding more nodes to the
cluster.
Q10.What is the difference between MongoDB Compass and MongoDB Atlas?
Ans:MongoDB Compass is a GUI for MongoDB, while MongoDB Atlas is a cloud-
based MongoDB service.

Q11.How do you create a new user in MongoDB using the MongoDB Shell?
Ans:You can create a new user in MongoDB using the MongoDB Shell by running
the command db.createUser({ user: "myuser", pwd: "mypassword", roles:
["readWrite"] })
Q12. What is the purpose of the mongo shell in MongoDB?
Ans:The mongo shell is a command-line interface for interacting with MongoDB
instances.
Q13.How do you perform data modeling in MongoDB?
Ans:You can perform data modeling in MongoDB by defining a data model that
represents the structure and relationships of the data.

Q14.What is the difference between a NoSQL database and a relational database?

Q15.How do you handle data migration in MongoDB?
Q16.What is the purpose of data normalization in MongoDB?
Q17.How do you optimize query performance in MongoDB?
Q18.What is the role of replication in a MongoDB cluster?
Q19.How do you monitor and troubleshoot a MongoDB cluster?
Q1.What is the primary data model used in MongoDB?
a) Relational b) Document-based c) Key-value d) Graph-based
Answer: b) Document-based
Q2.Which of the following is a characteristic of a NoSQL database?
a) Fixed schema
b) Dynamic schema
c) Support for transactions
d) Support for joins
Answer: b) Dynamic schema
Q3.What is the purpose of indexing in MongoDB?
a) To improve data security
b) To improve query performance
c) To reduce data storage
d) To increase data redundancy
Answer: b) To improve query performance
Q4.How do you establish relationships between documents in MongoDB?
a) Using foreign keys
b) Using references
c) Using embedded documents
d) Using joins
Answer: b) Using references
Q5.How do you secure a MongoDB instance with authentication and
authorization?
a) Using SSL/TLS encryption
b) Using access control lists (ACLs)
c) Using username and password authentication
d) Using a firewall
 Answer: b) Using access control lists (ACLs)
Q6.What is the difference between a collection and a document in MongoDB?
a) A collection is a group of documents, while a document is a single record
b) A collection is a single record, while a document is a group of records
c) A collection is a database, while a document is a collection
d) A collection is a schema, while a document is a collection
 Answer: a) A collection is a group of documents, while a document is a single
record
Q7.How do you ensure data consistency in a distributed MongoDB cluster?
a) Using transactions
b) Using replication
c) Using sharding
d) Using optimistic locking
 Answer: b) Using replication
Q8.What is optimistic locking, and how is it used in MongoDB?
a) It's a concurrency control mechanism that assumes multiple transactions can
complete without conflicts
b) It's a concurrency control mechanism that assumes multiple transactions will
always conflict
c) It's a data modeling technique used in MongoDB
d) It's a security feature used in MongoDB
 Answer: a) It's a concurrency control mechanism that assumes multiple
transactions can complete without conflicts
Q9.How do you scale a MongoDB cluster horizontally?
a) By adding more nodes to the cluster
b) By increasing the RAM on each node
c) By increasing the disk space on each node
d) By using a load balancer
 Answer: a) By adding more nodes to the cluster
Q10.What is the role of the mongod process in a MongoDB environment?
a) It's the MongoDB Shell
b) It's the MongoDB daemon that manages the MongoDB instance
c) It's a MongoDB driver
d) It's a MongoDB tool
 Answer: b) It's the MongoDB daemon that manages the MongoDB instance
L.o. 2: DESIGN NOSQL DATABASE