Data modeling best practices in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing the right data structure in Firebase

You want to store user profiles in Firebase Realtime Database. Which data structure is best to allow quick access to each user by their unique ID?

A Store user profiles as a dictionary where each key is the user ID and the value is the profile data.

B Store user profiles in separate databases for each user.

C Store user profiles as a single string with all profiles concatenated.

D Store all user profiles in a list where each profile is an item without keys.

💡 Hint

Think about how you can quickly find a user profile by ID without scanning all data.

Using a dictionary with user IDs as keys allows direct access to each profile without scanning a list, making reads efficient.

❓ Architecture

intermediate

Avoiding data duplication in Firebase

You have a list of products and a list of orders referencing those products. What is the best way to model this to avoid duplicating product details in each order?

A Store product IDs inside orders and keep product details in a separate products collection.

B Store full product details inside each order entry.

C Store orders inside each product entry.

D Duplicate product details in both products and orders collections.

💡 Hint

Think about how to keep data consistent and avoid repeating the same information.

Referencing product IDs in orders and keeping product details separately avoids duplication and keeps data consistent.

❓ security

advanced

Securing nested data in Firebase Realtime Database

You want to restrict write access so users can only update their own profile data nested under /users/{userId}. Which Firebase Realtime Database rule correctly enforces this?

A

{
  "rules": {
    "users": {
      "$userId": {
        ".write": "true"
      }
    }
  }
}

B

{
  "rules": {
    "users": {
      "$userId": {
        ".write": "auth != null"
      }
    }
  }
}

C

{
  "rules": {
    "users": {
      "$userId": {
        ".write": "auth.uid == 'admin'"
      }
    }
  }
}

D

{
  "rules": {
    "users": {
      "$userId": {
        ".write": "auth != null && auth.uid == $userId"
      }
    }
  }
}

💡 Hint

Users should only write to their own user ID path, not others.

Rule D checks that the user is authenticated and their ID matches the userId in the path, restricting writes properly.

❓ service_behavior

advanced

Understanding Firebase Realtime Database event triggers

What happens when you attach a listener to /messages that triggers on child_added event?

A The listener triggers every time any child under /messages is changed or removed.

B The listener triggers once for each existing child under /messages and then for every new child added.

C The listener triggers only once when the first child is added under /messages.

D The listener triggers only once when the listener is attached.

💡 Hint

Think about how Firebase sends data when you first attach a listener.

The child_added event fires once for each existing child at the time of attachment, then for every new child added afterward.

✅ Best Practice

expert

Optimizing Firebase data structure for scalability

You have a chat app with thousands of users and millions of messages. Which data modeling approach best supports fast queries and scalability?

A Store all messages in a single list under <code>/messages</code> with no further nesting.

B Store messages as separate top-level nodes with random keys and no grouping.

C Nest messages under each chat room ID, e.g., <code>/chatRooms/{roomId}/messages</code>, and paginate queries by timestamp.

D Store all messages inside each user's profile to keep data together.

💡 Hint

Think about how to limit data downloaded and keep queries efficient.

Nesting messages under chat rooms and paginating by timestamp limits data size per query and improves scalability.