Collection group queries in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What documents does this collection group query return?

Consider a Firestore database with multiple subcollections named comments under different posts. Which documents will this query return?

const query = firestore.collectionGroup('comments').where('approved', '==', true);

Firebase

const query = firestore.collectionGroup('comments').where('approved', '==', true);

A All documents in the root collection where 'approved' is true.

B Only documents in the 'comments' subcollection of the root collection where 'approved' is true.

C All documents in any 'comments' subcollection where the 'approved' field is true.

D Documents in any collection named 'comments' but only if they are direct children of the root.

💡 Hint

Think about what collectionGroup does: it searches all subcollections with the given name, regardless of their parent.

The collectionGroup('comments') query searches all subcollections named 'comments' anywhere in the database. The where clause filters documents where 'approved' is true. So it returns all approved comments from all posts.

📝 Syntax

intermediate

Identify the syntax error in this collection group query

Which option contains the correct syntax for querying all documents in subcollections named reviews where the rating is greater than 4?

Firebase

firestore.collectionGroup('reviews').where('rating', '>', 4).get()

A firestore.collectionGroup('reviews').where('rating' > 4).get()

B firestore.collectionGroup('reviews').where('rating', '>', 4).get()

C firestore.collectionGroup('reviews').where('rating', '=>', 4).get()

D firestore.collectionGroup('reviews').where('rating', 'gt', 4).get()

💡 Hint

Check the syntax of the where method parameters carefully.

The where method requires three parameters: field name, comparison operator as a string, and value. Option B uses the correct syntax. Options A, C, and D have syntax errors or invalid operators.

❓ optimization

advanced

How to optimize a collection group query with multiple filters?

You want to query all orders subcollections for documents where status is 'shipped' and total is greater than 100. Which approach optimizes performance best?

A Use a collection group query with a single <code>where</code> filter on <code>status</code> and ignore the <code>total</code> filter.

B Run two separate collection group queries, one filtering by <code>status</code> and one by <code>total</code>, then merge results in code.

C Query the root collection and filter results in the client code after fetching all documents.

D Use a collection group query with two <code>where</code> filters: <code>.where('status', '==', 'shipped').where('total', '>', 100)</code> and create a composite index for these fields.

💡 Hint

Think about how Firestore uses indexes to speed up queries with multiple filters.

Firestore performs best when queries use indexed fields. Combining filters in one query with a composite index is efficient. Running multiple queries or filtering client-side is slower and uses more bandwidth.

🔧 Debug

advanced

Why does this collection group query fail with a missing index error?

This query fails with an error about a missing index:

firestore.collectionGroup('messages').where('sender', '==', 'alice').where('read', '==', false).get()

What is the cause?

A Firestore requires a composite index on 'sender' and 'read' fields for collection group queries with multiple filters.

B The collection group name 'messages' is invalid and causes the error.

C The query uses '==' operator twice which is not allowed in collection group queries.

D Firestore does not support filtering on boolean fields like 'read' in collection group queries.

💡 Hint

Check Firestore's indexing requirements for collection group queries with multiple filters.

When a collection group query uses multiple filters, Firestore requires a composite index on those fields. Without it, the query fails with a missing index error.

🧠 Conceptual

expert

What is a key limitation of collection group queries in Firestore?

Which of the following is a true limitation when using collection group queries?

A Collection group queries cannot include <code>orderBy</code> clauses on fields not included in the <code>where</code> filters without an index.

B You cannot perform collection group queries on collections with different field structures.

C Collection group queries only work on root-level collections, not subcollections.

D You can only query one collection group per Firestore database.

💡 Hint

Think about Firestore's indexing rules and how they affect ordering in queries.

Firestore requires that any orderBy field in a collection group query must be indexed and usually must be included in the where filters or have a composite index. This is a common limitation that requires creating indexes.