Answer-first summary for fast verification
Answer: GitHub for source code management, Cloud Build as a CI tool, Cloud Build as a CD tool for deploying to Cloud Functions
The correct answer is D because Cloud Functions and Cloud Run are serverless products, and using Cloud Build for CI/CD significantly reduces overhead. Cloud Build can also be triggered by code pushes to GitHub. Other options are incorrect because Compute Engine is not serverless, Cloud Source Repositories cannot serve as a CD tool, and managing Jenkins on GCP introduces more overhead than using Cloud Build. For more details, refer to the Overview of Cloud Build, Building repositories from GitHub, and Setting up Jenkins on GKE.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Imagine you're assigned to create an automated build for deploying applications to serverless infrastructure on Google Cloud Platform. Which option would enable you to accomplish this task with minimal overhead?
A
GitHub for source code management, Cloud Build as a CI tool, Jenkins as a CD tool for deploying to Cloud Run
B
Cloud Source Repository for source code management, Cloud Build as a CI tool, Cloud Build as a CD tool for deploying to Cloud Run
C
GitHub for source code management, Cloud Build as a CI tool, Cloud Source Repository as a CD tool for deploying to Cloud Functions
D
GitHub for source code management, Cloud Build as a CI tool, 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, Cloud Build as a CD tool for deploying to Compute Engine