A team using multi-repo faces frequent integration issues because services depend on shared code. What is the most likely cause?

medium📝 Analysis Q14 of 15

Microservices - CI/CD for Microservices

AMulti-repo automatically merges conflicting changes causing errors

BMono-repo forces all services to use outdated code

CUsing multi-repo disables version control

DShared code changes are not synchronized across separate repositories

Step-by-Step Solution

Solution:

Step 1: Identify multi-repo challenges
In multi-repo, shared code updates must be manually synchronized, or services may use incompatible versions.
Step 2: Evaluate incorrect options
Multi-repo automatically merges conflicting changes causing errors is false as multi-repo does not auto-merge. Mono-repo forces all services to use outdated code is about mono-repo. Using multi-repo disables version control is incorrect about version control.
Final Answer:
Shared code changes are not synchronized across separate repositories -> Option D
Quick Check:
Multi-repo needs manual sync of shared code [OK]

Quick Trick: Multi-repo needs manual sync for shared code [OK]

Common Mistakes:

Master "CI/CD for Microservices" in Microservices

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Microservices Quizzes