A manufacturing company is planning the migration of a legacy assembly-line tracking application to Azure. The application runs on several on-premises physical servers running Windows Server and Red Hat Enterprise Linux. There is no up-to-date documentation detailing the network communication or ports used between these physical servers. Additionally, the backend database runs on Microsoft SQL Server 2016 and utilizes cross-database queries to aggregate data across multiple departments.
You need to design a migration assessment strategy to discover the server communication patterns and evaluate database compatibility for Azure migration.
Which two actions should you include in the strategy? (Choose two.)
- Install the Dependency agent and the Log Analytics agent on the physical servers.Answer
- BConfigure agentless dependency analysis using the Azure Migrate appliance.
- Use the Data Migration Assistant (DMA) to assess the SQL Server instances.Answer
- DRecommend migrating the database instances to Azure SQL Database elastic pools.
- EDeploy an Active Directory Federation Services (AD FS) farm on-premises to sync user accounts.
Answer
Install the Dependency agent and the Log Analytics agent on the physical servers, and use the Data Migration Assistant (DMA) to assess the SQL Server instances.
To discover server communication patterns on physical servers, agent-based dependency mapping is required, which is achieved by installing the Dependency agent and the Log Analytics agent on the target servers. To evaluate SQL Server database compatibility and detect blockers like cross-database queries, the Data Migration Assistant (DMA) must be used.
Step-by-Step Solution
Key Concept
Performing migration assessments for physical servers and evaluating database features against target Azure SQL services.