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 company is planning to migrate an existing on-premises application stack to Google Cloud. The leadership team has defined the following technical and operational goals for the migration:
Which cloud migration pathway should the company select?
Replatforming, often referred to as lift and optimize, is a cloud migration approach where an organization moves existing workloads to the cloud while making targeted optimizations to take advantage of managed cloud services. Rather than simply copying virtual machines as-is or completely rewriting the underlying application logic, replatforming upgrades the runtime environment or backing infrastructure—such as migrating a self-managed database to a managed database service or containerizing legacy virtual machines.
Compared to a simple rehost (lift and shift) approach—which leaves workloads unoptimized on standard virtual machines—replatforming unlocks the operational efficiencies of Google Cloud. At the same time, it avoids the heavy engineering investment and extended delays required by rebuild or deep re-architect strategies, striking the ideal balance for the company's stated goals.
A rebuild migration—frequently called remove and replace or rip and replace—involves completely decommissioning an existing legacy application and redesigning and rewriting it from scratch as a fully cloud-optimized workload. This approach discards the old codebase and architecture entirely to construct a brand-new solution tailored specifically for Google Cloud.
The company wants to migrate its existing database to Cloud SQL and convert its current virtual machines into containers on Google Kubernetes Engine (GKE) without rewriting the core application source code from scratch. A rebuild strategy directly contradicts this constraint because it requires decommissioning the existing application and writing a completely new codebase.
The existing on-premises application no longer satisfied current business requirements, relied on end-of-life technology that could not be supported in Google Cloud, or carried such severe technical debt that maintaining or migrating the existing codebase was no longer economical.
A repurchase migration occurs when an organization retires a self-hosted or purchased on-premises workload and replaces it by moving to a cloud-hosted Software-as-a-Service (SaaS) equivalent. Instead of migrating servers, databases, or custom application code to cloud infrastructure, the business transitions to a subscription-based software product managed entirely by a cloud provider or third-party vendor.
The company is actively migrating its own application stack—specifically moving its MySQL data into Cloud SQL and containerizing its virtual machines to run on Google Kubernetes Engine (GKE). A repurchase strategy would abandon the company's existing application infrastructure altogether in favor of buying a turnkey SaaS product, which does not involve managing databases in Cloud SQL or container clusters in GKE.
The company wanted to decommission an on-premises collaboration software and local storage system and transition its workforce directly to a fully managed SaaS solution like Google Workspace.
Rehosting, commonly known as lift and shift, is a migration strategy that moves workloads from a source environment (such as an on-premises data center) to a target cloud environment with minimal or no modifications. The only changes made to the workload are the baseline configurations strictly necessary for the application to function in the new infrastructure, such as deploying existing virtual machines directly onto Compute Engine or Google Cloud VMware Engine.
In this scenario, the company explicitly wants to modernize its operational model by moving from a self-hosted MySQL database to Cloud SQL and converting its virtual machines into containers on Google Kubernetes Engine (GKE). A rehost approach would simply move the self-hosted MySQL server onto a cloud-based virtual machine and keep the application running on standard VMs, failing to utilize managed database services or container orchestration platforms.
The organization needed to evacuate its on-premises data center as quickly as possible before a hardware lease expired, was migrating commercial off-the-shelf software that could not be altered, or had no immediate business need to adopt managed services like Cloud SQL or GKE.
Organizations often use rehost (lift and shift) as the first step in a phased migration strategy. Once the workloads are running on Compute Engine in Google Cloud, teams can later replatform or refactor those components to integrate more deeply with cloud-native services.
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