- A MongoDB could not do collation-based sorting
- B Locks were implemented on a per-server process basis
- C MongoDB could return stale reads
- D Queries against an index were not atomic
- Share this MCQ
Answer:
C
Share this MCQ
Answer: MongoDB could return stale reads
Explanation: In some failure scenarios where an application can access two distinct MongoDB processes, but these processes cannot access each other, it is possible for MongoDB to return stale reads. This issue was addressed since version 3.4.0 released in November 2016 (and back-ported to v3.2.12).
Share this MCQ