Writing data (set, update, push) in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when using set() with merge option?

Consider this Firebase Realtime Database operation:

ref.set({name: 'Alice'}, {merge: true})

What is the effect of using set with the merge: true option?

A It throws an error because set() does not support a merge option in Realtime Database.

B It updates only the specified fields in the existing data, preserving other fields.

C It appends the new object as a child node under the reference.

D It replaces the entire data at the reference with the new object, removing any existing fields.

💡 Hint

Think about the difference between set() and update() in Firebase Realtime Database.

In Firebase Realtime Database, the set() method replaces all data at the specified reference. The merge option is not supported here; it is a Firestore feature. To update specific fields without overwriting, update() should be used.

❓ Configuration

intermediate

Which code correctly pushes a new item to a list in Firebase Realtime Database?

You want to add a new message to a list of messages stored under /chat/messages. Which code snippet correctly pushes a new message with text 'Hello'?

A firebase.database().ref('/chat/messages').push({text: 'Hello'})

B firebase.database().ref('/chat/messages').set({text: 'Hello'})

C firebase.database().ref('/chat/messages').update({text: 'Hello'})

D firebase.database().ref('/chat/messages').child('text').push('Hello')

💡 Hint

Remember that push() creates a unique key for each new item in a list.

The push() method adds a new child with a unique key under the specified reference. Using set() or update() directly on the list path would overwrite or update the entire list, not add a new item.

❓ Architecture

advanced

How to atomically update multiple fields in Firebase Realtime Database?

You want to update the user's name and age at /users/user123 in a single operation without overwriting other data. Which approach achieves this atomically?

A Use push() with an object containing name and age fields.

B Use set() with an object containing only name and age fields.

C Use update() with an object containing name and age fields.

D Use set() with merge option set to true.

💡 Hint

Think about which method updates specific fields without replacing the entire node.

The update() method updates only the specified fields at the reference without overwriting other data. It is atomic and efficient for partial updates. set() replaces the entire node, push() adds a new child, and set() with merge is not supported in Realtime Database.

❓ security

advanced

What happens if a user tries to push data without write permission in Firebase Realtime Database?

Assuming Firebase Realtime Database rules deny write access to a user at /posts, what happens when the user runs ref.push({title: 'New Post'})?

A The data is pushed successfully and visible to all users.

B The data is pushed but only visible to the user who pushed it.

C The push() call silently fails without error.

D The push() call throws a permission denied error.

💡 Hint

Consider how Firebase enforces security rules on write operations.

Firebase Realtime Database enforces security rules on every write. If the user lacks write permission, the push() operation fails and returns a permission denied error.

✅ Best Practice

expert

Which approach minimizes data loss risk when updating nested data in Firebase Realtime Database?

You need to update a deeply nested field /users/user123/profile/age without affecting other profile data. Which method is best to minimize risk of data loss?

A Use set() on <code>/users/user123/profile</code> with the entire profile object including the updated age.

B Use update() on <code>/users/user123/profile</code> with only the age field.

C Use set() on <code>/users/user123/profile/age</code> with the new age value.

D Use push() on <code>/users/user123/profile/age</code> with the new age value.

💡 Hint

Think about partial updates and avoiding overwriting unrelated data.

Using update() on the profile node with only the age field updates that field without overwriting other profile data. Using set() on profile replaces the entire profile, risking data loss. push() is for adding new child nodes, not updating values.