What's changed: Created Cloud Digital Leader Chapter 4 (Domain 4 "Modernization": migration and computing = approaches (lift-and-shift/move-and-improve/rebuild)/Compute Engine/Spot VM; serverless, containers, APIs, hybrid = GKE/Cloud Run/Cloud Run functions/App Engine/Apigee/GKE).
4.1Cloud migration and computing
Understand the main cloud migration approaches (lift-and-shift, move-and-improve, rebuild) and their trade-offs, the motivations for migration, and the basics of cloud computing starting with Compute Engine, which provides virtual machines.
Modernizing—moving existing systems to the cloud—aims at cost reduction, agility, scalability, and lower operational burden. You need not rebuild everything at once; the practical approach is to choose a migration approach based on each system’s importance, time, and budget.
4.1.1Common migration approaches
| Approach | What it is | Trade-off |
|---|---|---|
| Lift-and-shift (rehost) | Move almost as-is to VMs | Fast but underuses cloud benefits |
| Move-and-improve (replatform) | Move while optimizing parts to managed services | Balanced |
| Rebuild/refactor | Rebuild cloud-native | High payoff but more effort/time |
Lift-and-shift moves existing systems almost as-is to VMs (Compute Engine), which is fast but underuses cloud benefits like autoscaling. Move-and-improve replaces some parts with managed services while migrating—a balanced approach. Rebuild re-architects cloud-native (containers, serverless) for maximum payoff but more time and effort. A staged path—"move quickly first, improve later"—is also common.
4.1.2Compute Engine (virtual machines)
Compute Engine is Google Cloud’s IaaS, providing virtual machines (VMs) with selectable CPU/memory. Because you manage up to the OS, it offers high control and is ideal as a lift-and-shift target for existing systems. It supports autoscaling of instance counts with demand and inexpensive Spot VMs (deeply discounted in exchange for possible preemption), balancing cost and scalability. When you need maximum control or compatibility with an existing OS/software, Compute Engine is the default choice.
Common: situation → approach/service. E.g., "move as-is quickly" = lift-and-shift (Compute Engine); "migrate while making some managed" = move-and-improve; "rebuild cloud-native" = rebuild; "VM with OS-level control" = Compute Engine; "cheap VM that may be preempted" = Spot VM.
Watch the mix-ups: (1) the trade-off lift-and-shift (fast but underuses benefits) vs rebuild (high payoff but high effort). (2) Compute Engine = IaaS (VMs), not serverless or container-only. (3) Migration need not "rebuild everything at once"—staged is fine.
4.1.3Section summary
- Migration = lift-and-shift (fast) / move-and-improve (balanced) / rebuild (high payoff, high effort); staged is fine
- Compute Engine = IaaS VMs; OS-level control, ideal as a lift-and-shift target
- Autoscaling and Spot VMs balance cost and scalability
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. Which migration approach moves existing systems almost as-is to VMs—fastest but underusing cloud benefits?
Q2. Which Google Cloud service provides VMs with OS-level control, ideal as a migration target?
Q3. Which migration approach rebuilds cloud-native with the highest payoff but the most effort and time?
Q4. Which Compute Engine VM offers deep discounts in exchange for possible preemption?
Q5. Which best states the main goal of modernization (cloud migration)?
Q6. Which balanced approach optimizes some parts to managed services while migrating?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.