Answer-first summary for fast verification
Answer: Absence of a Trigger in Cloud Build for automatic deployment.
Option C is correct because creating a trigger in Cloud Build is essential for automatically building and deploying code pushed to the Cloud Source Repository. Option A is incorrect as the GKE API is enabled by the Cloud Build service prior to deployment. Option B is also incorrect since the Kubernetes Engine Developer permissions are adequate for Cloud Build to deploy to GKE. Option D is incorrect because Cloud Source Repository does not require additional permissions to work with Cloud Build. For more details, refer to the Google Cloud documentation on automating builds with 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). Despite the Cloud Build Service account having 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 enabled.
B
Insufficient permissions granted to the Kubernetes Engine Developer role.
C
Absence of a Trigger in Cloud Build for automatic deployment.
D
Cloud Source Repositories lacks the necessary permissions to utilize Cloud Build.