Answer-first summary for fast verification
Answer: GitHub for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Functions, Cloud Source Repository for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Run
Options D and E are incorrect because Compute Engine is not serverless, and Cloud Source Repositories cannot function as a CD tool. Managing Jenkins on GCP introduces more overhead compared to using Cloud Build. Options A and B are correct as they utilize Cloud Functions and Cloud Run, which are serverless, and Cloud Build for CI/CD, minimizing overhead. Cloud Build can also be triggered by code pushes to GitHub. References: [Cloud Build Overview](https://cloud.google.com/build/docs/overview), [Automating Builds with GitHub](https://cloud.google.com/build/docs/automating-builds/create-github-app-triggers), [Jenkins on Kubernetes Engine](https://cloud.google.com/architecture/jenkins-on-kubernetes-engine-tutorial).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are tasked with creating an automated build process for deploying applications to serverless infrastructure on Google Cloud Platform. Which two options would allow you to accomplish this with minimal overhead?
A
GitHub for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Functions
B
Cloud Source Repository for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Run
C
GitHub for source code management, Cloud Build as a CI tool, and Jenkins as a CD tool for deploying to Cloud Run
D
Cloud Source Repository for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Compute Engine
E
GitHub for source code management, Cloud Build as a CI tool, and Cloud Source Repository as a CD tool for deploying to Cloud Functions
No comments yet.