Examkin

Soru

Zorluk: OrtaAutomating Continuous Deployment Pipelines and Release Strategies

An e-commerce organization uses Cloud Build and Cloud Deploy to execute automated continuous deployment pipelines for microservices backed by Cloud SQL. The cloud architecture team must secure the release pipeline, prevent state corruption during automated Infrastructure as Code (IaC) updates, and ensure application availability during database-backed release rollouts. Which TWO architectural and operational actions should the team implement?

  1. Configure Cloud Build to impersonate fine-grained target service accounts using dedicated IAM roles, and store Terraform state in a Cloud Storage backend with object versioning and state locking enabled.Cevap
  2. B
    Assign the primitive Owner role to the Cloud Build service account across all target Google Cloud projects to streamline resource deployment without permission failures.
  3. C
    Grant the Service Account Admin role directly to the Cloud Deploy runner service account so it can manage runtime identities across GKE clusters.
  4. Ensure database schema updates are backward-compatible with previous application code versions before executing progressive release rollouts.Cevap
  5. E
    Store Terraform state files in the local Cloud Build ephemeral workspace directory during pipeline runs to maximize pipeline execution velocity.

Cevap

The correct recommendations are configuring Cloud Build to use least-privilege service account impersonation with a versioned Cloud Storage backend for Terraform state, and enforcing backward-compatible database schema changes before progressive application deployments.
Automating release pipelines requires balancing infrastructure state safety, security, and application continuity. Impersonating targeted service accounts with fine-grained roles alongside a Cloud Storage backend featuring versioning and locking ensures secure, conflict-free IaC management. Additionally, designing database migrations to be backward-compatible protects active traffic during progressive release rollouts.

Adım Adım Çözüm

1
Secure the pipeline execution identity
Cloud Build operates using minimal required permissions via service account impersonation rather than broad administrative privileges.
Adhering to least privilege reduces blast radius in automated continuous deployment environments.
2
Configure remote IaC state management
Terraform state is stored centrally in Cloud Storage with object versioning and state locking.
Prevents state file corruption and race conditions when infrastructure updates are triggered concurrently.
3
Structure release strategies for zero-downtime application rollouts
Database schemas are updated in a backward-compatible manner prior to rolling out new application binaries.
Ensures that running application instances continue functioning while traffic is shifted during canary or progressive deployment phases.

Anahtar Kavram

Automating Secure CI/CD Pipelines and Zero-Downtime Release Strategies
Bu soruyu puanla

Konular

Automating Continuous Deployment Pipelines and Release Strategies