Why advanced patterns solve scale problems in Firebase - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Firebase in your app.

Firebase

const app = initializeApp({ apiKey: [1] });

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

A"your-api-key"

Bapikey

Capi_key

DyourApiKey

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the API key

Using incorrect variable names

You must provide your actual API key as a string to initialize Firebase correctly.

2fill in blank

medium

Complete the code to get a Firestore collection reference.

Firebase

const colRef = collection(db, [1]);

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

Adatabase

B"users"

CuserCollection

DcollectionName

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of string literals

Missing quotes around collection name

The collection name must be a string representing the Firestore collection you want to access.

3fill in blank

hard

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

Firebase

const q = query(colRef, 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 equality operator instead of greater than

Using less than or not equal operators

The query should use the greater than operator > to filter ages above 18.

4fill in blank

hard

Fill both blanks to create a batched write that updates two documents.

Firebase

const batch = writeBatch(db);
batch.[1](doc(db, "users", "user1"), { active: false });
batch.[2](doc(db, "users", "user2"), { active: false });
await batch.commit();

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

Aupdate

Bset

Cdelete

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'set' which overwrites documents

Using 'delete' which removes documents

Use update to modify existing documents in a batch write.

5fill in blank

hard

Fill all three blanks to create a Firestore security rule that allows read only if user is authenticated and document owner.

Firebase

allow read: if request.auth != null && request.auth.uid == resource.data.[1] && resource.data.[2] == [3];

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

AownerId

BuserId

Crequest.auth.uid

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect field names

Comparing to 'true' instead of user ID

The rule checks that the authenticated user's ID matches the document's ownerId and userId fields.

Practice

1. Why do advanced Firebase patterns like sharding and caching help apps as they grow?

easy

A. They reduce the number of users who can access the app.

B. They make the app use more storage space.

C. They keep the app fast and stable under heavy use.

D. They slow down the app to save battery.

Solution

1. Step 1: Understand app growth challenges

   As apps get more users and data, they can slow down or crash without good design.

2. Step 2: Role of advanced patterns

   Sharding splits data, caching stores frequent info, and queueing manages tasks to keep performance high.

3. Final Answer:

   They keep the app fast and stable under heavy use. -> Option C

4. Quick Check:

   Advanced patterns improve speed and stability [OK]

Hint: Think: patterns help apps stay fast with many users [OK]

Common Mistakes:

• Confusing more storage with better speed
• Thinking patterns limit users
• Believing patterns slow the app

2. Which Firebase feature is correctly used to reduce read load by storing frequent data temporarily?

easy

A. Caching

B. Queueing

C. Sharding

D. Indexing

Solution

1. Step 1: Identify feature purpose

   Caching temporarily stores data to avoid repeated reads from the database.

2. Step 2: Match feature to description

   Queueing manages tasks, sharding splits data, indexing helps search but does not store data temporarily.

3. Final Answer:

   Caching -> Option A

4. Quick Check:

   Temporary data storage = Caching [OK]

Hint: Caching stores frequent data to reduce reads [OK]

Common Mistakes:

• Mixing queueing with caching
• Thinking sharding stores data temporarily
• Confusing indexing with caching

3. Given this Firebase sharding example:

const shardCount = 3;
function getShard(userId) {
  return userId % shardCount;
}
console.log(getShard(7));

What is the output?

medium

A. 1

B. 0

C. 3

D. 7

Solution

1. Step 1: Understand the modulo operation

   The function returns userId % shardCount, which is 7 % 3.

2. Step 2: Calculate 7 % 3

   7 divided by 3 is 2 with remainder 1, so 7 % 3 = 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   7 % 3 = 1 [OK]

Hint: Modulo gives remainder; 7 % 3 = 1 [OK]

Common Mistakes:

• Confusing modulo with division
• Returning userId instead of remainder
• Using shardCount as output

4. This Firebase queueing code snippet causes tasks to run all at once instead of one by one:

const tasks = [];
function addTask(task) {
  tasks.push(task);
  tasks.forEach(t => t());
}

What is the main issue?

medium

A. Tasks are pushed but never run

B. All tasks run every time a new task is added

C. Tasks run only once and then stop

D. Tasks run in reverse order

Solution

1. Step 1: Analyze the forEach call inside addTask

   Each time addTask runs, it calls all tasks in the array, not just the new one.

2. Step 2: Understand effect on task execution

   This causes all tasks to run repeatedly, not one by one as intended.

3. Final Answer:

   All tasks run every time a new task is added -> Option B

4. Quick Check:

   forEach runs all tasks on each add [OK]

Hint: Check where tasks.forEach is called inside addTask [OK]

Common Mistakes:

• Thinking tasks never run
• Assuming tasks run only once
• Believing tasks run in reverse

5. You want to scale a Firebase app with many users writing data simultaneously. Which advanced pattern best helps avoid database write conflicts?

hard

A. Use sharding to split data into multiple parts

B. Use caching to store data locally only

C. Use a single large document for all writes

D. Use queueing to process writes one at a time

Solution

1. Step 1: Identify write conflict problem

   Many users writing at once can cause conflicts if writes happen simultaneously on the same data.

2. Step 2: Match pattern to problem

   Queueing processes writes one by one, preventing conflicts. Sharding splits data but may not prevent conflicts on same shard. Caching stores data locally but doesn't solve write conflicts. A single large document increases conflict risk.

3. Final Answer:

   Use queueing to process writes one at a time -> Option D

4. Quick Check:

   Queueing controls write order to avoid conflicts [OK]

Hint: Queue writes to avoid conflicts in simultaneous access [OK]

Common Mistakes:

• Thinking sharding alone prevents conflicts
• Using caching to solve write conflicts
• Storing all writes in one document