Question

Difficulty: HardMigration Assessment and Strategy

An organization plans to migrate a customer billing application from an on-premises Nutanix AHV environment to Azure. The application consists of several Linux web servers and a SQL Server database tier. The database tier utilizes SQL Server Agent for scheduled data aggregation and requires cross-database queries across multiple databases. To prepare for the migration, the security team mandates that no software agents can be installed on the source servers for dependency mapping or discovery. The target database solution must be a Platform as a Service (PaaS) offering to reduce administrative overhead. User authentication must be integrated with Microsoft Entra ID using the simplest deployment model that supports credential synchronization, without deploying any federated or on-premises authentication agent servers. Which combination of discovery configuration, target database service, and hybrid identity synchronization should you recommend?

  1. A
    Assessment: Install the Log Analytics and Dependency agents on all servers for dependency mapping. Database: Azure SQL Database. Identity: Microsoft Entra Connect with Active Directory Federation Services (AD FS).
  2. B
    Assessment: Deploy the Azure Migrate appliance and configure agentless dependency analysis. Database: Azure SQL Database. Identity: Microsoft Entra Connect with Pass-through Authentication (PTA).
  3. Assessment: Deploy the Azure Migrate appliance and configure agentless dependency analysis. Database: Azure SQL Managed Instance. Identity: Microsoft Entra Connect with Password Hash Synchronization (PHS).Answer
  4. D
    Assessment: Deploy the Azure Migrate appliance and configure agentless dependency analysis. Database: SQL Server on Azure Virtual Machines. Identity: Microsoft Entra Connect with Active Directory Federation Services (AD FS).

Answer

The correct recommendation is to use agentless dependency analysis with the Azure Migrate appliance, migrate the database to Azure SQL Managed Instance, and implement hybrid identity using Microsoft Entra Connect with Password Hash Synchronization (PHS).
The correct option addresses all technical and organizational constraints. First, agentless dependency analysis with the Azure Migrate appliance maps application dependencies without installing software on the source virtual machines, meeting the security constraint. Second, Azure SQL Managed Instance provides near-100% compatibility with the on-premises SQL Server database engine, supporting legacy features like SQL Server Agent and cross-database queries within a Platform as a Service (PaaS) model. Third, Microsoft Entra Connect with Password Hash Synchronization (PHS) is the simplest hybrid identity configuration because it synchronizes password hashes to Microsoft Entra ID, allowing authentication requests to be handled entirely in the cloud without requiring on-premises authentication agents or federated authentication infrastructure.

Step-by-Step Solution

1
Evaluate the assessment requirement for dependency mapping.
Determine that agentless dependency mapping using the Azure Migrate appliance must be configured.
The security team prohibits the installation of software agents on the source virtual machines, which rules out agent-based dependency mapping.
2
Evaluate the database tier requirements.
Select Azure SQL Managed Instance as the target database solution.
The application requires SQL Server Agent and cross-database queries. Azure SQL Database does not support these features natively. SQL Server on Azure Virtual Machines supports them but is an IaaS offering, violating the PaaS requirement.
3
Evaluate the hybrid identity synchronization requirements.
Select Microsoft Entra Connect with Password Hash Synchronization (PHS).
PHS is the simplest synchronization method and does not require on-premises authentication agent servers (unlike PTA) or federated authentication servers (unlike AD FS) to process or validate logins.

Key Concept

Selecting target migration services and assessment techniques based on technical compatibility, agent requirements, and operational complexity constraints.
Rate this question