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 260 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 260
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 after the change advisory board approves it.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
by closer89 at April 25, 2023, 8:57 p.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
wanrltw
1 year ago
Selected Answer: D
It's D
upvoted 1 times
...
kapara
1 year, 1 month ago
I don't get it why everybody here said D? IMHO Option D is FALSE bc - Creating feature branches for groups of developers and waiting for a change advisory board's approval can slow down the development process and might not align with the principles of agile and continuous delivery.
upvoted 1 times
wanrltw
1 year ago
As they say, better safe than sorry. When you rush, you're more prone to make a mistake and it often takes more time to fix a mistake than to prevent it. Also, check out the 4-eyes principle.
upvoted 1 times
...
...
__rajan__
1 year, 3 months ago
Selected Answer: D
D is correct.
upvoted 1 times
...
purushi
1 year, 5 months ago
Selected Answer: D
The defacto SCM process is described in option D. Advisory board approves it means approving the PR raised by developer before merging into develop/master branch.
upvoted 1 times
...
zanhsieh
1 year, 7 months ago
Selected Answer: B
B. Put all commits inside a single repo would place lots of burden on branching and commit history. This not only makes checkout slower but also hard to manage - think about a small-mid size team (10 developers) creating 200 commits per day, roughly equals to 156,000 for 3 months. The maintainers of a repo would have a hard time to chase down and merge 156,000 commits. Not to mention the repo permission management would be a nightmare if the repo extends to enterprise level (200 - 500 developers / SRE / qa / SA) .Forking repo as opt B would be a better choice. Each developer deals with his fork. PR merge and squash once ready. In fact, all famous OSS software, such as Kubernetes, Grafana, Prometheus, etc., use this approach.
upvoted 1 times
...
Writer
1 year, 8 months ago
Selected Answer: D
Use a centralized repository. A centralized repository is a single location where all of your team's code is stored. This makes it easy for everyone to access the latest code, and it also helps to prevent conflicts. Use branches. Branches are a way to create a separate version of the code for development purposes. This allows developers to work on new features or bug fixes without affecting the main branch of the code.
upvoted 2 times
...
closer89
1 year, 8 months ago
Selected Answer: D
You are a developer at a large organization
upvoted 2 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