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

Google Exam Professional Cloud Developer 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

Contribute your Thoughts:

Glory
2 months ago
I'm just here for the free coffee and donuts. Someone else can worry about the build process.
upvoted 0 times
...
Stephanie
2 months ago
Using Pub/Sub and App Engine? That's a bit overkill for a simple build process.
upvoted 0 times
Maryln
27 days 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
30 days ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
upvoted 0 times
...
Rikki
1 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Malcolm
2 months ago
A Compute Engine VM? That's just asking for more work. I'll pass on that one.
upvoted 0 times
Kayleigh
8 days 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
9 days ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
upvoted 0 times
...
Glory
1 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Nakisha
2 months ago
Jenkins is a great tool, but managing the infrastructure can be a pain. I'd skip that.
upvoted 0 times
Dorothy
1 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
Antione
1 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
1 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
1 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
Helga
1 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Chuck
3 months ago
Cloud Build seems like the simplest and most managed option. I'd go with that.
upvoted 0 times
Teddy
1 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
2 months ago
That sounds like the best choice for minimal operations overhead.
upvoted 0 times
...
Clarinda
2 months ago
A) Use Cloud Build with a trigger configured for each source code commit.
upvoted 0 times
...
...
Laquanda
3 months ago
I'm not sure, I think using Jenkins deployed via GCP Marketplace could also be a good option.
upvoted 0 times
...
Levi
3 months ago
I agree with Halina, Cloud Build is managed and has minimal operations overhead.
upvoted 0 times
...
Halina
4 months ago
I think we should use Cloud Build with a trigger for each source code commit.
upvoted 0 times
...

Save Cancel