Bird
0
0

How does combining gradual migration with feature toggles improve risk management?

hard📝 Trade-off Q9 of 15
Microservices - Migration from Monolith
How does combining gradual migration with feature toggles improve risk management?
AIt forces all users to use new services immediately
BIt disables testing during migration
CIt allows enabling new microservices only for select users before full rollout
DIt removes the need for rollback mechanisms
Step-by-Step Solution
Solution:

  1. Step 1: Understand feature toggles role

    Feature toggles let you turn features on/off for specific users or groups.

  2. Step 2: Combine with gradual migration

    This allows testing new microservices with limited users, reducing risk before full rollout.

  3. Final Answer:

    It allows enabling new microservices only for select users before full rollout -> Option C

  4. Quick Check:

    Feature toggles + gradual migration = safer rollout = B [OK]
Quick Trick: Toggle features for limited users first [OK]
Common Mistakes:
  • Forcing all users immediately
  • Skipping testing
  • Ignoring rollback needs

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Advanced Patterns - Sidecar pattern - Quiz 14medium CI/CD for Microservices - Canary deployment - Quiz 8hard CI/CD for Microservices - Why independent deployment is a microservices advantage - Quiz 6medium Configuration and Secrets Management - Secrets management (Vault, AWS Secrets Manager) - Quiz 4medium Configuration and Secrets Management - Why externalized config enables flexibility - Quiz 15hard Migration from Monolith - Incremental migration plan - Quiz 13medium Real-World Architecture Case Studies - When to revert to monolith - Quiz 15hard Testing Microservices - Why testing distributed systems is complex - Quiz 14medium Testing Microservices - Contract testing (Pact) - Quiz 1easy Testing Microservices - Unit testing services - Quiz 12easy