Free MongoDB C100DBA Practice Exam with Questions & Answers | Set: 5

MongoDB supports direct equality matching against elements contained in an array. When the predicate is { sizes: " M " } and sizes is an array field, a document matches when at least one element of the array equals the scalar value " M " . Document 1 contains only " XS " and " S " , so it does not match. Document 2 contains " M " in [ ' S ' , ' M ' , ' XL ' ], and document 3 contains " M " in [ ' M ' , ' L ' , ' XL ' , ' XXL ' ]; both therefore match. No $elemMatch expression is required for this simple scalar membership test. $elemMatch becomes important when multiple conditions must be satisfied by the same array element, particularly for arrays of embedded documents or compound conditions. This array equality behavior is a core part of MongoDB ' s document query model and allows concise filtering of array-valued fields. The correct result is consequently the t-shirt and vest documents, which corresponds to option D. This same matching behavior applies consistently whenever a scalar predicate targets values stored inside a BSON array field.

Study Guide reference/topic:MongoDB Architecture and Core Operations - querying array fields and equality predicates.

===========

The proposed index is a compound index across home_score and away_score. MongoDB supports compound multikey indexes, but it imposes an important restriction: for any one indexed document, no more than one field covered by the compound index may contain an array. Document 1 is valid because only away_score is an array. Document 2 is also valid because only home_score is an array. Document 4 contains scalar values for both fields. Document 3 contains arrays in both indexed fields: home_score: [5,8] and away_score: [9,6] . Indexing that document would require a compound multikey index to expand two independent array dimensions, which MongoDB prohibits. Therefore document 3 prevents the compound index from being valid. The restriction is important because a single multikey field already creates multiple index keys per document; allowing multiple independently array-valued keys in the same compound index would create ambiguous and potentially combinatorial key combinations. DBAs designing indexes over document schemas with arrays must understand these multikey constraints before building compound indexes. The failing document is _id:3, making option D correct.

Study Guide reference/topic:Indexing and Query Optimization - multikey indexes, compound multikey restrictions, and array-valued fields.

===========