Question

Difficulty: Very hardMigration Assessment and Strategy

An organization plans to migrate its legacy inventory management application to Azure. The current workload runs on 1515 physical bare-metal servers hosting Windows Server 20162016. The application uses a backend Microsoft SQL Server 20162016 instance containing multiple databases that rely on SQL Server Agent jobs and cross-database queries.

You need to design a migration assessment and transition strategy that meets the following requirements:
1. Identify and map all network dependencies, process communication paths, and ports across the 1515 physical servers using Azure Migrate.
2. Recommend a fully managed Azure SQL database hosting option that natively supports SQL Server Agent and cross-database queries.
3. Configure a hybrid identity synchronization method that allows on-premises Active Directory Domain Services (AD DS) users to authenticate to Azure resources without deploying any on-premises federation servers.

Which combination of solutions should you recommend?

  1. Perform agent-based dependency analysis by deploying the Azure Migrate appliance and installing the Azure Monitor Agent and Dependency Agent on each of the 1515 physical servers. Migrate the databases to Azure SQL Managed Instance. Configure Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless Single Sign-On (SSO).Answer
  2. B
    Configure agentless dependency mapping by deploying the Azure Migrate appliance and providing local administrator credentials to poll the 1515 physical servers remotely. Migrate the databases to Azure SQL Managed Instance. Configure Microsoft Entra Connect with Active Directory Federation Services (AD FS).
  3. C
    Perform agent-based dependency analysis by deploying the Azure Migrate appliance and installing the Azure Monitor Agent and Dependency Agent on each of the 1515 physical servers. Migrate the databases to Azure SQL Database single databases. Configure Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless Single Sign-On (SSO).
  4. D
    Configure agentless dependency mapping by deploying the Azure Migrate appliance and providing local administrator credentials to poll the 1515 physical servers remotely. Migrate the databases to Azure SQL Database elastic pools. Configure Microsoft Entra Connect with Active Directory Federation Services (AD FS).

Answer

The strategy recommending agent-based dependency mapping using the Azure Monitor Agent and Dependency Agent, Azure SQL Managed Instance, and Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless SSO
The option recommending agent-based dependency mapping, Azure SQL Managed Instance, and Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless SSO is correct. Agent-based dependency mapping is mandatory for physical servers since agentless discovery and mapping are only supported for virtualized VMware and Hyper-V workloads. Azure SQL Managed Instance natively supports instance-level features like SQL Server Agent and cross-database queries. Finally, PHS with Seamless SSO provides authentication without requiring federation servers on-premises, satisfying the identity configuration constraints.

Step-by-Step Solution

1
Determine the dependency mapping strategy for physical bare-metal servers.
Identify that Azure Migrate only supports agentless dependency mapping for VMware and Hyper-V environments. For physical servers, agent-based mapping using the Azure Monitor Agent and Dependency Agent is required.
Correctly matching the server type (physical bare-metal) to the supported Azure Migrate dependency mapping methodology.
2
Select the correct Azure SQL hosting tier for SQL Server features.
Select Azure SQL Managed Instance since it provides near-100% compatibility with on-premises SQL Server databases, natively supporting SQL Server Agent and cross-database queries, unlike Azure SQL Database single databases or elastic pools.
Ensuring application compatibility without code refactoring for database engine features.
3
Select the appropriate hybrid identity synchronization method.
Choose Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless Single Sign-On (SSO) as it allows AD DS users to authenticate to Azure resources without deploying dedicated AD FS federation servers.
Aligning hybrid identity design with on-premises infrastructure constraints.
4
Synthesize the results to identify the matching option.
Select the option combining agent-based dependency analysis, Azure SQL Managed Instance, and PHS with Seamless SSO.
Ensuring all requirements are satisfied by a single option.

Key Concept

Migration Assessment and Strategy
Estimated Time:3m 0s
Rate this question