Microservices - CI/CD for MicroservicesWhich of the following is the correct syntax to trigger a pipeline only for Service A in a CI/CD system?Atrigger: branches: - 'main' - 'develop'Btrigger: all: trueCtrigger: exclude: - 'serviceA/**'Dtrigger: paths: - 'serviceA/**'Check Answer
Step-by-Step SolutionSolution:Step 1: Understand pipeline triggersTriggering pipelines based on file paths limits runs to changes in specific service folders.Step 2: Analyze optionstrigger: paths: - 'serviceA/**' triggers only when files in 'serviceA' change; others trigger on all changes or exclude serviceA.Final Answer:trigger: paths: - 'serviceA/**' -> Option DQuick Check:Path-based trigger = service-specific pipeline [OK]Quick Trick: Use path triggers to isolate service pipelines [OK]Common Mistakes:Triggering on all branches ignores service specificityExcluding service paths triggers unrelated servicesNot using path filters causes unnecessary builds
Master "CI/CD for Microservices" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes CI/CD for Microservices - Mono-repo vs multi-repo - Quiz 3easy Configuration and Secrets Management - Dynamic configuration updates - Quiz 14medium Migration from Monolith - Anti-corruption layer - Quiz 14medium Migration from Monolith - Anti-corruption layer - Quiz 12easy Migration from Monolith - Why gradual migration reduces risk - Quiz 1easy Real-World Architecture Case Studies - When to revert to monolith - Quiz 1easy Real-World Architecture Case Studies - Netflix architecture overview - Quiz 9hard Testing Microservices - Unit testing services - Quiz 15hard Testing Microservices - Test environments and data - Quiz 6medium Testing Microservices - End-to-end testing challenges - Quiz 7medium