Rollback deployments in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all previous Firebase hosting releases.

Firebase

firebase hosting:[1]:list

Drag options to blanks, or click blank then click option'

Areleases

Bdeploy

Crollback

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deploy' instead of 'releases' to list versions.

The firebase hosting:releases:list command lists all previous hosting releases, which helps you identify which version to rollback to.

2fill in blank

medium

Complete the command to rollback Firebase hosting to a specific release ID.

Firebase

firebase hosting:releases:[1] --release <release_id>

Drag options to blanks, or click blank then click option'

Adeploy

Brollback

Creleases

Dserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deploy' instead of 'rollback' for rollback operation.

The firebase hosting:releases:rollback command rolls back your site to a previous release using the release ID.

3fill in blank

hard

Fix the error in the rollback command by choosing the correct flag to specify the release ID.

Firebase

firebase hosting:releases:rollback [1]

Drag options to blanks, or click blank then click option'

A--version

B--project

C--target

D--release

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--version' or '--project' instead of '--release'.

The correct flag to specify the release ID in rollback is --release.

4fill in blank

hard

Fill both blanks to complete the command that lists releases and then rollbacks to a specific release.

Firebase

firebase hosting:[1]:list && firebase hosting:releases:[2] --release <release_id>

Drag options to blanks, or click blank then click option'

Areleases

Brollback

Cdeploy

Dserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deploy' instead of 'rollback' for the second command.

First, list the releases with firebase hosting:releases:list, then rollback with firebase hosting:releases:rollback using the release ID.

5fill in blank

hard

Fill all three blanks to complete the commands to list releases, rollback, and then verify the current hosting status.

Firebase

firebase hosting:[1]:list && firebase hosting:releases:[2] --release <release_id> && firebase hosting:releases:[3]

Drag options to blanks, or click blank then click option'

Areleases

Brollback

Clist

Ddeploy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deploy' instead of 'list' to check hosting state.

Use firebase hosting:releases:list to list, firebase hosting:releases:rollback to revert, and firebase hosting:releases:list to check the current hosting state.

Practice

1.

What is the main purpose of firebase hosting:rollback?

easy

A. To deploy a new version of the website

B. To create a backup of the current deployment

C. To delete all hosting versions permanently

D. To undo a recent deployment and restore the previous version

Solution

1. Step 1: Understand rollback purpose

   Rollback is used to undo a deployment that caused issues by restoring the previous stable version.

2. Step 2: Identify command function

   The command firebase hosting:rollback specifically reverts to the last working deployment.

3. Final Answer:

   To undo a recent deployment and restore the previous version -> Option D

4. Quick Check:

   Rollback = undo deployment [OK]

Hint: Rollback means undo last deployment fast [OK]

Common Mistakes:

• Confusing rollback with deploying new versions
• Thinking rollback deletes all versions
• Assuming rollback creates backups

2.

Which of the following is the correct syntax to rollback the last Firebase Hosting deployment?

easy

A. firebase hosting:rollback

B. firebase rollback hosting

C. firebase deploy:rollback hosting

D. firebase hosting rollback --last

Solution

1. Step 1: Recall correct command structure

   The official Firebase CLI command for rollback is firebase hosting:rollback.

2. Step 2: Check option syntax

   Options B, C, and D do not match the correct Firebase CLI syntax for rollback.

3. Final Answer:

   firebase hosting:rollback -> Option A

4. Quick Check:

   Correct syntax = firebase hosting:rollback [OK]

Hint: Remember exact command: firebase hosting:rollback [OK]

Common Mistakes:

• Swapping command parts order
• Adding extra flags not needed
• Using deploy instead of hosting

3.

Given the deployment history shows versions v5, v6, and v7, with v7 currently live, what will firebase hosting:rollback do?

medium

A. Rollback to version v6

B. Rollback to version v7 again

C. Rollback to version v5

D. Delete all versions except v7

Solution

1. Step 1: Identify current live version

   The current live version is v7, the latest deployment.

2. Step 2: Understand rollback behavior

   Rollback reverts to the previous version before the current one, which is v6.

3. Final Answer:

   Rollback to version v6 -> Option A

4. Quick Check:

   Rollback = previous version v6 [OK]

Hint: Rollback always reverts to the immediate previous version [OK]

Common Mistakes:

• Choosing the oldest version instead of previous
• Thinking rollback redeploys current version
• Assuming rollback deletes versions

4.

You ran firebase hosting:rollback but got an error saying "No previous version found." What is the most likely cause?

medium

A. Firebase CLI is outdated

B. You have no prior deployments to rollback to

C. Your internet connection is down

D. You typed the command incorrectly

Solution

1. Step 1: Analyze error message meaning

   The error "No previous version found" means there is no earlier deployment saved to revert to.

2. Step 2: Consider possible causes

   This usually happens if this is the first deployment or all previous versions were deleted.

3. Final Answer:

   You have no prior deployments to rollback to -> Option B

4. Quick Check:

   No previous version = no rollback possible [OK]

Hint: No previous version means no rollback available [OK]

Common Mistakes:

• Assuming command syntax error
• Blaming network issues
• Ignoring deployment history

5.

You deployed version v10 but found a critical bug. You want to rollback to v9. However, v9 was deleted from the history. What is the best approach to recover your site quickly?

hard

A. Delete v10 and wait for Firebase to restore v9 automatically

B. Run firebase hosting:rollback to get v9 back

C. Redeploy a saved local copy of v9 manually

D. Contact Firebase support to restore v9

Solution

1. Step 1: Understand rollback limitations

   Rollback only works if the previous version exists in deployment history. Since v9 is deleted, rollback cannot restore it.

2. Step 2: Identify recovery method

   The best way is to redeploy a saved local copy of v9 manually to restore the stable version quickly.

3. Step 3: Evaluate other options

   Options B and C won't work because rollback needs the version present, and Firebase does not auto-restore deleted versions. Contact Firebase support to restore v9 may take too long for urgent fixes.

4. Final Answer:

   Redeploy a saved local copy of v9 manually -> Option C

5. Quick Check:

   Deleted version = manual redeploy needed [OK]

Hint: Rollback needs version history; redeploy local copy if missing [OK]

Common Mistakes:

• Expecting rollback to restore deleted versions
• Waiting for automatic Firebase restore
• Ignoring local backups