In this video, you will learn about the other features that Migrate for Compute Engine supports, like test clones and offline migration. Testing your applications in the cloud before you officially migrate them is an important way to save time and mitigate migration risk. It gives enterprises the opportunity to easily see how applications perform in the cloud and to make the appropriate adjustments before going live. Creating a test clone is completely optional, but we recommend testing virtual machines before putting them in production. Unlike the migration process, test clones leave the on-premises VMs running and create an identical clone of that machine from a snapshot of the source virtual machine. The image begins to transfer to the source environment Google Cloud platform. Thanks to its streaming technology Migrate for Compute Engine starts a thin clone in the cloud within about five minutes. The machine's data is streamed over secure connection to a highly optimized cache. There are a few points to be aware of. First, each virtual machine can have a maximum of one test clone at a time. Second, Windows virtual machines are automatically configured to run in the cloud, but Linux-based virtual machines need to have an RPM package or similar manually installed in addition. The test clone virtual machine is created in right isolation storage mode. That means, the changes in the cloud-based clone storage are not written back to on-premises storage. It is important to remember that test clones are exact copies of your source workload, including any credentials, data, and state which is currently being used on the virtual machine. And remember, both of them are running at the same time. We recommend that you use test clones in an isolated VPC or subnet to avoid conflicts or race conditions, which other services such as active directory, DNS, and shared repositories. After testing your workload with the test clone, you should delete it, deleting the test clone removes it from Google Cloud. Note that deleting the test clone has no impact whatsoever on your live system or data. No changes made to data in the test clone are ever written back to your live system.