An e-commerce enterprise is reviewing its Google Cloud architecture to eliminate technical debt accumulated during a rapid cloud migration. The audit identified two core issues: simple stateless HTTP microservices are running on a custom Google Kubernetes Engine (GKE) cluster requiring heavy administrative maintenance, and a single-region relational database is running on Cloud Spanner, causing excessive operational cost. Which TWO architectural refactoring decisions directly mitigate this technical debt? (Select TWO answers)
- Migrate the stateless HTTP microservices to Cloud Run to remove Kubernetes cluster management overhead.Answer
- Migrate the single-region relational database to Cloud SQL to reduce unnecessary cost and operational complexity.Answer
- CAssign primitive Owner roles to application service accounts to simplify identity and access management permissions.
- DStore Infrastructure as Code state files on local administrator workstations to avoid configuring remote backend storage.
Answer
Migrate the stateless HTTP microservices to Cloud Run to remove Kubernetes cluster management overhead, and migrate the single-region relational database to Cloud SQL to reduce unnecessary cost and operational complexity.
Refactoring stateless microservices from self-managed GKE clusters to Cloud Run eliminates ongoing cluster maintenance overhead. Replacing Cloud Spanner with Cloud SQL for single-region relational database needs aligns infrastructure sizing with actual requirements and significantly lowers operational expenses.
Step-by-Step Solution
Key Concept
Technical Debt Mitigation via Serverless and Right-Sized Cloud Resources