ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam
Go to Exam

Exam Professional Cloud Developer topic 1 question 353 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 353
Topic #: 1
[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?

  • A. Each developer commits their code to the main branch before each product release, conducts testing, and rolls back if integration issues are detected.
  • B. Each group of developers copies the repository, commits their changes to their repository, and merges their code into the main repository before each product release.
  • C. Each developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch daily.
  • D. Each 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.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
by 09bd94b at Feb. 20, 2025, 10:04 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Sandesh24
2 months ago
Selected Answer: C
Google-recommended best practices for source code management emphasize trunk-based development. In this approach, each developer works on a feature branch for their own work and merges their changes into the main branch frequently (ideally daily). This frequent integration minimizes merge conflicts, improves visibility of changes, and promotes continuous integration and delivery. • Option A: Committing directly to the main branch only before releases increases the risk of integration issues and delays feedback. • Option B: Copying the repository and merging before each product release introduces unnecessary complexity and delays integration. • Option D: Merging feature branches only before major releases can lead to large, disruptive changes and integration problems. Thus, Option C aligns best with the practice of frequent integration and continuous delivery, driving higher rates of software delivery and reducing integration risks.
upvoted 1 times
...
09bd94b
2 months, 1 week ago
Selected Answer: C
Agree with C
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago