Rollback strategies in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the rollback method used in a deployment pipeline.

Microservices

deployment.rollback_method = "[1]"

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

Acanary

Bmanual

Crolling

Dblue-green

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing automated deployment strategies instead of rollback methods.

Confusing deployment strategies with rollback triggers.

The manual rollback method requires explicit intervention to revert changes, which is a common basic rollback strategy.

2fill in blank

medium

Complete the code to define the rollback trigger condition based on error rate.

Microservices

if error_rate > [1]:
    trigger_rollback()

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

A0.05

B0.5

C0.005

D0.5%

Attempts:

3 left

💡 Hint

Common Mistakes

Using percentage strings instead of decimal numbers.

Setting the threshold too high or too low.

An error rate threshold of 0.05 (5%) is a common trigger for rollback in microservices deployments.

3fill in blank

hard

Fix the error in the rollback function call to correctly revert to the previous stable version.

Microservices

rollback_to_version([1])

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

Alast_stable_version

Bprevious_version

Ccurrent_version - 1

Dversion - 1

Attempts:

3 left

💡 Hint

Common Mistakes

Using variables that may not be defined or clear.

Subtracting from current version without checking stability.

The function should rollback to the last_stable_version to ensure stability after failure.

4fill in blank

hard

Fill both blanks to implement a canary rollback strategy with traffic shifting and monitoring.

Microservices

canary_deployment.shift_traffic([1])
monitoring.set_alert_threshold([2])

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

A10%

B5%

Cerror_rate > 0.05

Derror_rate > 0.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using too high traffic shift percentage initially.

Setting alert threshold too high to detect errors late.

Shift 10% traffic initially and set alert threshold to trigger rollback if error rate exceeds 5%.

5fill in blank

hard

Fill all three blanks to define a rollback plan with version tagging, backup creation, and rollback execution.

Microservices

tag_version([1])
create_backup([2])
execute_rollback([3])

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

Anew_release

Bcurrent_state

Clast_stable_release

Dbackup_snapshot

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing backup with release tags.

Rolling back to incorrect version identifiers.

Tag the new_release, create a backup of the current_state, and rollback to the last_stable_release if needed.

Practice

1. What is the main purpose of a rollback strategy in microservices?

easy

A. To quickly undo a bad deployment and restore the previous stable state

B. To add new features to the system without downtime

C. To permanently delete old versions of services

D. To monitor system performance continuously

Solution

1. Step 1: Understand rollback purpose

   Rollback strategies are designed to revert changes that cause issues, restoring stability.

2. Step 2: Identify correct purpose in options

   Only To quickly undo a bad deployment and restore the previous stable state describes undoing a bad deployment to restore a stable state.

3. Final Answer:

   To quickly undo a bad deployment and restore the previous stable state -> Option A

4. Quick Check:

   Rollback purpose = Undo bad deployment [OK]

Hint: Rollback means undo bad changes fast [OK]

Common Mistakes:

• Confusing rollback with feature deployment
• Thinking rollback deletes old versions permanently
• Mixing rollback with monitoring

2. Which of the following is a correct description of the blue-green deployment rollback method?

easy

A. Switch traffic back to the old environment if the new one fails

B. Gradually increase traffic to the new version while monitoring

C. Manually fix database schema errors after deployment

D. Deploy new code directly to production without testing

Solution

1. Step 1: Recall blue-green deployment basics

   Blue-green uses two identical environments; one active, one idle for new version.

2. Step 2: Identify rollback action

   If new version fails, traffic switches back to old environment instantly.

3. Final Answer:

   Switch traffic back to the old environment if the new one fails -> Option A

4. Quick Check:

   Blue-green rollback = Switch traffic back [OK]

Hint: Blue-green rollback switches traffic instantly [OK]

Common Mistakes:

• Confusing blue-green with canary deployment
• Thinking rollback fixes database manually
• Ignoring traffic switching concept

3. Consider this simplified code snippet for a canary deployment rollback trigger:

if error_rate > 0.05:
    rollback_canary()

What happens when the error rate exceeds 5% during canary deployment?

medium

A. The system continues deployment without changes

B. The error rate is ignored and logged only

C. The rollback_canary function is called to revert changes

D. The deployment is paused but not rolled back

Solution

1. Step 1: Analyze the condition in code

   The code checks if error_rate is greater than 0.05 (5%).

2. Step 2: Understand the action on condition true

   If true, rollback_canary() is called to revert the canary deployment.

3. Final Answer:

   The rollback_canary function is called to revert changes -> Option C

4. Quick Check:

   Error rate > 5% triggers rollback [OK]

Hint: Error rate > threshold triggers rollback function [OK]

Common Mistakes:

• Ignoring the rollback call in the code
• Assuming deployment pauses without rollback
• Confusing logging with rollback action

4. A microservice deployment uses database migration with rollback scripts. The rollback script fails due to a syntax error. What is the best immediate action?

medium

A. Ignore the failure and continue deployment

B. Restart the service without rollback

C. Delete the database and start fresh

D. Manually fix the rollback script and retry rollback

Solution

1. Step 1: Identify rollback script failure impact

   A syntax error in rollback script prevents safe undo of migration changes.

2. Step 2: Choose safe recovery action

   Fixing the script manually and retrying rollback ensures data integrity and system stability.

3. Final Answer:

   Manually fix the rollback script and retry rollback -> Option D

4. Quick Check:

   Fix rollback script error before retrying [OK]

Hint: Fix rollback script errors before retrying rollback [OK]

Common Mistakes:

• Ignoring rollback failure and proceeding
• Deleting database without backup
• Restarting service without fixing rollback

5. You have a microservices system using canary deployments with automated rollback on failure. Suddenly, a rollback triggers repeatedly due to a false positive error spike caused by monitoring noise. What is the best architectural improvement to reduce unnecessary rollbacks?

hard

A. Disable rollback automation and rely on manual checks

B. Implement a cooldown period before allowing another rollback

C. Remove monitoring to avoid false alarms

D. Rollback immediately on any error spike without delay

Solution

1. Step 1: Understand problem cause

   False positive error spikes cause repeated rollbacks due to noisy monitoring data.

2. Step 2: Identify architectural fix

   Adding a cooldown period prevents rapid repeated rollbacks, allowing noise to settle before next rollback.

3. Final Answer:

   Implement a cooldown period before allowing another rollback -> Option B

4. Quick Check:

   Cooldown period reduces rollback noise impact [OK]

Hint: Cooldown period prevents rollback storms from noise [OK]

Common Mistakes:

• Disabling automation loses rollback benefits
• Removing monitoring hides real issues
• Rolling back immediately causes instability