Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Google Exam Professional Cloud Developer Topic 11 Question 97 Discussion

Actual exam question for Google's Professional Cloud Developer exam

Question #: 97
Topic #: 11

[All Professional Cloud Developer Questions]

You are a developer at a large organization. Your team uses Git for source code management (SCM). You want to ensure that your team follows Google-recommended best practices to manage code to drive higher rates of software delivery. Which SCM process should your team use?

AEach group of developers creates a feature branch from the main branch for their work, commits their changes to their branch, and merges their code into the main branch before each major release.

BEach developer commits their code to the main branch before each product release, conducts testing, and rolls back if integration issues are detected.

CEach group of developers copies the repository, commits their changes to their repository, and merges their code into the main repository before each product release.

DEach developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch after peer review.

Show Suggested Answer

Suggested Answer: D

by Michel at Oct 19, 2024, 06:42 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Glory

2 months ago

Haha, option A reminds me of the old days when we used to roll back code changes every other release. Those were the fun times!

upvoted 0 times

Remona

1 months ago

Yeah, option A definitely brings back memories of rolling back code changes.

upvoted 0 times

...

Genevieve

2 months ago

I think option D is more in line with Google-recommended best practices.

upvoted 0 times

...

Carlton

2 months ago

Option A sounds like a blast from the past!

upvoted 0 times

...

...

France

3 months ago

Option D sounds like the most structured and controlled approach. I like how it involves a change advisory board to approve the code merge.

upvoted 0 times

...

Linette

3 months ago

I think option C is the way to go. Committing to the main branch daily keeps the integration issues at bay.

upvoted 0 times

Lou

2 months ago

True, but with option D, there's an approval process before merging code into the main branch.

upvoted 0 times

...

Timothy

2 months ago

But with option C, each developer has their own branch to work on, which can be more organized.

upvoted 0 times

...

Jacquelyne

2 months ago

I think option D might be better, creating a feature branch for each group of developers.

upvoted 0 times

...

Teri

2 months ago

I agree, committing to the main branch daily definitely helps with integration.

upvoted 0 times

...

...

Elvera

3 months ago

I agree with Thurman. Option D ensures that changes are approved before integration, reducing the risk of breaking the main branch.

upvoted 0 times

...

Thurman

3 months ago

I think option D is the best choice because it allows for code review before merging into the main branch.

upvoted 0 times

...