Examkin

Soru

Zorluk: ZorAutomating Continuous Deployment Pipelines and Release Strategies

A financial software firm uses Google Cloud Deploy to automate releases across multiple staging and production Kubernetes clusters. To meet strict regulatory auditing standards, all deployment target definitions and pipeline release manifests must be immutably tracked and automatically applied without manual interventions. However, an operator recently modified target cluster endpoints directly using the gcloud CLI to resolve an emergency outage, causing subsequent automated pipeline runs to fail due to state inconsistency. Which architectural practice should the Cloud Architect implement to eliminate configuration drift and ensure compliant pipeline provisioning?

  1. Define Cloud Deploy pipelines and targets declaratively in version-controlled YAML manifests managed by Terraform, applying changes exclusively through an automated CI/CD pipeline while restricting direct write IAM permissions.Cevap
  2. B
    Allow developers to run imperative gcloud deploy update commands during emergencies, relying on post-incident manual sync procedures to update target configurations.
  3. C
    Grant the deployment pipeline runner service account the Owner primitive IAM role at the project level to automatically overwrite any conflicting manual changes during execution.
  4. D
    Maintain deployment target state files on local unversioned disk storage attached to build worker nodes to reduce provisioning latency.

Cevap

Define Cloud Deploy pipelines and target resources declaratively using version-controlled manifests managed via Infrastructure as Code (Terraform) in an automated pipeline, revoking manual write permissions.
Managing Cloud Deploy pipelines and targets declaratively through version-controlled Infrastructure as Code (such as Terraform) ensures all infrastructure changes are peer-reviewed, reproducible, and auditable. Revoking direct write access from human operators prevents imperative CLI drift and maintains continuous deployment reliability.

Adım Adım Çözüm

1
Analyze the root cause of pipeline failures
Identified that imperative manual updates using gcloud created configuration drift between the environment state and the automated release definitions.
Manual modifications bypass source control and break automated deployment synchronization.
2
Establish declarative Infrastructure as Code governance
Define all Cloud Deploy delivery pipelines and target resources in version-controlled configuration files managed by Terraform.
Declarative manifests stored in version control serve as the single source of truth for deployment infrastructure.
3
Enforce least privilege access controls on infrastructure modification
Restrict user IAM roles to prevent direct write operations on Cloud Deploy targets and restrict target management to automated service accounts.
Prevents unauthorized or out-of-band imperative CLI changes, guaranteeing audit compliance and pipeline stability.

Anahtar Kavram

Continuous Deployment Infrastructure Automation and Drift Prevention
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Automating Continuous Deployment Pipelines and Release Strategies