New Year Sale 2026! 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 7 Question 105 Discussion

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

Your company stores their source code in a Cloud Source Repositories repository. Your company wants to build and test their code on each source code commit to the repository and requires a solution that is managed and has minimal operations overhead.

Which method should they use?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://cloud.google.com/build/docs/automating-builds/create-manage-triggers#:~:text=A%20Cloud%20Build%20trigger%20automatically,changes%20that%20match%20certain%20criteria.


by Irene at Apr 04, 2025, 09:04 PM

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
Kristofer
3 months ago
Wait, D seems overly complex for just building code.
upvoted 0 times
...
Keva
3 months ago
C sounds too complicated for this scenario.
upvoted 0 times
...
Nicholle
3 months ago
I disagree, B could work well too with Jenkins.
upvoted 0 times
...
Ricarda
3 months ago
I didn't know Cloud Build could handle triggers so easily!
upvoted 0 times
...
Lorrie
4 months ago
A is the best choice for minimal overhead!
upvoted 0 times
...
Melvin
4 months ago
I feel like the Pub/Sub option could work, but it sounds more complex than just using Cloud Build directly.
upvoted 0 times
...
Slyvia
4 months ago
I practiced a similar question, and I think using a trigger with Cloud Build is the most straightforward approach.
upvoted 0 times
...
Serina
4 months ago
I'm not entirely sure, but I think Jenkins might require more management than Cloud Build.
upvoted 0 times
...
Kizzy
4 months ago
I remember we discussed Cloud Build in class, and it seems like the best option for minimal overhead.
upvoted 0 times
...
Glenn
5 months ago
I think the key here is the requirement for a "managed" solution with minimal operations overhead. That makes me lean towards either option A or option D. I'll need to dig into the details of how each of those work to decide which one is the better fit.
upvoted 0 times
...
Joanne
5 months ago
Option B with Jenkins deployed on GCP Marketplace could work, but it might have more operational overhead than the Cloud Build option. I'll need to weigh the pros and cons of each approach.
upvoted 0 times
...
Lovetta
5 months ago
Hmm, I'm a bit unsure about this one. The question mentions the need for a "managed" solution, so I'm not sure if the Compute Engine VM option (C) would be the best choice. I'll have to think this through carefully.
upvoted 0 times
...
Sabra
5 months ago
This seems like a straightforward question. I'd go with option A - Cloud Build with a trigger for each commit. It's a managed service, so it should have minimal operations overhead.
upvoted 0 times
...
Glory
10 months ago
I'm just here for the free coffee and donuts. Someone else can worry about the build process.
upvoted 0 times
...
Stephanie
10 months ago
Using Pub/Sub and App Engine? That's a bit overkill for a simple build process.
upvoted 0 times
Maryln
9 months ago
C) Use a Compute Engine virtual machine instance with an open source continuous integration tool, configured to watch for source code commits.
upvoted 0 times
...
Kip
9 months ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
upvoted 0 times
...
Rikki
9 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Malcolm
10 months ago
A Compute Engine VM? That's just asking for more work. I'll pass on that one.
upvoted 0 times
Kayleigh
8 months ago
D) Use a source code commit trigger to push a message to a Cloud Pub/Sub topic that triggers an App Engine service to build the source code.
upvoted 0 times
...
Tommy
8 months ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
upvoted 0 times
...
Glory
9 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Nakisha
10 months ago
Jenkins is a great tool, but managing the infrastructure can be a pain. I'd skip that.
upvoted 0 times
Dorothy
9 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
Antione
9 months ago
D) Use a source code commit trigger to push a message to a Cloud Pub/Sub topic that triggers an App Engine service to build the source code.
upvoted 0 times
...
Gianna
9 months ago
D) Use a source code commit trigger to push a message to a Cloud Pub/Sub topic that triggers an App Engine service to build the source code.
upvoted 0 times
...
Leslie
9 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
Helga
9 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Chuck
10 months ago
Cloud Build seems like the simplest and most managed option. I'd go with that.
upvoted 0 times
Teddy
9 months ago
D) Use a source code commit trigger to push a message to a Cloud Pub/Sub topic that triggers an App Engine service to build the source code.
upvoted 0 times
...
Tran
9 months ago
That sounds like the best choice for minimal operations overhead.
upvoted 0 times
...
Clarinda
10 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Laquanda
11 months ago
I'm not sure, I think using Jenkins deployed via GCP Marketplace could also be a good option.
upvoted 0 times
...
Levi
11 months ago
I agree with Halina, Cloud Build is managed and has minimal operations overhead.
upvoted 0 times
...
Halina
11 months ago
I think we should use Cloud Build with a trigger for each source code commit.
upvoted 0 times
...

Save Cancel