Preview channels in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does a Firebase Preview Channel behave after 7 days?

You create a Firebase Preview Channel to test your web app deployment. What happens to this preview channel after 7 days?

A The preview channel is paused but not deleted after 7 days.

B The preview channel remains active indefinitely until manually deleted.

C The preview channel automatically expires and is deleted after 7 days.

D The preview channel is converted to a production channel after 7 days.

💡 Hint

Think about how preview channels are designed to be temporary for testing.

Firebase Preview Channels are temporary and automatically expire after 7 days to avoid clutter and unnecessary resource use.

❓ Architecture

intermediate

What is the main purpose of Firebase Preview Channels in deployment architecture?

Why would a developer use Firebase Preview Channels in their deployment workflow?

A To permanently host the production version of the app.

B To test changes in a live environment without affecting the production site.

C To backup the production app automatically.

D To monitor user analytics in real-time.

💡 Hint

Consider the need to test new features safely before going live.

Preview Channels allow developers to share and test changes in a live-like environment without impacting the main production site.

❓ security

advanced

Which security feature is automatically applied to Firebase Preview Channels URLs?

Firebase Preview Channels generate unique URLs for testing. What security feature do these URLs have by default?

A They are protected by IP whitelisting automatically.

B They require Firebase Authentication to access.

C They are publicly accessible without restrictions.

D They use unguessable, unique URLs to limit access.

💡 Hint

Think about how Firebase prevents random users from accessing preview builds.

Firebase Preview Channels use unique, hard-to-guess URLs to restrict access without requiring authentication or IP restrictions.

✅ Best Practice

advanced

What is a recommended best practice when using Firebase Preview Channels for team collaboration?

How should teams manage Firebase Preview Channels to ensure smooth collaboration and avoid confusion?

A Share the preview channel URL only with relevant team members and delete channels after testing.

B Keep all preview channels active indefinitely for future reference.

C Use the same preview channel URL for all features to simplify sharing.

D Avoid using preview channels and deploy directly to production for faster feedback.

💡 Hint

Think about managing temporary resources and access control.

Sharing URLs only with relevant people and deleting channels after use keeps the environment clean and secure.

🧠 Conceptual

expert

What happens if you deploy a new preview channel with the same ID as an existing one in Firebase Hosting?

You deploy a new preview channel using the same channel ID as an existing preview channel. What is the result?

A The existing preview channel is replaced with the new deployment, updating the URL content.

B Firebase creates a second preview channel with the same ID, causing a conflict error.

C Both preview channels run independently with different URLs.

D The deployment fails with an error because channel IDs must be unique.

💡 Hint

Consider how Firebase manages preview channels by ID.

Deploying to an existing preview channel ID updates the content at that channel's URL, replacing the previous deployment.

Practice

1. What is the main purpose of Firebase preview channels?

easy

A. To create temporary, shareable versions of your app for testing

B. To permanently host your live app

C. To backup your Firebase database

D. To monitor app usage statistics

Solution

1. Step 1: Understand preview channels concept

   Preview channels allow you to create temporary versions of your app that you can share for testing.

2. Step 2: Compare with other options

   Permanent hosting, backups, and monitoring are different Firebase features unrelated to preview channels.

3. Final Answer:

   To create temporary, shareable versions of your app for testing -> Option A

4. Quick Check:

   Preview channels = temporary test versions [OK]

Hint: Preview channels = temporary test app versions [OK]

Common Mistakes:

• Confusing preview channels with permanent hosting
• Thinking preview channels backup data
• Assuming preview channels track usage

2. Which command correctly creates a Firebase preview channel named test123?

easy

A. firebase hosting:channel:deploy test123

B. firebase deploy --channel test123

C. firebase hosting:deploy test123

D. firebase channel:create test123

Solution

1. Step 1: Recall the correct Firebase CLI command

   The command to create a preview channel is firebase hosting:channel:deploy CHANNEL_ID.

2. Step 2: Match the command with the channel name

   Replacing CHANNEL_ID with test123 gives firebase hosting:channel:deploy test123.

3. Final Answer:

   firebase hosting:channel:deploy test123 -> Option A

4. Quick Check:

   Correct CLI command = firebase hosting:channel:deploy test123 [OK]

Hint: Use hosting:channel:deploy with your channel name [OK]

Common Mistakes:

• Using deploy without hosting:channel
• Using channel:create which is invalid
• Mixing command order or flags

3. What happens when you deploy to a Firebase preview channel with the command firebase hosting:channel:deploy preview1?

medium

A. The live app is overwritten immediately

B. The app is published to the app stores

C. The Firebase database is reset

D. A temporary URL is created to share the app version

Solution

1. Step 1: Understand the effect of deploying to a preview channel

   Deploying to a preview channel creates a temporary, shareable URL for testing.

2. Step 2: Eliminate incorrect options

   It does not overwrite the live app, reset databases, or publish to app stores.

3. Final Answer:

   A temporary URL is created to share the app version -> Option D

4. Quick Check:

   Deploy to preview channel = temporary URL [OK]

Hint: Deploying preview channel creates temporary share URL [OK]

Common Mistakes:

• Thinking it overwrites live app immediately
• Confusing preview deploy with database reset
• Assuming it publishes app to stores

4. You ran firebase hosting:channel:deploy MyTest but got an error saying the channel name is invalid. What is a likely cause?

medium

A. You need to be logged out of Firebase CLI

B. You must include the --force flag

C. Channel names cannot contain uppercase letters

D. Channel names must be numeric only

Solution

1. Step 1: Check Firebase preview channel naming rules

   Channel names must be lowercase alphanumeric and can include dashes, but no uppercase letters.

2. Step 2: Evaluate other options

   --force flag is not required for naming; numeric-only names are not required; being logged out causes authentication errors, not naming errors.

3. Final Answer:

   Channel names cannot contain uppercase letters -> Option C

4. Quick Check:

   Invalid channel name = uppercase letters [OK]

Hint: Use only lowercase letters in channel names [OK]

Common Mistakes:

• Trying uppercase letters in channel names
• Assuming --force fixes naming errors
• Confusing auth errors with naming errors

5. You want to share a new feature with your team without affecting the live app. Which steps correctly use Firebase preview channels to do this?

hard

A. Run firebase deploy to update live app, then email the team

B. Run firebase hosting:channel:deploy featureX and share the generated URL

C. Create a new Firebase project and deploy the app there

D. Use firebase hosting:disable to stop live hosting temporarily

Solution

1. Step 1: Identify the correct way to create a preview version

   Using firebase hosting:channel:deploy featureX creates a temporary preview channel for sharing.

2. Step 2: Understand why other options are incorrect

   Deploy updates live app; creating new project is unnecessary; disabling hosting stops live app, not preview.

3. Final Answer:

   Run firebase hosting:channel:deploy featureX and share the generated URL -> Option B

4. Quick Check:

   Preview channel deploy + share URL = safe testing [OK]

Hint: Deploy preview channel and share URL, not live deploy [OK]

Common Mistakes:

• Deploying directly to live app by mistake
• Creating new projects unnecessarily
• Disabling hosting instead of previewing