Discuss Google Professional Cloud Developer Exam Topic 13 Question 109

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?

AManually trigger the build for new releases.

BCreate a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

CCreate a build trigger on a Git branch name pattern. Use a Git branch naming convention for new releases.

DCommit your source code to a second Cloud Source Repositories repository with a second Cloud Build trigger. Use this repository for new releases only.

Suggested Answer: C

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

31 comments · newest first

William 10 months ago

B is definitely the best practice for automated releases.

Cherri 10 months ago

Wait, D? That sounds like overkill for just releases!

Jenelle 11 months ago

I disagree, A seems simpler for small teams.

Weldon 11 months ago

C could work, but it feels a bit messy to manage branches.

Germaine 11 months ago

B is the way to go! Git tags are perfect for releases.

Dyan 11 months ago

I recall something about using a second repository, but that seems overly complicated for just managing releases.

Layla 11 months ago

I practiced a similar question where we had to choose between branches and tags. I think tags are better for versioning releases.

Hillary 12 months ago

I'm not entirely sure, but I feel like manually triggering builds isn't efficient for releases.

Kerry 12 months ago

I remember we discussed build triggers in class, and I think using a Git tag pattern makes sense for automating releases.

Nan 1 year 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.

Tiara 1 year 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.

Ettie 1 year 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.

Chantay 1 year 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.

Bong 1 year ago

D sounds like a lot of unnecessary overhead. B is the simplest and most straightforward solution.

Essie 1 year ago

↳ replying to Bong

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Brice 1 year ago

↳ replying to Bong

I think B is the best option.

Nenita 1 year ago

Haha, manually triggering builds? What is this, the Stone Age? B is definitely the way to go.

Walton 1 year ago

↳ replying to Nenita

Haha, manually triggering builds? What is this, the Stone Age?

Angella 1 year ago

↳ replying to Nenita

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Jettie 1 year ago

↳ replying to Nenita

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Bette 1 year ago

↳ replying to Nenita

A) Manually trigger the build for new releases.

Michel 1 year ago

↳ replying to Nenita

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Vallie 1 year ago

I agree with Evan, using a Git tag convention for new releases sounds like a good idea.

Michael 1 year ago

I agree, B is the correct answer. Automating the release process with Git tags is efficient and reduces manual effort.

Evan 1 year ago

I disagree, I believe we should create a build trigger on a Git tag pattern for new releases.

Frederic 1 year ago

B seems like the way to go - using a Git tag for new releases is a common and reliable approach.

Erick 1 year ago

↳ replying to Frederic

That's a good point. Using Git tags for new releases is a reliable method.

Kerry 1 year ago

↳ replying to Frederic

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Kenneth 1 year ago

↳ replying to Frederic

That's a good point. Using Git tags for new releases is a reliable method.

Reuben 1 year ago

↳ replying to Frederic

B) Create a build trigger on a Git tag pattern. Use a Git tag convention for new releases.

Felix 1 year ago

I think we should manually trigger the build for new releases.

Google Professional Cloud Developer Exam - Topic 13 Question 109 Discussion