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.