Answer-first summary for fast verification
Answer: 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., GitHub for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Functions.
Options B and D are correct because they utilize Cloud Functions and Cloud Run, which are serverless products, and leverage Cloud Build for CI/CD, reducing overhead. Options A, C, and E are incorrect due to reasons such as the use of non-serverless products (Compute Engine), the inability of Cloud Source Repositories to act as a CD tool, and the higher overhead associated with managing Jenkins on GCP compared to Cloud Build. References: [Cloud Build Overview](https://cloud.google.com/build/docs/overview), [Automating Builds with GitHub App Triggers](https://cloud.google.com/build/docs/automating-builds/create-github-app-triggers), [Jenkins on Kubernetes Engine Tutorial](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 for deploying applications to serverless infrastructure on Google Cloud Platform. Which two options would enable you to accomplish this task with minimal overhead?
A
GitHub for source code management, Cloud Build as a CI tool, and Jenkins as a CD tool for deploying to Cloud Run.
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 Cloud Source Repository as a CD tool for deploying to Cloud Functions.
D
GitHub for source code management, Cloud Build as a CI tool, and Cloud Build as a CD tool for deploying to Cloud Functions.
E
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.
No comments yet.