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 runs a legacy monolithic application on on-premises virtual machines and plans to modernize it on Google Cloud. The leadership team has established the following modernization goals:
Which application modernization approach should the organization implement?
Migrate to Containers is a modernization tool that extracts existing applications from virtual machines—such as those running on VMware or Compute Engine—and packages them into native containers without requiring access to source code or rewriting the application. Deploying that resulting container to Cloud Run runs the workload on Google Cloud's serverless infrastructure, which automatically provisions resources and bills on a pay-per-use basis.
Using Migrate to Containers would be appropriate if the organization wanted to quickly replatform an existing VM-based application into a container to unify infrastructure management and increase workload density on GKE without rewriting or decomposing the application code.
In Compute Engine, a custom image is a preconfigured virtual machine boot disk that contains an operating system along with application-specific software and settings. An instance template combines this custom boot disk image with a machine type and network settings so administrators can launch identical VM instances or scale fleets of VMs using managed instance groups.
This approach would be suitable if the organization was performing a lift-and-shift (rehosting) migration of a legacy VM workload that could not be containerized and needed a repeatable way to provision identical Compute Engine VMs for disaster recovery or basic horizontal scaling.
Refactoring (or re-architecting) transforms a monolithic application by decomposing it into loosely coupled, independent microservices packaged inside containers. A container is a lightweight, standalone executable package that bundles application code with its runtime, system tools, and libraries. By adopting a hybrid container runtime strategy on Google Cloud, organizations can run stateless workloads on Cloud Run—a fully managed, serverless container platform—while hosting complex or stateful workloads on Google Kubernetes Engine (GKE), a managed Kubernetes orchestration environment.
Unlike simple virtual machine migrations or basic component replatforming, combining refactoring with containerization across Cloud Run and GKE unlocks true cloud-native agility. It pairs the zero-ops simplicity and scale-to-zero economics of serverless computing with the deep architectural control of Kubernetes.
Replatforming is a cloud modernization approach where an organization optimizes specific parts of an application—such as its database, caching layer, or storage system—without changing the core application architecture and with minimal changes to the codebase. In this approach, the monolithic application continues to run on Compute Engine virtual machines (VMs), while a self-hosted relational database is replaced with Cloud SQL, a fully managed database service that handles patching, backups, and high availability.
This approach would be the right choice if the organization wanted a low-risk intermediate modernization step to reduce database administration overhead and improve VM availability using managed instance groups, without investing the time and effort to rewrite or re-architect the monolithic codebase.
While replatforming databases to Cloud SQL is a valuable practice during cloud migration, achieving independent team velocity and cross-platform portability requires decomposing the monolith and adopting containerization.
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