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 runs a legacy monolithic application on dedicated virtual machines (VMs). Leadership plans to modernize the application into containerized microservices on Google Kubernetes Engine (GKE) to address several challenges:
Which strategic outcome will the organization achieve by adopting containerized microservices?
Modernizing a monolithic application into containerized microservices involves decoupling a single, tightly integrated codebase into smaller, autonomous service components packaged as lightweight containers. Orchestrating these containers on Google Kubernetes Engine (GKE) enables organizations to adopt cloud-native patterns that transform both software delivery and infrastructure efficiency.
Unlike simple infrastructure migration strategies that preserve legacy architectural bottlenecks, transitioning to containerized microservices directly resolves the root causes of slow delivery, hardware underutilization, and architectural rigidity.
Migrating existing virtual machines directly to Compute Engine without modifying the underlying application code or architecture is known as rehosting, or a lift-and-shift migration. Its primary purpose is to quickly transition workloads off on-premises hardware and into the cloud infrastructure with minimal initial engineering effort.
This option would be the right choice if the organization wanted to exit an on-premises data center rapidly with minimal upfront risk and had workloads with few dependencies that were not worth refactoring.
While rehosting is a valid initial step in a phased migration strategy, achieving the strategic outcomes of containers and microservices requires refactoring or re-architecting the application code to untangle dependencies.
Deploying only net-new workloads to the public cloud while leaving existing legacy applications untouched in their current environment is known as a strict cloud-first approach. This strategy focuses IT modernization efforts exclusively on brand-new initiatives rather than transforming established systems.
This option would be appropriate if the organization decided that the existing legacy application was restricted by strict regulatory constraints or end-of-life hardware dependencies that made migration unfeasible, and instead chose to focus solely on building new digital products in the cloud.
Organizations often combine a cloud-first mindset for new applications with a structured modernization path (such as refactoring into microservices) for high-value legacy workloads to maximize return on investment.
An architecture where all components share local state, rely on local dependencies, and must be deployed and scaled together as a single unit describes a traditional stateful monolithic architecture. In this model, user sessions, cached data, and business logic are tightly bound to specific server instances.
This option would describe the behavior of a legacy monolithic system prior to modernization, or a specialized legacy workload that has not yet been decoupled into stateless, independent services.
Modern cloud-native architectures emphasize decoupled and stateless design patterns. By separating applications into independent microservices and storing state externally in managed databases or shared caches, containers can scale rapidly, withstand restarts, and be upgraded independently.
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