MENU
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?
Suggested Answer: A
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
35 comments · newest first
KR
Kristofer
10 months ago
Wait, D seems overly complex for just building code.
KE
Keva
10 months ago
C sounds too complicated for this scenario.
NI
Nicholle
11 months ago
I disagree, B could work well too with Jenkins.
RI
Ricarda
11 months ago
I didn't know Cloud Build could handle triggers so easily!
LO
Lorrie
11 months ago
A is the best choice for minimal overhead!
ME
Melvin
11 months ago
I feel like the Pub/Sub option could work, but it sounds more complex than just using Cloud Build directly.
SL
Slyvia
11 months ago
I practiced a similar question, and I think using a trigger with Cloud Build is the most straightforward approach.
SE
Serina
12 months ago
I'm not entirely sure, but I think Jenkins might require more management than Cloud Build.
KI
Kizzy
12 months ago
I remember we discussed Cloud Build in class, and it seems like the best option for minimal overhead.
GL
Glenn
1 year 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.
JO
Joanne
1 year 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.
LO
Lovetta
1 year 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.
SA
Sabra
1 year 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.
GL
Glory
1 year ago
I'm just here for the free coffee and donuts. Someone else can worry about the build process.
ST
Stephanie
1 year ago
Using Pub/Sub and App Engine? That's a bit overkill for a simple build process.
MA
Maryln
1 year ago
C) Use a Compute Engine virtual machine instance with an open source continuous integration tool, configured to watch for source code commits.
KI
Kip
1 year ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
RI
Rikki
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
MA
Malcolm
1 year ago
A Compute Engine VM? That's just asking for more work. I'll pass on that one.
KA
Kayleigh
1 year 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.
TO
Tommy
1 year ago
B) Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
GL
Glory
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
NA
Nakisha
1 year ago
Jenkins is a great tool, but managing the infrastructure can be a pain. I'd skip that.
DO
Dorothy
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
AN
Antione
1 year 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.
GI
Gianna
1 year 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.
LE
Leslie
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
HE
Helga
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
CH
Chuck
1 year ago
Cloud Build seems like the simplest and most managed option. I'd go with that.
TE
Teddy
1 year 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.
TR
Tran
1 year ago
That sounds like the best choice for minimal operations overhead.
CL
Clarinda
1 year ago
A) Use Cloud Build with a trigger configured for each source code commit.
LA
Laquanda
1 year ago
I'm not sure, I think using Jenkins deployed via GCP Marketplace could also be a good option.
LE
Levi
2 years ago
I agree with Halina, Cloud Build is managed and has minimal operations overhead.
HA
Halina
2 years ago
I think we should use Cloud Build with a trigger for each source code commit.