User profile data in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is user profile data in Firebase?

User profile data in Firebase is information stored about a user, such as their name, email, and preferences, which helps personalize their experience.

beginner

Where is user profile data typically stored in Firebase?

User profile data is typically stored in Firebase Realtime Database or Firestore, which are cloud-hosted NoSQL databases.

intermediate

How can you secure user profile data in Firebase?

You secure user profile data by using Firebase Authentication to identify users and Firebase Security Rules to control who can read or write data.

beginner

What is the role of Firebase Authentication in managing user profile data?

Firebase Authentication verifies user identity, enabling safe access to user profile data and linking data to the correct user.

beginner

Why is it important to keep user profile data updated?

Keeping user profile data updated ensures the app provides accurate, personalized experiences and maintains correct user information.

Where is user profile data commonly stored in Firebase?

A Firebase Functions

B Firebase Hosting

C Firebase Cloud Messaging

D Firestore or Realtime Database

User profile data is stored in Firestore or Realtime Database, which are designed for storing and syncing data.

What Firebase service helps verify user identity before accessing profile data?

A Firebase Crashlytics

B Firebase Storage

C Firebase Authentication

D Firebase Analytics

Firebase Authentication verifies who the user is to protect access to their profile data.

Which Firebase feature controls who can read or write user profile data?

A Firebase Security Rules

B Firebase Hosting

C Firebase Cloud Functions

D Firebase Performance Monitoring

Firebase Security Rules define permissions for reading and writing data.

Why should user profile data be kept up to date?

A To provide accurate and personalized app experiences

B To increase app download speed

C To reduce Firebase costs

D To improve app graphics

Updated profile data helps the app personalize content and services correctly.

Which Firebase database type is NoSQL and suitable for user profile data?

A MySQL

B Firestore

C PostgreSQL

D Oracle DB

Firestore is a NoSQL database provided by Firebase for flexible data storage.

Explain how Firebase Authentication and Security Rules work together to protect user profile data.

Think about who can see or change the data after login.

Describe where and why user profile data is stored in Firebase.

Consider the database types Firebase offers.

Practice

1. What is the main purpose of storing user profile data in Firebase Firestore?

easy

A. To host static website files

B. To run server-side scripts automatically

C. To send emails to users

D. To save personal information for each user securely

Solution

1. Step 1: Understand user profile data purpose

   User profile data holds personal details like name and email for each user.

2. Step 2: Identify Firebase Firestore role

   Firestore stores this data securely and allows easy access and updates.

3. Final Answer:

   To save personal information for each user securely -> Option D

4. Quick Check:

   User profile data = personal info storage [OK]

Hint: User profiles store personal info, not run scripts or host files [OK]

Common Mistakes:

• Confusing Firestore with hosting or email services
• Thinking Firestore runs backend code automatically
• Assuming user profiles are for sending emails

2. Which Firebase Firestore syntax correctly creates a document for a user profile with ID 'user123'?

easy

A. db.collection('users').doc('user123').set({name: 'Alice'})

B. db.users('user123').add({name: 'Alice'})

C. db.collection('users').add('user123', {name: 'Alice'})

D. db.doc('users/user123').create({name: 'Alice'})

Solution

1. Step 1: Review Firestore document creation syntax

   Use collection('name').doc('id').set(data) to create or overwrite a document.

2. Step 2: Match syntax with options

   db.collection('users').doc('user123').set({name: 'Alice'}) matches correct syntax: collection, doc, then set with data object.

3. Final Answer:

   db.collection('users').doc('user123').set({name: 'Alice'}) -> Option A

4. Quick Check:

   Correct Firestore doc creation = db.collection('users').doc('user123').set({name: 'Alice'}) [OK]

Hint: Use collection().doc().set() to create user profile docs [OK]

Common Mistakes:

• Using add() with document ID specified
• Wrong method names like create() instead of set()
• Incorrect chaining of methods

3. Given this code snippet, what will be the output if the user document does not exist?

const docRef = db.collection('users').doc('user999');
docRef.get().then(doc => {
  if (doc.exists) {
    console.log(doc.data().name);
  } else {
    console.log('No user found');
  }
});

medium

A. No user found

B. undefined

C. Error: Document not found

D. null

Solution

1. Step 1: Understand doc.exists property

   doc.exists is false if document does not exist in Firestore.

2. Step 2: Follow code logic for missing document

   If doc.exists is false, code logs 'No user found'.

3. Final Answer:

   No user found -> Option A

4. Quick Check:

   Missing doc triggers else block = 'No user found' [OK]

Hint: Check doc.exists before accessing data to avoid errors [OK]

Common Mistakes:

• Assuming doc.data() returns null or undefined
• Expecting an error instead of else block output
• Ignoring the else condition

4. Identify the error in this Firebase Firestore code to update a user's profile name:

db.collection('users').doc('user123').update({
  username: 'Bob'
});

medium

A. update() cannot be used to change existing fields

B. Missing await or then to handle promise

C. Field name should be 'name' not 'username'

D. Document ID 'user123' must be a number

Solution

1. Step 1: Check Firestore update method usage

   update() returns a promise and should be handled with await or then.

2. Step 2: Identify missing promise handling

   Code does not handle promise, which can cause silent failures.

3. Final Answer:

   Missing await or then to handle promise -> Option B

4. Quick Check:

   Firestore update returns promise, must handle it [OK]

Hint: Always handle promises with await or then in Firestore calls [OK]

Common Mistakes:

• Thinking update() cannot change fields
• Assuming field names must be fixed
• Believing document IDs must be numeric

5. You want to store user profiles with optional phone numbers. Which Firestore data structure best handles missing phone numbers without errors?

hard

A. Set phone number field to empty string if missing

B. Always set phone number field to null

C. Include phone number field only if user provides it

D. Create a separate collection for phone numbers

Solution

1. Step 1: Understand optional fields in Firestore

   Firestore allows documents to omit fields that are not provided.

2. Step 2: Choose best practice for optional data

   Including the phone number field only when available avoids storing empty or null values and reduces confusion.

3. Final Answer:

   Include phone number field only if user provides it -> Option C

4. Quick Check:

   Omit optional fields if missing to keep data clean [OK]

Hint: Omit optional fields instead of storing empty or null values [OK]

Common Mistakes:

• Storing empty strings which can confuse queries
• Using null values that may cause unexpected behavior
• Overcomplicating with separate collections for simple optional data