C100DBA · Question #94
The MongoDB explain() method does not support which of the following verbosity mode:
The correct answer is A. executionStats. There appears to be an error in this question. The stated correct answer (A: executionStats) is actually incorrect - executionStats is a valid and widely-used MongoDB explain() verbosity mode. MongoDB's explain() method supports exactly three verbosity modes: queryPlanner…
Question
The MongoDB explain() method does not support which of the following verbosity mode:
Options
- AexecutionStats
- BqueryPlanner
- CcustomExecutionStats
- DallPlansExecution
How the community answered
(42 responses)- A86% (36)
- B5% (2)
- C7% (3)
- D2% (1)
Explanation
There appears to be an error in this question. The stated correct answer (A: executionStats) is actually incorrect - executionStats is a valid and widely-used MongoDB explain() verbosity mode.
MongoDB's explain() method supports exactly three verbosity modes:
queryPlanner(default) - shows the query plan selected by the optimizerexecutionStats- shows execution stats for the winning planallPlansExecution- shows stats for all candidate plans
The mode that does not exist is C: customExecutionStats - MongoDB provides no such mode.
The correct answer should be C, not A.
Corrected explanation:
customExecutionStats (C) is the unsupported mode because MongoDB only recognizes three fixed verbosity levels and offers no mechanism for custom variants. queryPlanner (B) is the default mode used when no verbosity is specified. executionStats (A) is fully supported and shows runtime metrics like documents examined and execution time. allPlansExecution (D) is supported and extends executionStats by including stats from rejected candidate plans.
Memory tip: Think "Q-E-A" - QueryPlanner, ExecutionStats, AllPlansExecution. Any name outside these three is fabricated.
You may want to flag this question to whoever provided the exam material, as the answer key appears to have a typo - likely C and A were swapped.
Topics
Community Discussion
No community discussion yet for this question.