Firebase Emulator Suite - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Firebase Emulator Suite Behavior

When running the Firebase Emulator Suite locally, which behavior correctly describes how data is handled compared to the live Firebase services?

A Data in the emulators is stored locally and isolated; it does not affect or sync with the live Firebase project.

B Data written to the emulators is automatically synced to the live Firebase project in real-time.

C The emulator suite only simulates authentication but uses live database and storage services.

D Emulators require an active internet connection to proxy all requests to the live Firebase backend.

💡 Hint

Think about whether local emulators affect your real cloud data.

The Firebase Emulator Suite runs services locally and stores data only on your machine. It does not sync or affect your live Firebase project data, allowing safe testing without risk to production.

❓ Configuration

intermediate

Configuring Firebase Emulator Suite Ports

You want to run the Firebase Emulator Suite but need to change the default port for the Firestore emulator from 8080 to 8085. Which configuration snippet in firebase.json correctly sets this?

A { "emulators": { "firestore": { "port": 8085 } } }

B { "firestore": { "emulatorPort": 8085 } }

C { "emulators": { "firestore": { "emulatorPort": 8085 } } }

D { "emulators": { "firestore": { "portNumber": 8085 } } }

💡 Hint

Check the official Firebase Emulator Suite config structure for port settings.

The correct key to set the port for Firestore emulator inside firebase.json is port under emulators.firestore. Other keys like emulatorPort or portNumber are invalid.

❓ security

advanced

Security Implications of Using Firebase Emulator Suite

Which statement correctly describes a security best practice when using the Firebase Emulator Suite for local development?

A Always expose the emulator ports publicly on the internet to allow remote team members to connect easily.

B Use the same API keys and credentials in emulators as in production to ensure consistency.

C Disable all Firebase security rules when using emulators since local testing is always safe.

D Use the emulator suite only on trusted local networks and avoid exposing emulator ports externally to prevent unauthorized access.

💡 Hint

Consider risks of exposing local services to the internet.

Emulators run locally and do not enforce production security rules by default. Exposing emulator ports publicly can lead to unauthorized access. Best practice is to keep emulators on trusted local networks and not expose them externally.

❓ Architecture

advanced

Firebase Emulator Suite Integration Architecture

You want to test a Firebase Cloud Function locally that triggers on Firestore document writes. Which setup correctly integrates the Firebase Emulator Suite components to enable this local testing?

A Run Firestore emulator and deploy functions to production; test triggers by writing to the local Firestore emulator.

B Run only the Functions emulator; it automatically connects to the live Firestore service for triggers.

C Run Firestore emulator and Functions emulator; configure Functions emulator to listen to Firestore emulator events locally.

D Run Firestore emulator and Functions emulator separately without linking; triggers will not fire locally.

💡 Hint

Think about how emulators communicate to simulate triggers.

To test Cloud Functions triggered by Firestore events locally, both Firestore and Functions emulators must run. The Functions emulator listens to events from the Firestore emulator, enabling local trigger testing without deploying to production.

🧠 Conceptual

expert

Firebase Emulator Suite Data Persistence Behavior

After stopping and restarting the Firebase Emulator Suite, what happens to the data stored in the Firestore and Realtime Database emulators by default?

A All data is automatically persisted to disk and restored on restart without extra configuration.

B Data is lost on restart unless you enable data persistence explicitly in the emulator configuration.

C Firestore data persists by default, but Realtime Database data is always lost on restart.

D Realtime Database data persists by default, but Firestore data is always lost on restart.

💡 Hint

Consider whether emulator data is saved automatically or requires setup.

By default, the Firebase Emulator Suite does not persist data to disk unless you enable data persistence explicitly. Without enabling persistence, data is lost on restart. You can configure the emulators to persist data if desired.