AZ-305 Question 197
Select 3Your company plans to migrate a mission-critical on-premises .NET application and its underlying SQL Server database to Azure with minimal downtime. You want to thoroughly assess performance and test final changes before cutting over to production in Azure. Which three design considerations should you include in your migration plan?
- A
Deploy the Azure Migrate appliance to perform an on-premises assessment and gather performance data.
- B
Use Azure Database Migration Service in online mode to replicate ongoing changes from the on-premises SQL database to Azure.
- C
Cut over directly to the production environment without testing to reduce overhead.
- D
Rely exclusively on Azure Site Recovery for VM replication, ignoring database-specific migration tools.
- E
Perform a test migration using Azure Migrate’s ‘Test Migration’ feature in a sandbox environment.
- F
Skip baseline performance assessments to expedite the migration timeline.
Show answer and explanation
Correct answers: A, B, E
Explanation
A well-designed migration plan involves collecting performance data, using appropriate services for continuous replication to minimize downtime, and conducting a test migration prior to final cutover. Azure Migrate, combined with Azure Database Migration Service, allows assessment of on-premises workloads, site replication, and database synchronization. Following Microsoft’s best practices (see docs.microsoft.com/azure/migrate and docs.microsoft.com/azure/dms), these steps help ensure a successful, low-downtime migration.
- A. Correct.
Option 1 is correct because the Azure Migrate appliance is essential for collecting on-premises workload performance data, sizing, and dependencies. This assessment phase helps you make informed decisions for right-sizing and planning your migration strategy.
- B. Correct.
Option 2 is correct because Azure Database Migration Service (DMS) in online mode allows you to replicate ongoing changes from on-premises databases to Azure. This helps minimize downtime by enabling continuous data synchronization until final cutover.
- C. Incorrect.
Option 3 is incorrect because cutting over directly to production without proper testing increases the risk of unforeseen complications and extended downtime if issues arise. A test migration is strongly recommended for mission-critical workloads.
- D. Incorrect.
Option 4 is incorrect because, while Azure Site Recovery can replicate virtual machines, it does not provide the same level of database-specific capabilities or continuous SQL replication as Azure Migrate and Azure DMS do for a mission-critical SQL workload. ASR is more oriented toward disaster recovery scenarios rather than in-depth migration assessments and online database migrations.
- E. Correct.
Option 5 is correct because Azure Migrate offers a ‘Test Migration’ feature, allowing you to run a trial migration to a sandbox environment. This ensures your application and database function properly in Azure before cutting over to production.
- F. Incorrect.
Option 6 is incorrect because skipping baseline performance assessments removes critical insights into resource utilization and sizing. Without this data, you risk over-provisioning or under-provisioning in Azure, leading to cost inefficiencies or performance bottlenecks.