Microservices - CI/CD for MicroservicesIn a rolling update, if a failure is detected in version 3 of the service, what is the expected rollback behavior?ARollback to version 2 and stop further updatesBContinue updating to version 4 ignoring errorsCRollback to version 1 immediatelyDDeploy version 3 again without changesCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand rolling update rollbackRolling update replaces versions incrementally; rollback reverts to last stable version.Step 2: Identify correct rollback targetIf version 3 fails, rollback goes back to version 2, the last stable version.Final Answer:Rollback to version 2 and stop further updates -> Option AQuick Check:Failure in version 3 = rollback to version 2 [OK]Quick Trick: Rollback reverts to last stable version in rolling update [OK]Common Mistakes:Ignoring errors and continuing updatesRolling back too far to version 1Redeploying faulty version
Master "CI/CD for Microservices" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes Advanced Patterns - Backend for Frontend (BFF) pattern - Quiz 13medium Advanced Patterns - Backend for Frontend (BFF) pattern - Quiz 2easy Configuration and Secrets Management - Environment-based configuration - Quiz 5medium Migration from Monolith - Incremental migration plan - Quiz 12easy Migration from Monolith - Identifying service boundaries - Quiz 12easy Migration from Monolith - Database decomposition strategy - Quiz 11easy Real-World Architecture Case Studies - Spotify architecture overview - Quiz 7medium Real-World Architecture Case Studies - Architecture decision records (ADR) - Quiz 8hard Testing Microservices - Chaos engineering basics - Quiz 8hard Testing Microservices - Test environments and data - Quiz 10hard