Google Exam Professional Cloud Developer Topic 2 Question 87 Discussion

Actual exam question for Google's Professional Cloud Developer exam

Question #: 87
Topic #: 2

[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 Francesco at Jul 08, 2024, 10:07 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Herman

11 months ago

Option D is the way to go. Gotta love those fancy 'change advisory boards' - makes me feel like I'm in a corporate spy movie or something.

upvoted 0 times

...

Martin

11 months ago

Haha, Option A sounds like a recipe for disaster. Committing directly to the main branch? No testing? What could go wrong?

upvoted 0 times

Adelina

10 months ago

Yeah, Option D also sounds good. Having a feature branch for each group's work adds an extra layer of control.

upvoted 0 times

...

Mendy

10 months ago

I agree, Option C seems like a safer approach. Each developer creating their own branch for work.

upvoted 0 times

...

Jani

10 months ago

Option A does sound risky. No testing before committing to the main branch is a bad idea.

upvoted 0 times

...

Sylvia

11 months ago

I think option A is the most efficient. Committing directly to the main branch before release simplifies the process.

upvoted 0 times

...

Pura

11 months ago

I prefer option C. It allows developers to work independently and merge changes daily.

upvoted 0 times

...

Clorinda

11 months ago

I like Option C. Daily merges into the main branch keep things moving, and it's a good balance between individual work and collaboration.

upvoted 0 times

...

Jovita

11 months ago

Definitely going with Option D. Feature branches and change approvals ensure code quality and reduce integration issues.

upvoted 0 times

Adrianna

9 months ago

I agree, having a separate branch for each feature helps keep things organized.

upvoted 0 times

...

Mozell

9 months ago

It's important to get approval before merging to main to prevent any issues. Option D is the best choice.

upvoted 0 times

...

Tamra

10 months ago

Option D is the way to go. Feature branches and approvals are key for code quality.

upvoted 0 times

...

Victor

10 months ago

Yes, following best practices like feature branches can really help with software delivery.

upvoted 0 times

...

Georgene

10 months ago

I agree, it's important to have a process in place for code quality.

upvoted 0 times

...

Nichelle

10 months ago

Option D is the way to go. Feature branches and approvals are key.

upvoted 0 times

...

Della

11 months ago

Option C seems like the way to go. It's important to keep the main branch stable and have developers work on their own branches.

upvoted 0 times

Desirae

11 months ago

Yes, creating branches for each developer's work helps keep the main branch stable and allows for easier code integration.

upvoted 0 times

...

Erinn

11 months ago

I agree, option C is definitely the best practice for managing code in Git.

upvoted 0 times

...

Lorrie

12 months ago

I agree with Cecilia. Option D ensures that changes are approved before merging.

upvoted 0 times

...

Cecilia

12 months ago

I think option D is the best choice.

upvoted 0 times

...