Explanation:
The company requires a managed solution with minimal operations overhead. Cloud Build (Option A) is a fully managed CI/CD service on Google Cloud that integrates natively with Cloud Source Repositories. Configuring a trigger in Cloud Build automatically runs builds on each commit, eliminating operational tasks like server maintenance. Options B and C involve self-managed tools (Jenkins or open-source CI on Compute Engine), which require infrastructure management. Option D introduces unnecessary complexity by using Pub/Sub and App Engine for builds, whereas Cloud Build is purpose-built for this use case.
Ultimate access to all questions.
No comments yet.
Which Google Cloud solution should your company use to automatically build and test source code on each commit to a Cloud Source Repositories repository, with minimal operational overhead?
A
Use Cloud Build with a trigger configured for each source code commit.
B
Use Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source code commits.
C
Use a Compute Engine virtual machine instance with an open source continuous integration tool, configured to watch for source code commits.
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.