Examkin

Soru

Zorluk: OrtaAssessing and Mitigating Technical Debt in Cloud Architectures

A global healthcare diagnostics company recently completed a rapid cloud migration of its patient telemetry monitoring platform to Google Cloud. A post-migration architecture audit revealed significant technical debt: infrastructure modifications are frequently executed directly through the GCP Console resulting in configuration drift, and application service accounts retain broad primitive Owner permissions to avoid deployment friction. Which strategy should the cloud architect recommend to mitigate this technical debt while establishing long-term governance?

  1. Import existing GCP resources into a version-controlled Infrastructure as Code state managed in Cloud Storage with object locking, replace primitive permissions with fine-grained predefined roles following least privilege, and enforce all changes through an automated CI/CD deployment pipeline.Cevap
  2. B
    Maintain primitive Owner roles on application service accounts to preserve service availability, but enforce scheduled daily automated scripts that export console configuration changes back into local text files.
  3. C
    Permit ongoing manual GCP Console adjustments for rapid incident mitigation while configuring a weekly scheduled Terraform apply pipeline from developer workstations to overwrite console changes.
  4. D
    Migrate all telemetry ingestion workloads to a multi-region Cloud Spanner database cluster and grant Service Account Admin roles to all compute instances to automate permission propagation.

Cevap

Import existing GCP resources into a version-controlled Infrastructure as Code state managed in Cloud Storage with object locking, replace primitive permissions with fine-grained predefined roles following least privilege, and enforce all changes through an automated CI/CD deployment pipeline.
The correct answer systematically addresses both security and operational debt by locking infrastructure configurations into IaC backed by centralized state storage, restricting deployment access strictly to CI/CD pipelines, and applying least-privilege IAM roles to eliminate broad administrative access.

Adım Adım Çözüm

1
Identify accumulated cloud technical debt areas
Discovered manual console modifications (configuration drift) and overly broad primitive IAM roles on application service accounts.
Technical debt assessment requires pin-pointing operational risk and security exposure in the current architecture.
2
Establish Infrastructure as Code (IaC) governance
Import resources into IaC state stored centrally in Cloud Storage with state locking and versioning, enforcing deployment strictly through automated CI/CD pipelines.
Automated pipelines eliminate manual console drift and establish auditable, reproducible deployment practices.
3
Remediate IAM security technical debt
Revoke primitive Owner roles and grant minimal, task-specific predefined or custom IAM roles.
Enforcing the principle of least privilege limits the impact of compromised service accounts and satisfies compliance requirements.

Anahtar Kavram

Assessing and Mitigating Technical Debt in Cloud Architectures
Bu soruyu puanla

Konular

Assessing and Mitigating Technical Debt in Cloud Architectures