An organization plans to migrate a legacy three-tier web application hosted on-premises on a Hyper-V failover cluster to Azure. The application database tier consists of two Microsoft SQL Server virtual machines that execute cross-database queries. The application tier has strict low-latency requirements for database communication. The company wants to implement Microsoft Entra ID for hybrid identity but does not have any regulatory or technical requirements for federated authentication methods.
Which two actions should you include in the migration assessment and strategy? (Choose two.)
- Configure agentless or agent-based dependency analysis in Azure Migrate to identify network communication patterns and group dependent servers.Answer
- Recommend Azure SQL Managed Instance as the migration target for the database servers to support the cross-database queries.Answer
- CDeploy on-premises Active Directory Federation Services (AD FS) to establish identity federation with Microsoft Entra ID.
- DGroup the virtual machines into migration waves based solely on server name prefixes to accelerate the migration timeline.
- EMigrate the database servers to individual Azure SQL Database single databases using the Serverless compute tier.
Answer
Configure agentless or agent-based dependency analysis in Azure Migrate to identify network communication patterns and group dependent servers, and recommend Azure SQL Managed Instance as the migration target for the database servers to support the cross-database queries.
The correct strategy requires performing dependency analysis to map server relationships and support low-latency grouping, while choosing Azure SQL Managed Instance to support cross-database queries.
Step-by-Step Solution
Key Concept
Identifying database compatibility features and network dependencies is critical to designing a successful Azure migration assessment and strategy.
Estimated Time:2m 0s