Your team develops services that run on Google Kubernetes Engine. Your team's code is stored in Cloud Source Repositories. You need to quickly identify bugs in the code before it is deployed to produc

Question

Options

• AUse Spinnaker to automate building container images from code based on Git tags.
• BUse Cloud Build to automate building container images from code based on Git tags.
• CUse Spinnaker to automate deploying container images to the production environment.
• DUse Cloud Build to automate building container images from code based on forked versions.

• A
  9% (4)
• B
  81% (35)
• C
  2% (1)
• D
  7% (3)

Explanation

Cloud Build integrates natively with Cloud Source Repositories and can be configured to automatically trigger a build pipeline - including compiling code, running unit tests, and building container images - whenever a Git tag is pushed. This provides fast, automated feedback to developers about bugs and failures before the image reaches the GKE production environment, fulfilling the requirement for efficient automation. Option A and C (Spinnaker) is a continuous delivery tool focused on deploying to environments, not on building or testing code - it does not help identify bugs early. Option D (forked versions) is not a standard CI trigger pattern and adds complexity without a clear quality-gate benefit tied to Git tags.

No community discussion yet for this question.