Data aggregation patterns in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get a reference to the Firestore collection named 'orders'.

Firebase

const ordersRef = firestore.[1]('orders');

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

Acollection

Bdoc

Cget

Dset

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'doc' instead of 'collection' to get a collection reference.

Using 'get' or 'set' which are for reading or writing data, not referencing.

Use collection to get a reference to a Firestore collection.

2fill in blank

medium

Complete the code to increment the 'totalSales' field atomically in a Firestore document.

Firebase

docRef.update({ totalSales: firebase.firestore.FieldValue.[1](1) });

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

Aincrement

Bdelete

CarrayUnion

DserverTimestamp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' which removes a field.

Using 'serverTimestamp' which sets the time, not increments.

The increment method atomically increases a numeric field.

3fill in blank

hard

Fix the error in the code to correctly aggregate the sum of 'amount' fields from multiple documents.

Firebase

let total = 0;
docs.forEach(doc => {
  total [1] doc.data().amount;
});

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

A=

B*=

C-=

D+=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' which resets total instead of adding.

Using '-=' or '*=' which change the value incorrectly.

Use += to add each amount to the total sum.

4fill in blank

hard

Fill both blanks to create a Firestore query that gets documents where 'status' is 'completed' and orders by 'date' descending.

Firebase

const query = collectionRef.where('status', '==', [1]).[2]('date', 'desc');

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

A'completed'

B'pending'

CorderBy

Dlimit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pending' instead of 'completed' for the filter.

Using 'limit' instead of 'orderBy' for sorting.

Use 'completed' to filter status and orderBy to sort by date descending.

5fill in blank

hard

Fill all three blanks to create a map of user IDs to their total order amounts, filtering orders above 100.

Firebase

const userTotals = {};
orders.forEach(order => {
  if (order.amount [1] 100) {
    const userId = order.[2];
    userTotals[userId] = (userTotals[userId] || 0) [3] order.amount;
  }
});

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

A>

BuserId

C+=

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>' for filtering.

Accessing wrong property instead of 'userId'.

Using '=' instead of '+=' for accumulation.

Use > to filter amounts above 100, access userId property, and += to accumulate totals.

Practice

1. What is the main purpose of data aggregation in Firebase applications?

easy

A. To combine multiple data points into a single summary value

B. To store raw data without any processing

C. To delete old data automatically

D. To create multiple copies of the same data

Solution

1. Step 1: Understand data aggregation meaning

   Data aggregation means combining many pieces of data into one useful summary.

2. Step 2: Identify the purpose in Firebase

   In Firebase, aggregation helps by summarizing data to improve speed and reduce repeated calculations.

3. Final Answer:

   To combine multiple data points into a single summary value -> Option A

4. Quick Check:

   Aggregation = summary data [OK]

Hint: Aggregation means combining data into summaries [OK]

Common Mistakes:

• Thinking aggregation deletes data
• Confusing aggregation with data duplication
• Believing aggregation stores raw data only

2. Which Firebase feature helps safely update aggregated data to avoid conflicts?

easy

A. Transactions

B. Realtime Database rules

C. Cloud Functions triggers

D. Static hosting

Solution

1. Step 1: Identify safe update method

   When multiple users update data, conflicts can happen. Firebase transactions handle this safely.

2. Step 2: Match feature to safe updates

   Transactions ensure data is read, modified, and written atomically, preventing conflicts in aggregation.

3. Final Answer:

   Transactions -> Option A

4. Quick Check:

   Safe updates = Transactions [OK]

Hint: Use transactions to update data safely [OK]

Common Mistakes:

• Confusing rules with update safety
• Thinking Cloud Functions handle conflicts automatically
• Selecting unrelated features like static hosting

3. Given this Firebase Realtime Database structure:

{
  "likes": {
    "post1": 3,
    "post2": 5
  }
}

If a user likes post1 and the app uses a transaction to increment the count, what will be the new value of likes/post1?

medium

A. 3

B. Error

C. 5

D. 4

Solution

1. Step 1: Understand current value

   The current like count for post1 is 3.

2. Step 2: Apply transaction increment

   The transaction safely adds 1 to the current count, so 3 + 1 = 4.

3. Final Answer:

   4 -> Option D

4. Quick Check:

   3 + 1 = 4 [OK]

Hint: Increment count by 1 inside transaction [OK]

Common Mistakes:

• Assuming value stays the same
• Adding 2 instead of 1
• Expecting an error without reason

4. You wrote this transaction code to update a total count:

const totalRef = firebase.database().ref('totalCount');
totalRef.transaction(current => current + 1);

But sometimes the count becomes NaN. What is the likely cause?

medium

A. The database path is incorrect

B. The initial value of totalCount is null or undefined

C. Transactions cannot increment numbers

D. Firebase does not support transactions

Solution

1. Step 1: Analyze transaction function

   The function adds 1 to current value. If current is null or undefined, adding 1 results in NaN.

2. Step 2: Identify cause of NaN

   If totalCount is not set initially, current is null, so current + 1 = NaN.

3. Final Answer:

   The initial value of totalCount is null or undefined -> Option B

4. Quick Check:

   Null + 1 = NaN [OK]

Hint: Initialize count before incrementing [OK]

Common Mistakes:

• Believing transactions can't increment
• Assuming path error causes NaN
• Thinking Firebase lacks transaction support

5. You want to keep track of the total number of comments across all posts in Firebase. Which approach best uses data aggregation patterns to keep this count updated efficiently?

hard

A. Use Cloud Storage to save comment counts in a file

B. Query all comments each time and count them on the client

C. Store a totalComments value and update it inside a transaction whenever a comment is added or removed

D. Create a separate collection with one document per comment

Solution

1. Step 1: Evaluate counting methods

   Querying all comments each time is slow and inefficient for large data.

2. Step 2: Use aggregation with transactions

   Updating a totalComments value inside a transaction ensures safe, fast aggregation without repeated counting.

3. Step 3: Reject unrelated options

   Cloud Storage is not for real-time counts; separate collection per comment does not aggregate counts.

4. Final Answer:

   Store a totalComments value and update it inside a transaction whenever a comment is added or removed -> Option C

5. Quick Check:

   Aggregate with transaction = Store a totalComments value and update it inside a transaction whenever a comment is added or removed [OK]

Hint: Update total count inside transaction on each change [OK]

Common Mistakes:

• Counting all comments on client every time
• Using storage files for counts
• Not using transactions for safe updates