Diagram
A decision tree for rehosting a legacy workload on Google Cloud: it first checks whether the app can run as a standard VM or is tightly coupled to VMware, then branches on compliance and Windows licensing needs to pick VMware Engine, sole-tenant Compute Engine, or multi-tenant Compute Engine.
Choosing Between the Two Rehosting Targets
The two main Google Cloud rehosting targets differ in how much of the existing platform they preserve:
| Target | What it preserves | Choose when |
|---|---|---|
| Google Cloud VMware Engine | VMware environment, vSphere, vCenter, HCX, NSX-T, vSAN policies | The application is tightly coupled to VMware and needs minimal change |
| Google Compute Engine | Individual VMs, with multi-tenant or sole-tenant tenancy | The application can run on standard VMs and does not need VMware-specific features |
Exam tip: Rehosting keeps the application largely unchanged; workloads that no longer satisfy requirements, can be replaced by similar applications, or depend on end-of-life technology may be better candidates for other migration paths.
Domain 6 of 6
27 practice questions
Practice this DomainLast updated