Examkin

Soru

Zorluk: OrtaManaging Technology Debt and Legacy Cloud Migrations

A regional bank is migrating a legacy batch transaction processing monolith to Google Cloud. Over years of operation, the application has accumulated significant technical debt: deployments frequently fail due to breaking database schema modifications, infrastructure is modified manually in production causing configuration drift, and application services rely heavily on local disk state.

As the Cloud Architect leading this modernization initiative, which TWO architectural strategies should you implement to eliminate this technical debt and establish a reliable cloud deployment pipeline? (Select TWO.)

  1. Adopt the expand-contract (parallel change) pattern for all database schema modifications to maintain backward compatibility during application deployments.Cevap
  2. Define all GCP infrastructure using Infrastructure as Code (IaC) templates enforced via CI/CD pipelines while revoking manual resource modification access.Cevap
  3. C
    Provision a multi-zone Google Kubernetes Engine (GKE) cluster to host simple stateless web components to streamline environment orchestration overhead.
  4. D
    Grant primitive Editor IAM roles to the automated migration service accounts to streamline resource provisioning across all landing zone projects.

Cevap

The correct strategies are adopting the expand-contract pattern for database schema migrations and defining infrastructure as code enforced via automated CI/CD pipelines while preventing manual console modifications.
Addressing technical debt during legacy cloud migrations requires decoupling database schema changes from application deployments and eliminating infrastructure configuration drift. The expand-contract pattern introduces database changes in distinct phases (expand, transition, contract), guaranteeing backward compatibility for active application instances. Simultaneously, managing all GCP infrastructure declaratively via Infrastructure as Code (IaC) pipelines and revoking manual mutation rights prevents drift between repository state and runtime environments.

Adım Adım Çözüm

1
Analyze the technical debt causes described in the migration scenario.
Identified two core issues: database deployment coupling causing breaking changes, and manual production modifications causing infrastructure drift.
Technical debt remediation requires targeted patterns that explicitly resolve root causes.
2
Evaluate database refactoring techniques for legacy zero-downtime migrations.
The expand-contract (parallel change) pattern allows old and new code versions to run concurrently against the database schema without breaking functionality.
Decoupling application code releases from database schema changes prevents deployment failures.
3
Evaluate infrastructure governance and configuration drift mitigation.
Declarative IaC (e.g., Terraform) managed exclusively through CI/CD pipelines eliminates manual configuration drift.
Restricting manual changes ensures the defined IaC state always matches actual cloud infrastructure.

Anahtar Kavram

Legacy Migration Technical Debt Remediation via IaC and Database Expand-Contract Pattern
Bu soruyu puanla

Konular

Managing Technology Debt and Legacy Cloud Migrations

Bu konudan daha fazla soru