Question

Difficulty: Very hardMigration Assessment and Strategy

A company plans to migrate its legacy ERP system from an on-premises datacenter hosting physical servers and VMware vSphere virtual machines to Azure.

The system requirements and constraints are:
- The inventory consists of 40 virtual machines running on VMware vSphere and 5 physical servers running specialized processing software.
- The database tier runs on SQL Server on-premises, using SQL Server Agent jobs for nightly ETL tasks and cross-database queries between two databases on the same instance.
- Users will authenticate using their existing on-premises Active Directory Domain Services (AD DS) credentials. No advanced federation features (such as certificate-based authentication or smart cards) are required, but minimizing infrastructure overhead and deployment complexity is critical.
- You need to map application dependencies for all servers to identify migration groups, ensuring that network connection details (ports, IP addresses) are captured for security group planning.

Which two actions should you include in the migration assessment and strategy? (Choose two.)

  1. Configure agentless dependency mapping for the VMware virtual machines, and install the Azure Monitor agent and Dependency agent on the physical servers to enable agent-based dependency mapping.Answer
  2. Recommend Azure SQL Managed Instance as the target database tier, and run the Azure SQL migration assessment using Azure Migrate to evaluate compatibility.Answer
  3. C
    Configure agentless dependency mapping for both the VMware virtual machines and the physical servers using the Azure Migrate appliance.
  4. D
    Deploy Active Directory Federation Services (AD FS) on-premises and configure a federation trust with Microsoft Entra ID to authenticate users.
  5. E
    Recommend Azure SQL Database elastic pools as the target database tier to support the cross-database queries.

Answer

The correct strategy involves combining agentless dependency mapping for VMware virtual machines with agent-based dependency mapping for physical servers, and recommending Azure SQL Managed Instance as the target database tier to support cross-database queries and SQL Server Agent jobs.
The correct strategy involves combining agentless dependency mapping for VMware virtual machines with agent-based dependency mapping for physical servers, as physical servers do not support agentless discovery for network connections. Additionally, since the application requires SQL Server Agent and cross-database queries, Azure SQL Managed Instance is the required target database tier, and performing a compatibility assessment is necessary to identify any migration blockers.

Step-by-Step Solution

1
Analyze the virtual and physical server inventory and determine the appropriate dependency mapping method.
VMware virtual machines can use agentless dependency mapping, while the physical servers require agent-based dependency mapping with the Azure Monitor agent and Dependency agent.
Agentless dependency mapping is not supported for physical servers in Azure Migrate, so a hybrid dependency strategy is required.
2
Evaluate the on-premises SQL Server requirements, specifically cross-database queries and SQL Server Agent.
Identify Azure SQL Managed Instance as the appropriate target database tier.
Azure SQL Database single databases or elastic pools do not support native cross-database queries or SQL Server Agent jobs, which are legacy requirements.
3
Analyze the identity synchronization requirements for hybrid authentication.
Determine that Microsoft Entra Password Hash Synchronization (PHS) with Seamless SSO is the optimal identity synchronization mechanism.
Using PHS with Seamless SSO minimizes infrastructure overhead and complexity compared to deploying AD FS, as there are no requirements for advanced federation features.

Key Concept

Selecting the correct assessment tools, dependency mapping strategies, and database target tiers during an Azure migration planning phase.
Estimated Time:3m 0s
Rate this question