Answer-first summary for fast verification
Answer: No trigger has been set up in Cloud Build to initiate the deployment process.
The correct answer is **D** because for Cloud Build to automatically build and deploy code pushed to the Cloud Source Repository, triggers must be established. The other options are incorrect because: The Kubernetes Engine Developer permissions are adequate for deployments to GKE; Cloud Source Repository does not require additional permissions to work with Cloud Build; and the GKE API is automatically enabled by Cloud Build when necessary 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 interact with Cloud Build.
D
No trigger has been set up in Cloud Build to initiate the deployment process.
No comments yet.