Scaled Agile Exam SAFe-DevOps Topic 4 Question 18 Discussion

Actual exam question for Scaled Agile's SAFe-DevOps exam

Question #: 18
Topic #: 4

[All SAFe-DevOps Questions]

What is trunk-based development?

AEach developer maintains a separate branch

BTeams with similar dependencies create one single branch for the team's work

CAll teams committing their code into one trunk

DEvery team works in their own trunk

Show Suggested Answer

Suggested Answer: C

Trunk-based development is a version control management practice where all developers work on the same trunk of shared code. The trunk is always in a releasable state, which means that at least once a day, developers must integrate their changes to the trunk. This is accomplished through short-lived feature branches related to project tasks. Trunk-based development is a common practice among DevOps teams and part of the DevOps lifecycle since it streamlines merging and integration phases. It also enables continuous integration, which is the practice of merging all development versions of a code base several times a day. Trunk-based development has several benefits, such as:

It reduces the complexity and conflicts of merging long-lived branches

It improves the quality and consistency of the code by enforcing frequent testing and validation

It accelerates the delivery and deployment of new functionality by minimizing the transaction cost and risk

It fosters a culture of collaboration and transparency among developers

by Latosha at Sep 06, 2024, 12:00 PM

Limited Time Offer

25%

Off

Get Premium SAFe-DevOps Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Devora

2 months ago

I'm with Rosalind on this one. Option C is the way to go. All teams working in one trunk, that's the essence of trunk-based development. Easy peasy.

upvoted 0 times

Leila

28 days ago

Exactly, it promotes collaboration and ensures a smoother development process.

upvoted 0 times

...

Vallie

1 months ago

That way we can avoid integration issues and conflicts.

upvoted 0 times

...

William

1 months ago

It makes sense to have all teams committing their code into one trunk.

upvoted 0 times

...

Lauryn

1 months ago

I agree with you, option C is definitely the way to go.

upvoted 0 times

...

Adrianna

3 months ago

Ha! Looks like the exam writers are trying to trick us. 'Every team works in their own trunk'? That's just plain silly. Definitely going with Option C.

upvoted 0 times

Alex

2 months ago

I think the exam writers are trying to confuse us with that option.

upvoted 0 times

...

Aja

2 months ago

Yeah, I agree. Option D doesn't make sense at all.

upvoted 0 times

...

Joanna

2 months ago

Option C is the correct answer. All teams committing their code into one trunk.

upvoted 0 times

...

Nicolette

3 months ago

Hmm, I'm not so sure. Wouldn't Option B make more sense? Teams with similar dependencies working in one branch for the team's work? That sounds like the definition to me.

upvoted 0 times

Shawnna

1 months ago

I guess it depends on how the teams prefer to work. Both Option B and Option C could fit the definition of trunk-based development.

upvoted 0 times

...

Troy

2 months ago

That's true, Option C could also be considered trunk-based development. It's all about how the teams collaborate.

upvoted 0 times

...

Shad

2 months ago

But what about Option C? All teams committing their code into one trunk could also be trunk-based development.

upvoted 0 times

...

Erinn

2 months ago

I think Option B is correct. It does make sense for teams with similar dependencies to work in one branch.

upvoted 0 times

...

Laura

3 months ago

I think every team works in their own trunk, to have more control over their code changes.

upvoted 0 times

...

Lauran

3 months ago

I think it's all teams committing their code into one trunk, to avoid integration issues.

upvoted 0 times

...

Rosalind

3 months ago

Option C looks like the correct answer to me. All teams committing their code into one trunk - that's trunk-based development, right?

upvoted 0 times

Lai

2 months ago

That's right. It helps to ensure continuous integration and avoid merge conflicts.

upvoted 0 times

...

Lettie

2 months ago

Yes, you are correct. Trunk-based development involves all teams committing their code into one trunk.

upvoted 0 times

...

Tamesha

3 months ago

I disagree, I believe it's when teams with similar dependencies create one single branch for their work.

upvoted 0 times

...

Ronnie

3 months ago

I think trunk-based development is when each developer maintains a separate branch.

upvoted 0 times

...