Rollback strategies in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blue-Green Deployment Rollback

In a blue-green deployment, if the new version (green) fails after release, what is the immediate rollback action?

A Switch traffic back to the blue environment while fixing the green environment.

B Restart the green environment services to clear errors.

C Deploy a hotfix directly to the green environment without switching traffic.

D Delete the blue environment to force all traffic to green.

💡 Hint

Think about how blue-green deployment separates live and new versions.

Blue-green deployment keeps two identical environments. Rollback means switching traffic back to the stable blue environment.

❓ Architecture

intermediate

Rollback Strategy in Canary Releases

During a canary release, a small percentage of users get the new version. If errors are detected, what is the best rollback approach?

A Increase traffic to the canary version to gather more error data.

B Restart the canary version services and continue routing traffic.

C Deploy a patch to the canary version without affecting traffic routing.

D Stop sending traffic to the canary version and route all users to the stable version.

💡 Hint

Consider how canary releases limit exposure to new versions.

Rollback in canary releases involves stopping traffic to the new version and reverting users to the stable version to avoid impact.

❓ scaling

advanced

Capacity Planning for Rollback in Microservices

You have a microservices system using blue-green deployment. To support rollback, what capacity planning approach is best?

A Use a single environment and redeploy on rollback to save resources.

B Scale down the inactive environment to zero to save costs during normal operation.

C Maintain full capacity for both blue and green environments simultaneously.

D Only keep the active environment running and recreate the other on rollback.

💡 Hint

Think about how quickly rollback must happen without downtime.

Maintaining full capacity for both environments allows instant rollback without delay or downtime.

❓ tradeoff

advanced

Tradeoffs Between Database Rollback Strategies

Which rollback strategy for databases in microservices has the highest risk of data inconsistency?

A Implementing backward-compatible schema changes with feature toggles.

B Using database backups to restore to a previous state.

C Applying compensating transactions to undo changes.

D Rolling forward with patches to fix issues without rollback.

💡 Hint

Consider what happens to data created after the backup point.

Restoring from backups can lose data created after the backup, causing inconsistency and data loss.

❓ estimation

expert

Estimating Downtime During Rollback

A microservices system uses blue-green deployment with 10 services. Each service takes 30 seconds to switch traffic and 10 seconds to verify health. Estimate the minimum downtime during rollback if services are switched sequentially.

A 400 seconds

B 40000 seconds

C 4000 seconds

D 400000 seconds

💡 Hint

Calculate total time per service and multiply by number of services.

Each service takes 30 + 10 = 40 seconds. For 10 services sequentially: 40 * 10 = 400 seconds. However, downtime is the total time all services are switched, so 400 seconds is correct. Since the question asks minimum downtime during rollback, and switching traffic is sequential, downtime accumulates to 400 seconds.