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.
An organization is assessing its on-premises inventory to build a Google Cloud migration plan and identifies two specific workloads:
Which strategic migration decisions should the organization make for these workloads?
This option confuses foundational migration terms by misapplying both retire and retain. Moving from an on-premises application to a cloud-hosted Software-as-a-Service (SaaS) equivalent is actually a repurchase strategy, whereas retiring a workload means decommissioning it completely because its capabilities are no longer required. Similarly, selecting a workload as a first-mover means actively migrating it to Google Cloud in the initial batch, which is the opposite of retaining it in the source environment.
Moving to a SaaS platform would be the right choice if the organization wanted to repurchase a standard collaboration or CRM tool rather than maintain it on-premises. Selecting a workload as a first-mover would be appropriate if the workload were actively used, non-mission-critical, loosely coupled, and representative of common development patterns.
A rebuild migration (sometimes referred to as remove and replace or rip and replace) involves decommissioning an existing legacy application and completely redesigning and rewriting it from scratch as a cloud-optimized workload on Google Cloud. Combining a full rebuild with permanently retaining the original workloads on-premises means running duplicate systems across both environments indefinitely.
Rebuilding from scratch would be the right choice if an application were still essential to the business, had no existing replacement, and was too outdated or costly to maintain or migrate—provided the legacy version was decommissioned after cutover rather than retained permanently.
During the assessment phase of a cloud migration, organizations evaluate every workload—an independent application, service, or computing task that delivers business value—to determine its optimal path forward. Not every workload in an on-premises inventory should be moved to the cloud. Retain means keeping a workload in its current source environment (either temporarily or permanently), while retire means decommissioning and shutting down a workload that is no longer needed.

Making strategic retain and retire decisions early in the assessment phase shapes the entire migration plan and timeline. Compared to forcing every legacy system into a lift-and-shift or refactoring batch, filtering out workloads that cannot move or should not exist allows engineering teams to focus their resources on workloads that deliver genuine business value in Google Cloud.
Rehost (commonly referred to as lift and shift) and refactor (often called move and improve) are active migration pathways used to move workloads into Google Cloud. In a rehost migration, an organization moves a workload from a source environment to a target environment with minimal or no code modifications. In a refactor migration, teams modify and optimize the application's code and configuration to take advantage of cloud-native capabilities such as elastic scalability and high availability.
This approach would be appropriate if Workload A had cloud-friendly licensing and needed to move quickly to Google Cloud with minimal code changes, and if Workload B were a valuable, actively used core application that required code updates to run efficiently in a cloud environment.
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