Answer-first summary for fast verification
Answer: A trigger in Cloud Build that automates the build process upon code push was not established.
Option A is incorrect because the Kubernetes Engine Developer permission is sufficient for Cloud Build to deploy to GKE. Option B is incorrect as the GKE API is automatically enabled by the Cloud Build service when needed for deployment. Option C is also incorrect because Cloud Source Repository does not require additional permissions to work with Cloud Build. Option D is correct because for Cloud Build to automatically build and deploy code pushed to Cloud Source Repository, specific triggers must be created to initiate the process. Reference: [Cloud Build Documentation](https://cloud.google.com/build/docs/automating-builds/create-manage-triggers).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your team is developing an automated CI/CD pipeline within a development project. Utilizing Cloud Source Repository for code versioning and Cloud Build for building and deploying the application to Google Kubernetes Engine (GKE), you've assigned the Cloud Build Service account the Kubernetes Engine Developer permissions. However, after a developer pushes code to the Cloud Source Repository, the application fails to deploy to GKE. What could be the underlying issue?
A
The Kubernetes Engine Developer permissions are inadequate for the deployment process.
B
The GKE API has not been activated for the project.
C
Cloud Source Repositories lacks the necessary permissions to interact with Cloud Build.
D
A trigger in Cloud Build that automates the build process upon code push was not established.