Task 1.4: Creating a migration plan (i.e., documents and architectural diagrams).

• AReplicate the VMs to Compute Engine with Migrate to Virtual Machines

  Incorrect

  Migrate to Virtual Machines moves workloads; this phase is assessment, before anything moves.

• BRun the Migration Center discovery client to collect inventory and performance data

  Correct

  The discovery client automatically finds servers and VMs and collects their configuration and utilization for assessment.

• CBuy three-year resource-based commitments for the expected Compute Engine capacity

  Incorrect

  A commitment locks in a machine configuration and region for years; buying it before the estate is measured and sized commits to guesses.

• DRe-platform the SQL Server databases onto Cloud SQL for SQL Server right away

  Incorrect

  Moving the databases is migration work, and leadership asked for numbers before any workload moves.

• EGenerate a TCO report in Migration Center from the collected asset data

  Correct

  The TCO report compares the current environment with the Google Cloud options and their costs, which is the business-case input leadership asked for.

Assessment comes before migration. Migration Center discovers assets, records their utilization and produces cost estimates and TCO reports, which give the business case its numbers.

• AA continuous migration to Cloud SQL for MySQL with Database Migration Service

  Correct

  A continuous migration copies the data and keeps replicating changes until cutover, so the source stays online and downtime is limited to the promotion.

• BA mysqldump export imported into Cloud SQL for MySQL during a weekend outage

  Incorrect

  An export-and-import migration takes the catalog offline for the whole export, transfer and import.

• CA rehost of the database servers to Compute Engine with Migrate to Virtual Machines

  Incorrect

  Rehosting keeps self-managed MySQL on VMs, so it does not deliver the managed service Cymbal wants.

• DA Bigtable instance loaded from nightly exports of the catalog databases

  Incorrect

  Bigtable is not a traditional relational database, so the MySQL-based catalog application would need rewriting, and nightly loads lag a day.

For homogeneous MySQL moves with minimal downtime, Database Migration Service runs a continuous migration into Cloud SQL and lets you promote the destination when you are ready to cut over.

• AStorage Transfer Service agents copying over the network

  Incorrect

  Even a dedicated 1 Gbps link moves well under 600 TB in six weeks, and this one is shared with production.

• Bgcloud storage cp with parallel composite uploads from a server

  Incorrect

  Parallel uploads use the link better but cannot exceed its bandwidth.

• CBigQuery Data Transfer Service scheduled from the archive server

  Incorrect

  This service loads data into BigQuery from supported sources; it does not move file archives.

• DTransfer Appliance, filled on site and shipped back to Google

  Correct

  Transfer Appliance moves large datasets physically, so the transfer does not depend on the slow, shared network link.

Plan data movement from volume, bandwidth and deadline. When the network cannot carry the data in time, Google recommends Transfer Appliance.

• AGoogle Cloud VMware Engine private clouds, moving VMs with HCX

  Correct

  VMware Engine runs the VMware platform in Google Cloud, including vCenter and HCX, so VMs move without conversion and the team keeps its tools.

• BCompute Engine VMs migrated with Migrate to Virtual Machines

  Incorrect

  This converts the VMs to Compute Engine, which changes formats and tooling, and is more work on a four-month deadline.

• CGKE workloads produced from the VMs by Migrate to Containers

  Incorrect

  Containerizing the workloads is re-platforming, which the company ruled out for the exit.

• DCloud Run services rebuilt from each application's source code

  Incorrect

  Rebuilding applications for Cloud Run is a re-platform and takes far longer than the deadline allows.

The migration method follows the constraints: a short deadline, VMware skills and no re-platforming point to VMware Engine, with modernization possible later.

• AMove the largest applications first to free the most rack space early

  Incorrect

  Ordering by size ignores the dependencies that caused the earlier failures.

• BMove each application's database first and its servers in a later wave

  Incorrect

  Splitting tightly coupled tiers across waves adds cross-site latency and the same breakage risk.

• CConvert every VM into containers before the first wave is planned

  Incorrect

  Containerizing is a modernization choice, not a dependency plan, and it delays the migration.

• DGenerate the Migration Center network dependencies report from discovery data

  Correct

  The report shows the observed connections between servers and databases, which reveals which applications depend on each other.

• EPlace applications that depend on each other in the same migration wave

  Correct

  Mapping dependencies is how the assessment phase decides what to move together and in what order.

Dependency planning is part of every migration plan: discover the connections, then group what depends on each other into the same wave.

• ASQL Server VMs on sole-tenant nodes reserved for the company's project

  Incorrect

  Microsoft applications brought under License Mobility do not need sole-tenant nodes, so reserving whole nodes only adds cost.

• BSQL Server license-included images on Compute Engine VMs

  Incorrect

  License-included images charge for SQL Server, so the company would pay for licenses it already owns.

• CIts own SQL Server licenses on Compute Engine VMs on shared hosts

  Correct

  License Mobility lets eligible application licenses such as SQL Server move to Google Cloud while Software Assurance stays active.

• DCloud SQL for SQL Server instances that use the existing licenses

  Incorrect

  Cloud SQL includes the SQL Server license in its price and does not support bringing your own license.

Licensing shapes the migration target. SQL Server licenses with Software Assurance and License Mobility can be brought to ordinary Compute Engine VMs, while managed Cloud SQL and license-included images charge for the license.