MENU
Consider the following example document:
{
"_id": Objectld("5360c0a0a655a60674680bbe"),
"user"
"login": "irOn"
"description": "Made of steel"
"date": ISODate("2014-04-30T09:16:45.836Z"),
}
>
and index creation command:
db.users.createlndex( { "user.login": 1, "user.date": -1 }, "mylndex" )
When performing the following query:
db.users.find( { "user.login": /Air.*/ },
{ "user":1, "_id":0 > ).sort( { "user.date":1 > )
which of the following statements correctly describe how MongoDB will handle the query? Check all that apply.
Suggested Answer: B
Get Premium C100DBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
18 comments · newest first
BA
Barb
10 months ago
D is definitely wrong, at least B and A are valid.
CH
Charlena
11 months ago
Wait, how can it be a covered query if '_id' is excluded?
GE
Gerald
11 months ago
C seems off, I don't think it needs a full scan.
DO
Donette
11 months ago
Totally agree with B, the login field is indexed!
LE
Lettie
11 months ago
A is correct, it uses the index for sorting.
LA
Lazaro
12 months ago
I'm leaning towards option E since it mentions a covered query, but I can't recall if filtering out '_id' really makes it covered in this scenario.
AD
Adell
12 months ago
I feel like I saw a similar question where MongoDB had to do a collection scan when the query didn't match the index properly. So maybe option C could be true?
NO
Nobuko
12 months ago
I think option B sounds right because 'user.login' is indexed, but I'm not completely confident about how the regex affects that.
JI
Jina
1 year ago
I remember that for a query to be optimized, it needs to use an index on both the filter and sort fields, but I'm not sure if that's the case here.
AL
Alaine
1 year ago
This seems like a classic case of using an index to efficiently execute a query. The combination of the indexed fields and the sorting should allow MongoDB to use the index to retrieve the results in the correct order.
BU
Buck
1 year ago
I'm a bit confused about the "scanAndOrder = false" part. Does that mean the sort will be done in memory without a full table scan? I'll need to review my MongoDB query optimization knowledge for this one.
BO
Boris
1 year ago
Okay, let me think this through step-by-step. The query is filtering on "user.login" which is indexed, so that's good. And it's sorting on "user.date" which is also indexed, so that should allow an optimized sort.
LI
Lili
1 year ago
Hmm, the index includes both "user.login" and "user.date", so I'm thinking it might use that index for the query. But I'm not sure if it will be a full index scan or an optimized sort.
JO
Jose
1 year ago
This looks like a tricky MongoDB query question. I'll need to carefully analyze the index and query details to determine the most likely execution plan.
TI
Tijuana
1 year ago
This is a good question to test our understanding of digitization in manufacturing. I think the key is to focus on the core outcomes, rather than peripheral benefits. I'll review the options and choose the one that seems most fundamental.
AL
Alisha
1 year ago
Based on my understanding, the correct answer is B. The evidence report is designed to provide a comprehensive view of all the evidence items in a case.
MA
Madalyn
1 year ago
This seems like a straightforward question. The developer needs a full GPU dedicated to the machine-learning training, so I'd go with option C - Passthrough GPU.
JA
Jacinta
1 year ago
The instructions seem pretty detailed, but I want to make sure I understand the difference between the various data validation options. I'll take my time and double-check each step.