Answer-first summary for fast verification
Answer: No Trigger was established in Cloud Build.
The correct answer is **D** because for Cloud Build to automatically initiate builds upon code pushes to Cloud Source Repository, triggers must be configured. The other options are incorrect because: The Kubernetes Engine Developer permissions are adequate for deployment tasks; Cloud Source Repository does not require additional permissions for Cloud Build operations; and the GKE API is automatically enabled by the Cloud Build service when needed for deployment. For more details, refer to the documentation on [Creating and managing build triggers](https://cloud.google.com/build/docs/automating-builds/create-manage-triggers).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
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 applications to Google Kubernetes Engine (GKE). Despite assigning the Cloud Build Service account with Kubernetes Engine Developer permissions, the application fails to deploy to GKE after a code push to the Cloud Source Repository. What could be the underlying issue?
A
The GKE API has not been activated.
B
Insufficient permissions are granted by the Kubernetes Engine Developer role.
C
Cloud Source Repositories lacks the necessary permissions to utilize Cloud Build.
D
No Trigger was established in Cloud Build.
No comments yet.