MongoDB MongoDB Transactions and ACID Compliance

Question 1

In which MongoDB version were multi-document ACID transactions introduced for replica sets?

Accepted Answer

MongoDB 4.0

Answer

MongoDB 3.6

Answer

MongoDB 4.2

Answer

MongoDB 5.0

Question 2

What does ACID stand for in the context of database transactions?

Accepted Answer

Atomic, Consistent, Isolated, Durable

Answer

Automated, Concurrent, Indexed, Distributed

Answer

Associative, Consistent, Incremental, Distributed

Answer

Atomic, Cached, Isolated, Dynamic

Question 3

How do you start a multi-document transaction in MongoDB using the Node.js driver?

Accepted Answer

session.startTransaction()

Answer

db.beginTransaction()

Answer

client.openTransaction()

Answer

db.collection.lockWrite()

Question 4

What happens to a MongoDB transaction if commitTransaction() is not called before the session times out?

Accepted Answer

The transaction is rolled back and all changes are discarded

Answer

The transaction is committed automatically

Answer

The transaction is saved as a pending transaction

Answer

An error is thrown and the application must retry

Question 5

Which read concern is required to read the latest majority-committed data within a MongoDB transaction?

Accepted Answer

snapshot

Answer

local

Answer

available

Answer

majority

Question 6

What is the recommended write concern for MongoDB transactions to ensure durability?

Accepted Answer

{ w: 'majority' }

Answer

{ w: 0 }

Answer

{ w: 1 }

Answer

{ w: 'all' }