An organization is establishing an automated, secure continuous integration and continuous delivery (CI/CD) pipeline on Google Cloud to deploy containerized applications to Google Kubernetes Engine (GKE). Arrange the following pipeline execution stages in the correct sequence from developer code commit to final production verification.
- 1Cloud Build is triggered automatically via a repository webhook upon code commit to run unit tests.
- 2Artifact Analysis scans the container image for vulnerability CVEs before it is stored in Artifact Registry.
- 3Cloud Build executes Terraform to validate state and update GKE cluster manifests stored in a Google Cloud Storage backend.
- 4Cloud Deploy initiates a automated deployment to the staging GKE cluster and performs automated integration testing.
- 5Cloud Deploy promotes the validated release to the production GKE cluster and monitors Cloud Monitoring health metrics.
Cevap
The correct chronological sequence for the CI/CD pipeline is: 1) Trigger Cloud Build via repository webhook on code commit, 2) Perform vulnerability scanning with Artifact Analysis before pushing to Artifact Registry, 3) Validate and execute Terraform IaC manifests against GKE, 4) Deploy to staging environment via Cloud Deploy for integration testing, and 5) Promote the release to production via Cloud Deploy with Cloud Monitoring verification.
The sequence follows Google Cloud SDLC best practices: Source trigger -> Build & Security scanning -> Infrastructure/Manifest update -> Staging deployment & testing -> Production promotion & health monitoring.
Adım Adım Çözüm
Anahtar Kavram
Continuous Integration and Continuous Delivery (CI/CD) Pipeline Sequencing and Security