Which of the following is a recommended practice when using transactions in MongoDB?
Including as many operations as possible within a single transaction to simplify code logic.
Keeping transactions short-lived and focused to minimize locking overhead and potential for conflicts.
Keeping transactions as long-running as possible to maximize the number of operations covered.
Avoiding the use of indexes within transactions as they can negatively impact performance.
Which of these practices helps protect against brute-force password attacks on MongoDB?
Using a firewall to restrict network access to the MongoDB server
Enabling access control and configuring strong password policies
Implementing rate limiting on database read operations
Regularly backing up database files
Which operator is used to create a text index in MongoDB?
$text
$createIndex
$index
$geo
Which sharding strategy distributes data based on ranges of the shard key values?
Ranged sharding
Hashed sharding
Random sharding
Zone sharding
What is the primary consideration for choosing between HDDs and SSDs for MongoDB storage?
Random Read/Write Performance
Storage Capacity
Data Redundancy
Cost per Gigabyte
What is the primary purpose of using transactions in MongoDB?
To enable data replication across multiple MongoDB clusters.
To create backups and restore data in case of failures.
To improve query performance for individual operations.
To ensure atomicity, consistency, isolation, and durability (ACID) properties for multiple operations.
What is the default storage engine for MongoDB versions 4.2 and later?
RocksDB
InMemory
WiredTiger
MMAPv1
What is the minimum number of nodes required to set up a MongoDB replica set?
1
3
7
2
During a read operation in MongoDB, if the requested data is not found in the WiredTiger cache, where is it retrieved from?
Data Files
Journal Files
Oplog
Config Servers
What is a crucial aspect to consider regarding performance when working with transactions in MongoDB?
Transactions always improve performance by grouping related operations.
Transactions are only recommended for read-only operations to maintain data consistency.
Transactions generally have no impact on performance and can be used liberally.
Transactions can introduce additional overhead, so it's essential to use them judiciously where ACID properties are strictly required.