Question

Difficulty: MediumMigration Assessment and Strategy

A company plans to migrate an on-premises payroll application running on physical servers to Azure. The application relies on a local Microsoft SQL Server database that utilizes SQL Server Agent jobs for nightly processing and performs cross-database queries. The company also needs to synchronize their on-premises Active Directory Domain Services (AD DS) identities to Microsoft Entra ID. The migration strategy must minimize administrative and infrastructure overhead, maintain application compatibility, and ensure that all server connections are identified before migration.

Which migration and identity synchronization strategy should you recommend?

  1. Migrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.Answer
  2. B
    Migrate the database to an Azure SQL Database single database, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.
  3. C
    Migrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and deploy Active Directory Federation Services (AD FS) to federate identities.
  4. D
    Migrate the database to Azure SQL Managed Instance, migrate the application servers immediately without performing a dependency analysis to minimize assessment time, and configure Microsoft Entra Connect with Password Hash Synchronization.

Answer

Migrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.
The correct strategy migrates the database to Azure SQL Managed Instance because it supports instance-level features like SQL Server Agent and cross-database queries. It uses Azure Migrate dependency analysis to ensure all connection vectors are verified before server migration. It utilizes Password Hash Synchronization (PHS) to sync identities with the least administrative and on-premises infrastructure overhead.

Step-by-Step Solution

1
Select the database migration target based on application features.
Choose Azure SQL Managed Instance.
The database relies on SQL Server Agent jobs and cross-database queries, which are fully supported natively on Azure SQL Managed Instance but restricted or unsupported on Azure SQL Database single databases.
2
Plan the network and server dependency assessment.
Perform dependency analysis using Azure Migrate.
A dependency analysis identifies all inbound and outbound server connections, ensuring no critical integrations are missed or broken during the migration of physical workloads.
3
Select the hybrid identity synchronization mechanism.
Configure Password Hash Synchronization (PHS) using Microsoft Entra Connect.
PHS requires the least amount of administrative and on-premises infrastructure overhead compared to Active Directory Federation Services (AD FS), satisfying the requirement to minimize operational overhead.

Key Concept

Selecting SQL database deployment tiers, dependency assessment methods, and hybrid identity architectures based on legacy application requirements and operational constraints.
Estimated Time:1m 30s
Rate this question