Explanation:
The simplest and fully managed solution for continuous deployment to Cloud Run upon a source code commit is to use Cloud Run's built-in continuous deployment feature. This feature automatically handles the building and deploying process when a commit is made to the source repository, without the need for manual configuration of build steps or triggers. Option C, which suggests configuring continuous deployment of new revisions from a source repository for Cloud Run using buildpacks, directly utilizes this feature, making it the correct choice. Options A and B involve manual or self-managed solutions, which do not meet the requirement for a fully managed solution. Option D, while it uses Cloud Build, requires explicit trigger configuration, making it less simple than Option C.
Ultimate access to all questions.
How can you set up a fully managed, automated continuous deployment pipeline for a Go application in Cloud Run, triggered by commits to Cloud Source Repositories, using the simplest deployment solution?
A
Configure a cron job on your workstations to periodically run gcloud run deploy --source in the working directory.
B
Configure a Jenkins trigger to run the container build and deploy process for each source code commit to Cloud Source Repositories.
C
Configure continuous deployment of new revisions from a source repository for Cloud Run using buildpacks.
D
Use Cloud Build with a trigger configured to run the container build and deploy process for each source code commit to Cloud Source Repositories.
No comments yet.