Microservices - CI/CD for MicroservicesIn a multi-repo setup, what happens when a shared library is updated in one repository?AAll microservices automatically receive the updateBEach microservice must update its dependency manuallyCThe update is blocked until all repos merge changesDThe shared library is deleted from other reposCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand multi-repo shared library managementIn multi-repo, each microservice repo manages its own dependencies separately.Step 2: Effect of updating shared libraryUpdating the library in one repo does not propagate automatically; each service must update manually.Final Answer:Each microservice must update its dependency manually -> Option BQuick Check:Multi-repo shared update = manual per service [OK]Quick Trick: Multi-repo requires manual dependency updates [OK]Common Mistakes:Assuming automatic update propagationThinking updates are blocked until mergesBelieving shared library is deleted elsewhere
Master "CI/CD for Microservices" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes Advanced Patterns - Choreography vs orchestration - Quiz 15hard Advanced Patterns - Backend for Frontend (BFF) pattern - Quiz 2easy Advanced Patterns - Sidecar pattern - Quiz 12easy CI/CD for Microservices - Why independent deployment is a microservices advantage - Quiz 11easy Migration from Monolith - Identifying service boundaries - Quiz 3easy Migration from Monolith - Strangler fig pattern - Quiz 12easy Migration from Monolith - Database decomposition strategy - Quiz 9hard Real-World Architecture Case Studies - Microservices maturity model - Quiz 9hard Real-World Architecture Case Studies - Architecture decision records (ADR) - Quiz 5medium Testing Microservices - Chaos engineering basics - Quiz 13medium