A healthcare provider plans to migrate a medical imaging portal and archiving application from an on-premises Hyper-V environment to Azure. The application architecture includes a front-end IIS web portal, an application tier, a SQL Server database cluster utilizing cross-database queries, and a network file share. To ensure a successful migration, you must identify all active network connections, ports, and dependencies between the application components and external systems before grouping servers into migration waves.
Which approach should you include in the migration assessment strategy?
- APlan the migration of the application tiers into separate resource groups based on CPU utilization, then use Azure Monitor network logs post-migration to identify and resolve broken connection dependencies.
- Deploy the Azure Migrate appliance to the Hyper-V host, configure agentless dependency analysis to discover network connections, and recommend Azure SQL Managed Instance as the target for the database tier.Answer
- CRecommend Azure SQL Database single database for hosting the database tier to reduce hosting costs, and deploy the Azure Migrate dependency agent on each Hyper-V VM to map external ports.
- DDeploy Active Directory Federation Services (AD FS) to manage the identity synchronization for database administrators, and perform schema mapping using Azure Data Studio before analyzing network dependencies.
Answer
Deploy the Azure Migrate appliance to the Hyper-V host, configure agentless dependency analysis to discover network connections, and recommend Azure SQL Managed Instance as the target for the database tier.
Deploying the Azure Migrate appliance to perform agentless dependency analysis is the correct approach to discover active connections and ports without VM agent installation overhead. Furthermore, Azure SQL Managed Instance is the correct migration target for the SQL Server cluster because it natively supports legacy features like cross-database queries.
Step-by-Step Solution
Key Concept
Azure Migrate dependency assessment and target tier selection for SQL Server migration
Estimated Time:2m 0s