Examkin

Question

Difficulty: MediumRelease Management and Deployment Strategies (Blue-Green, Canary, Rolling)

An enterprise supply chain platform processes high-throughput freight tracking telemetry using a microservices application deployed on Google Kubernetes Engine (GKE), backed by Cloud SQL for PostgreSQL. The development team is preparing to release a major version update that includes non-backward-compatible database schema changes. The business requires zero downtime during release and immediate rollback capabilities if application errors increase. Which TWO implementation steps must the cloud architect mandate to safely execute this release?

  1. Apply an expand-contract database migration pattern by introducing additive schema changes (new columns/tables) and maintaining dual-write support before initiating application deployment.Answer
  2. Configure GKE Native Ingress traffic splitting to incrementally route canary traffic to the new microservice revision while monitoring SLO error budgets.Answer
  3. C
    Execute a blue-green application cutover while executing a single transactional DDL script that drops and renames active database tables.
  4. D
    Provision a complete standalone duplicate GKE cluster in the target region immediately prior to deployment without requesting regional compute quota adjustments.

Answer

The cloud architect must implement an expand-contract database migration pattern to ensure backward compatibility and configure GKE Native Ingress traffic splitting to safely run a canary release.
To achieve zero downtime when database schemas change, the expand-contract (parallel change) pattern must be applied so the database supports both application versions concurrently. Paired with GKE Ingress traffic splitting (canary deployment), traffic can be gradually routed to the new release while monitoring error budgets.

Step-by-Step Solution

1
Decouple database schema deployment from application deployment using the expand-contract strategy.
Database changes become non-breaking and additive, ensuring both older and newer versions of the GKE application microservices can run concurrently against the database.
Prevents database lockouts and application failures during traffic migration.
2
Deploy the new microservice workload alongside the existing version in GKE and leverage GKE Native Ingress to manage traffic distribution.
A small percentage of traffic (canary) is shifted to the new release to validate behavior under actual production load.
Reduces blast radius and enables instant rollback by shifting traffic weight back to 0% if SLI metric regressions are detected.

Key Concept

Release Management and Deployment Strategies (Blue-Green, Canary, Rolling)
Rate this question

Topics

Release Management and Deployment Strategies (Blue-Green, Canary, Rolling)