Why is trunk-based development considered beneficial for continuous integration and delivery (CI/CD)?

hard📝 Conceptual Q10 of 15

Git - Collaboration Workflows

ABecause it avoids any merges, simplifying the pipeline

BBecause it encourages frequent integration, enabling faster feedback and deployment

CBecause it requires manual testing before merging

DBecause it uses multiple main branches for parallel releases

Step-by-Step Solution

Solution:

Step 1: Link trunk-based development to CI/CD goals
Frequent integration helps detect issues early and speeds up deployment cycles.
Step 2: Evaluate options
Because it encourages frequent integration, enabling faster feedback and deployment correctly states this benefit. Other options contradict CI/CD principles or trunk-based development.
Final Answer:
Because it encourages frequent integration, enabling faster feedback and deployment -> Option B
Quick Check:
Trunk-based development supports CI/CD by frequent integration [OK]

Quick Trick: Frequent merges speed up CI/CD feedback [OK]

Common Mistakes:

Master "Collaboration Workflows" in Git

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Git Quizzes