Rollback deployments in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Firebase Hosting Rollback Behavior

You deployed a new version of your Firebase Hosting site but noticed a critical bug. You want to rollback to the previous version quickly.

What happens when you run firebase hosting:rollback?

A It instantly switches the live site to the previous deployed version without downtime.

B It creates a new deployment identical to the previous version but does not switch traffic automatically.

C It deletes the current version and redeploys the previous version, causing downtime.

D It archives all versions but requires manual DNS changes to rollback.

💡 Hint

Think about how Firebase Hosting manages versions and traffic switching.

Firebase Hosting rollback instantly switches the live site to the previous deployed version without downtime by updating the serving configuration.

❓ Configuration

intermediate

Rollback Command Usage

You want to rollback your Firebase Hosting deployment to the version deployed 3 deployments ago.

Which command correctly rolls back to that specific version?

A firebase hosting:rollback --version-name 3

B firebase hosting:rollback --to 3

C firebase hosting:rollback 3

D firebase hosting:rollback --target 3

💡 Hint

Check the official Firebase CLI rollback command syntax.

The version number is specified as a positional argument: firebase hosting:rollback 3. Other flags are invalid.

❓ Architecture

advanced

Rollback Impact on CDN Cache

After rolling back a Firebase Hosting deployment, what happens to the cached content on the CDN edge servers?

A The rollback triggers a manual cache purge request that you must run separately.

B The CDN cache continues serving the old content until it expires naturally.

C The CDN cache is disabled temporarily during rollback to prevent stale content.

D The CDN cache is automatically invalidated and refreshed with the rollback version content.

💡 Hint

Consider how Firebase Hosting manages content freshness after deployment changes.

Firebase Hosting automatically invalidates CDN caches on rollback to ensure users get the correct content immediately.

❓ security

advanced

Rollback and Security Rules Consistency

You rolled back your Firebase Hosting deployment to a previous version. What happens to the Firebase Security Rules associated with the hosting content?

A Security Rules remain as they were in the current version and do not rollback automatically.

B Security Rules rollback automatically to the version associated with the hosting rollback.

C Security Rules are disabled temporarily until manually re-enabled after rollback.

D Security Rules are deleted and must be redeployed manually after rollback.

💡 Hint

Think about how Firebase separates hosting content from security rules deployment.

Firebase Security Rules are managed separately and do not rollback automatically with hosting content.

✅ Best Practice

expert

Rollback Strategy for Zero Downtime

You want to implement a rollback strategy for Firebase Hosting that guarantees zero downtime and quick recovery from faulty deployments.

Which approach best achieves this?

A Deploy a new version with fixes and manually update DNS records to point to it.

B Use Firebase Hosting's built-in rollback command to instantly switch versions without downtime.

C Delete the faulty deployment and redeploy the previous version from local files.

D Pause all traffic to the site, rollback, then resume traffic after verification.

💡 Hint

Consider the features Firebase Hosting provides for deployment management.

Firebase Hosting's rollback command instantly switches traffic to a previous version with no downtime, making it the best practice for quick recovery.