Microservices - CI/CD for MicroservicesWhy is it important to keep the old environment intact for some time after switching traffic in blue-green deployment?ATo allow quick rollback if issues are detectedBTo save costs by running both environments indefinitelyCTo prevent users from accessing the new versionDTo perform database schema changes only on the old environmentCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand rollback importanceKeeping old environment allows quick switch back if new version has problems.Step 2: Eliminate incorrect reasonsRunning both indefinitely increases cost; preventing user access or schema changes on old environment are unrelated.Final Answer:To allow quick rollback if issues are detected -> Option AQuick Check:Old environment retention = rollback safety [OK]Quick Trick: Keep old environment for quick rollback [OK]Common Mistakes:Running both environments to save costBlocking user access intentionallyDoing schema changes only on old environment
Master "CI/CD for Microservices" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes Advanced Patterns - Outbox pattern for reliable events - Quiz 4medium Advanced Patterns - Sidecar pattern - Quiz 12easy CI/CD for Microservices - Mono-repo vs multi-repo - Quiz 8hard Configuration and Secrets Management - Dynamic configuration updates - Quiz 5medium Configuration and Secrets Management - Feature toggles - Quiz 4medium Migration from Monolith - Incremental migration plan - Quiz 11easy Migration from Monolith - Identifying service boundaries - Quiz 8hard Real-World Architecture Case Studies - When to revert to monolith - Quiz 7medium Real-World Architecture Case Studies - Lessons from microservices failures - Quiz 7medium Testing Microservices - Why testing distributed systems is complex - Quiz 8hard