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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Developer Exam - Topic 13 Question 109 Discussion

You are using Cloud Build to create a new Docker image on each source code commit to a Cloud Source Repositoties repository. Your application is built on every commit to the master branch. You want to release specific commits made to the master branch in an automated method. What should you do?
C) Create a build trigger on a Git branch name pattern. Use a Git branch naming convention for new releases.
A) Manually trigger the build for new releases.
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
D) Commit your source code to a second Cloud Source Repositories repository with a second Cloud Build trigger. Use this repository for new releases only.

Google Professional Cloud Developer Exam - Topic 13 Question 109 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 109
Topic #: 13
[All Professional Cloud Developer Questions]

You are using Cloud Build to create a new Docker image on each source code commit to a Cloud Source Repositoties repository. Your application is built on every commit to the master branch. You want to release specific commits made to the master branch in an automated method. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Soledad at Jul 13, 2025, 01:16 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
William
9 months ago
B is definitely the best practice for automated releases.
upvoted 0 times
...
Cherri
9 months ago
Wait, D? That sounds like overkill for just releases!
upvoted 0 times
...
Jenelle
9 months ago
I disagree, A seems simpler for small teams.
upvoted 0 times
...
Weldon
9 months ago
C could work, but it feels a bit messy to manage branches.
upvoted 0 times
...
Germaine
9 months ago
B is the way to go! Git tags are perfect for releases.
upvoted 0 times
...
Dyan
10 months ago
I recall something about using a second repository, but that seems overly complicated for just managing releases.
upvoted 0 times
...
Layla
10 months ago
I practiced a similar question where we had to choose between branches and tags. I think tags are better for versioning releases.
upvoted 0 times
...
Hillary
10 months ago
I'm not entirely sure, but I feel like manually triggering builds isn't efficient for releases.
upvoted 0 times
...
Kerry
10 months ago
I remember we discussed build triggers in class, and I think using a Git tag pattern makes sense for automating releases.
upvoted 0 times
...
Nan
11 months ago
I'm pretty confident that option B is the way to go. Using Git tags to trigger the build for new releases is a common and reliable approach. Seems like the most elegant solution here.
upvoted 0 times
...
Tiara
11 months ago
Option D seems a bit overkill to me. Why create a whole new repository just for releases? I feel like the tag or branch pattern options are more straightforward and efficient.
upvoted 0 times
...
Ettie
11 months ago
Hmm, I'm a bit confused on the difference between using a Git tag pattern versus a Git branch name pattern. I'll have to think through the pros and cons of each approach.
upvoted 0 times
...
Chantay
11 months ago
I think the key here is to automate the release process, so I'm leaning towards option B. Creating a build trigger on a Git tag pattern seems like a good way to handle new releases.
upvoted 0 times
...
Bong
1 year ago
D sounds like a lot of unnecessary overhead. B is the simplest and most straightforward solution.
upvoted 0 times
Essie
12 months ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
Brice
12 months ago
I think B is the best option.
upvoted 0 times
...
...
Nenita
1 year ago
Haha, manually triggering builds? What is this, the Stone Age? B is definitely the way to go.
upvoted 0 times
Walton
11 months ago
Haha, manually triggering builds? What is this, the Stone Age?
upvoted 0 times
...
Angella
12 months ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
Jettie
1 year ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
Bette
1 year ago
A) Manually trigger the build for new releases.
upvoted 0 times
...
Michel
1 year ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
...
Vallie
1 year ago
I agree with Evan, using a Git tag convention for new releases sounds like a good idea.
upvoted 0 times
...
Michael
1 year ago
I agree, B is the correct answer. Automating the release process with Git tags is efficient and reduces manual effort.
upvoted 0 times
...
Evan
1 year ago
I disagree, I believe we should create a build trigger on a Git tag pattern for new releases.
upvoted 0 times
...
Frederic
1 year ago
B seems like the way to go - using a Git tag for new releases is a common and reliable approach.
upvoted 0 times
Erick
1 year ago
That's a good point. Using Git tags for new releases is a reliable method.
upvoted 0 times
...
Kerry
1 year ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
Kenneth
1 year ago
That's a good point. Using Git tags for new releases is a reliable method.
upvoted 0 times
...
Reuben
1 year ago
B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.
upvoted 0 times
...
...
Felix
1 year ago
I think we should manually trigger the build for new releases.
upvoted 0 times
...

Save Cancel