Firestore queries and indexes in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to query Firestore for documents where the field 'status' equals 'active'.

GCP

query = firestore_client.collection('users').where('status', '==', [1])

Drag options to blanks, or click blank then click option'

A'inactive'

B'active'

C'pending'

D'deleted'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around string values

Using wrong comparison operator

The query filters documents where the 'status' field is exactly 'active'.

2fill in blank

medium

Complete the code to order Firestore query results by the 'createdAt' timestamp in descending order.

GCP

query = firestore_client.collection('orders').order_by('createdAt', [1])

Drag options to blanks, or click blank then click option'

Adesc

Basc

Cascending

Ddescending

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ascending' or 'descending' instead of 'asc' or 'desc'

Reversing order direction

Use 'desc' to order results from newest to oldest.

3fill in blank

hard

Fix the error in the Firestore query to filter documents where 'age' is greater than 18.

GCP

query = firestore_client.collection('users').where('age', [1], 18)

Drag options to blanks, or click blank then click option'

A>

B<=

C==

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '>'

Using '<=' which filters wrong range

The '>' operator filters documents where 'age' is greater than 18.

4fill in blank

hard

Fill both blanks to create a Firestore composite index query filtering 'category' equals 'books' and ordering by 'price' ascending.

GCP

query = firestore_client.collection('products').where('category', '==', [1]).order_by('price', [2])

Drag options to blanks, or click blank then click option'

A'books'

B'electronics'

Casc

Ddesc

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong category value

Ordering price descending instead of ascending

The query filters products in 'books' category and orders them by price from low to high.

5fill in blank

hard

Fill all three blanks to create a Firestore query that filters documents where 'status' is 'active', 'priority' is greater than 3, and orders by 'dueDate' descending.

GCP

query = firestore_client.collection('tasks').where('status', '==', [1]).where('priority', [2], 3).order_by('dueDate', [3])

Drag options to blanks, or click blank then click option'

A'active'

B>

Cdesc

Dasc

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong operators

Ordering dueDate ascending instead of descending

This query finds tasks that are active, have priority above 3, and sorts them by due date from newest to oldest.

Practice

1. What is the main purpose of indexes in Firestore queries?

easy

A. To make queries faster and more efficient

B. To store large files like images

C. To backup data automatically

D. To encrypt data for security

Solution

1. Step 1: Understand what indexes do in Firestore

   Indexes help Firestore find data quickly without scanning all documents.

2. Step 2: Relate indexes to query performance

   By using indexes, queries run faster and use less resources.

3. Final Answer:

   To make queries faster and more efficient -> Option A

4. Quick Check:

   Indexes speed up queries = D [OK]

Hint: Indexes speed up data search in Firestore queries [OK]

Common Mistakes:

• Thinking indexes store files
• Confusing indexes with backups
• Assuming indexes encrypt data

2. Which of the following is the correct syntax to create a simple Firestore query filtering by a field age equal to 30?

easy

A. db.collection('users').filter('age', '=', 30)

B. db.collection('users').where('age', '==', 30)

C. db.collection('users').query('age' == 30)

D. db.collection('users').find('age', 30)

Solution

1. Step 1: Recall Firestore query syntax

   Firestore uses where(field, operator, value) to filter data.

2. Step 2: Match syntax with options

   db.collection('users').where('age', '==', 30) uses where('age', '==', 30), which is correct syntax.

3. Final Answer:

   db.collection('users').where('age', '==', 30) -> Option B

4. Quick Check:

   Correct Firestore filter syntax = B [OK]

Hint: Use .where(field, '==', value) for filtering in Firestore [OK]

Common Mistakes:

• Using .filter instead of .where
• Using == inside query string
• Using .find which is not Firestore syntax

3. Given this Firestore query:

db.collection('orders').where('status', '==', 'shipped').orderBy('date', 'desc')

What must you do to avoid an error when running this query?

medium

A. Remove the orderBy clause

B. Create a single-field index on date only

C. No index needed, Firestore handles it automatically

D. Create a composite index on status and date

Solution

1. Step 1: Understand query with multiple filters and sorting

   This query filters by status and sorts by date.

2. Step 2: Know Firestore index requirements

   Firestore requires a composite index for queries with multiple filters or sorting on different fields.

3. Final Answer:

   Create a composite index on status and date -> Option D

4. Quick Check:

   Composite index needed for multiple filters + orderBy = A [OK]

Hint: Use composite indexes for queries with filters and sorting [OK]

Common Mistakes:

• Assuming single-field index is enough
• Thinking Firestore auto-creates all indexes
• Removing orderBy to fix error

4. You wrote this Firestore query:

db.collection('products').where('price', '>', 100).orderBy('name')

But it gives an error about missing index. What is the best fix?

medium

A. Change price filter to ==

B. Remove the orderBy clause

C. Create a composite index on price (ascending) and name (ascending)

D. Create a single-field index on name only

Solution

1. Step 1: Identify query components causing index error

   The query filters by price > 100 and orders by name.

2. Step 2: Understand Firestore index needs for range filter + orderBy

   Firestore requires a composite index on both fields with correct sort order.

3. Final Answer:

   Create a composite index on price (ascending) and name (ascending) -> Option C

4. Quick Check:

   Composite index needed for range filter + orderBy = C [OK]

Hint: Create composite index matching filter and orderBy fields [OK]

Common Mistakes:

• Removing orderBy instead of indexing
• Changing filter operator incorrectly
• Creating only single-field index

5. You want to query a Firestore collection events to find documents where type is 'conference' and attendees is greater than 100, sorted by date ascending. Which index should you create to support this query?

hard

A. Composite index on type (ascending), attendees (ascending), and date (ascending)

B. Single-field index on date only

C. Composite index on type (descending) and date (ascending)

D. No index needed, Firestore supports this query by default

Solution

1. Step 1: Analyze query filters and sorting

   The query filters by type == 'conference' and attendees > 100, and sorts by date ascending.

2. Step 2: Determine required index type

   Multiple filters plus sorting require a composite index including all these fields with correct order.

3. Final Answer:

   Composite index on type (ascending), attendees (ascending), and date (ascending) -> Option A

4. Quick Check:

   Composite index covers all filters and orderBy fields = A [OK]

Hint: Include all filter and orderBy fields in composite index [OK]

Common Mistakes:

• Creating only single-field index
• Using wrong sort order in index
• Assuming no index needed