Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail organization runs a self-hosted MySQL database on on-premises virtual machines and plans to migrate it to Google Cloud. Leadership has established the following goals and constraints for the migration:
Which migration strategy and Google Cloud service should the organization choose?
Rehosting, commonly known as a lift-and-shift migration, involves moving an existing workload from an on-premises environment to cloud infrastructure—such as Compute Engine virtual machines (VMs)—with minimal or no modifications to the underlying architecture. In this Infrastructure as a Service (IaaS) model, Google Cloud manages the physical data center, networking, and virtualization layers, while the customer remains responsible for the guest operating system and database software.
While rehosting preserves the existing MySQL engine and avoids rewriting application queries, it fails to satisfy the core requirement of transitioning to a fully managed relational database service. Because the database remains self-hosted on Compute Engine VMs, the organization's IT team must still manually configure and maintain database patching, backups, replication, and high-availability failover.
This approach would be the right choice if the organization needed to evacuate an on-premises data center as quickly as possible without changing any operational processes, or if the database relied on custom operating system configurations, specialized third-party software dependencies, or legacy configurations where refactoring or replatforming before migration was not feasible.
Organizations sometimes use rehosting as the first step in a phased migration strategy to exit physical data centers rapidly, and then subsequently replatform the self-hosted database to Cloud SQL in a second phase to reduce long-term operational overhead.
Refactoring (often called move and improve) involves modifying and optimizing applications to take advantage of cloud-native capabilities without completely rewriting their core functionality. Google Kubernetes Engine (GKE) Autopilot is a managed container orchestration service where Google Cloud provisions and manages the underlying cluster infrastructure, including compute nodes, scaling, and baseline security configurations for containerized workloads.
Although GKE Autopilot is a managed compute environment for containers, it is not a managed relational database service. Running a MySQL database inside containers on GKE still leaves the organization responsible for managing the database engine itself, including MySQL patching, schema backups, point-in-time recovery, and database replication. Furthermore, refactoring a database into microservices violates the constraint to avoid rewriting application queries or untangling dependencies prior to migration.
This option would be the right choice if the organization wanted to modernize its application frontend virtual machines or monolithic business logic into scalable, containerized microservices with automated cluster management, rather than migrating a backend relational database.
In a multi-tier cloud migration, organizations frequently mix and match migration approaches across a single application stack—for example, refactoring the frontend virtual machines to run on GKE Autopilot while simultaneously replatforming the backend MySQL database to Cloud SQL.
Replatforming (often referred to as move and tinker) involves migrating a workload to the cloud while introducing targeted platform optimizations—such as moving from a self-managed database to a fully managed database service—without changing the core application architecture. Cloud SQL for MySQL is Google Cloud's fully managed relational database service that automates routine database administration tasks while maintaining full compatibility with standard MySQL engines.

Compared to lifting and shifting onto virtual machines—which leaves the burden of database administration on internal IT teams—or refactoring and rebuilding—which demand costly and time-consuming application code changes—replatforming to Cloud SQL for MySQL delivers immediate operational relief and cloud-native reliability with minimal migration risk and zero application refactoring.
Rebuilding (sometimes called remove and replace or rip and replace) is an intensive modernization strategy that involves discarding an existing software component or database and rewriting the workload from scratch to use a completely different cloud-native architecture. Cloud Bigtable is Google Cloud's fully managed, wide-column NoSQL database service designed for massive analytical and operational workloads requiring high throughput and low latency.
This option directly conflicts with two stated requirements: retaining the current MySQL database engine and schema, and migrating to a relational database service. Moving from MySQL to Cloud Bigtable is a heterogeneous migration from a relational (SQL) database to a non-relational (NoSQL) key-value and wide-column store, which would force developers to completely redesign the data schema and rewrite all application queries.
This strategy would be appropriate if the legacy database technology had reached its end of life, required uneconomical third-party licensing fees, or no longer satisfied business requirements because the workload had evolved into a massive-scale, high-throughput NoSQL time-series or analytical workload that required Cloud Bigtable.
When an existing relational database still meets functional business needs and uses a modern, supported engine like MySQL, rebuilding introduces unnecessary project risk and delay compared to replatforming directly to Cloud SQL.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated