AZ-305 ยท Migration design
Migrating servers and apps with Azure Migrate
Azure Migrate server migration (agentless vs agent-based replication, test migration, cutover), App Service migration of web apps, moving to IaaS vs PaaS.
Key points
- Agentless (recommended): VMware via appliance, snapshots and Changed Block Tracking; Hyper-V via provider and Recovery Services agent on hosts.
- Agent-based: Replication appliance plus Mobility service agent in every VM; physical, AWS, GCP, Xen, KVM.
- Flow: initial and delta replication, test migration (non-production VNet), Migrate (source shut down, final sync), Complete migration.
- ASP.NET apps to App Service: replatform.
Source: https://learn.microsoft.com/en-us/azure/migrate/server-migrate-overview
Practice questions
In agent-based server migration with Azure Migrate, what is installed inside each machine that you replicate?
- The Azure Migrate appliance
- The Mobility service agent
- The Azure Connected Machine agent
- The Azure File Sync agent
Show answer
Answer: B. The Mobility service agent
Agent-based replication needs the Mobility service agent on every VM or physical server, working with a separate Replication appliance. The Azure Migrate appliance used for agentless VMware replication does not put anything inside the guests.
Which statements about a test migration in Azure Migrate are correct?
- The source machine stays online and keeps replicating
- It creates an Azure VM from replicated data, ideally in a non-production VNet
- Running it at least once per machine before cutover is recommended
- It stops replication, so replication must be re-enabled afterwards
- It is mandatory; the final migration cannot start without it
Show answer
Answer: A. The source machine stays online and keeps replicating, B. It creates an Azure VM from replicated data, ideally in a non-production VNet, C. Running it at least once per machine before cutover is recommended
A test migration builds an Azure VM from the replicated data, ideally in a non-production VNet, while the source keeps running and replicating; Microsoft recommends doing it at least once per machine. It does not stop replication, and you can skip the testing stage and go straight to migration.
When you start the final migration of a VMware VM with agentless replication, changes made since the last replication cycle are lost unless you copy them manually.
Show answer
Answer: False
False. By default Azure Migrate shuts down the source VM and runs an on-demand replication of the remaining changes before creating the Azure VM, so the planned migration has no data loss. You can opt out of the shutdown, but that is your choice.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
