You store source in Cloud Source Repositories and need managed CI that builds/tests on every commit with minimal ops. Which method should you use?
Choose an answer
Tap an option to check your answer.
Correct answer: Use Cloud Build with a trigger on each source commit..
Why this is the answer
Cloud Build is Google Cloud's fully managed CI/CD platform, designed to integrate seamlessly with Cloud Source Repositories. By configuring a trigger on each commit, Cloud Build automatically executes your defined build steps (e.g., compile, test, deploy) without requiring you to manage any underlying infrastructure. This fulfills the requirement for managed CI with minimal operational overhead. Jenkins from the Marketplace or an open-source CI tool on a Compute Engine VM would require significant operational effort for setup, maintenance, and scaling, contradicting the "minimal ops" requirement. While a Pub/Sub trigger could initiate a build, Cloud Build offers a more direct and integrated solution for source-to-build workflows, making the App Engine service an unnecessary intermediary for this specific use case.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed