Examkin

Question

Difficulty: HardMigration Assessment and Strategy

An organization is planning to migrate a legacy enterprise resource planning (ERP) system hosted on-premises on physical servers to Azure. The system consists of two application servers running a proprietary Java application that communicates with several unidentified legacy internal services, and a SQL Server database that utilizes SQL Server Agent jobs, cross-database queries, and SQL Common Language Runtime (CLR) integration. The organization requires that users authenticate using their existing on-premises credentials while avoiding the deployment and management of federation infrastructure. Which two actions should you include in the migration assessment and strategy? (Choose two.)

  1. Recommend migrating the database to Azure SQL Managed Instance.Answer
  2. Recommend configuring Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless Single Sign-On (SSO).Answer
  3. C
    Recommend migrating the database to a singleton Azure SQL Database.
  4. D
    Recommend deploying Active Directory Federation Services (AD FS) and Web Application Proxies to federate authentication.
  5. E
    Recommend migrating the database directly to Azure SQL Managed Instance without performing a dependency assessment on the application servers.

Answer

Migrate the database to Azure SQL Managed Instance, and configure Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless Single Sign-On (SSO).
The correct strategy involves migrating the database to Azure SQL Managed Instance because it supports legacy SQL Server features like cross-database queries, SQL Server Agent, and SQL CLR. For identity, configuring Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless SSO provides on-premises credentials for users without the complexity of deploying federation services (AD FS).

Step-by-Step Solution

1
Analyze database requirements.
The database uses SQL Server Agent, cross-database queries, and SQL CLR.
To select a compatible cloud database hosting option.
2
Determine the database tier.
Azure SQL Managed Instance supports these legacy database features, whereas Azure SQL Database does not.
To ensure functional parity and avoid rewriting application code.
3
Analyze identity requirements.
The organization needs on-premises authentication but wants to avoid federation infrastructure.
To choose a hybrid identity solution that minimizes operational complexity.
4
Determine the identity synchronization method.
Microsoft Entra Connect with Password Hash Synchronization (PHS) and Seamless SSO satisfies this requirement without AD FS.
To meet authentication requirements with low administrative overhead.
5
Analyze application dependencies.
The application has dependencies on unidentified legacy services, requiring dependency mapping before migration.
To ensure all dependent components are identified and migrated together, preventing post-migration connectivity issues.

Key Concept

Analyzing database requirements, identity synchronization, and application dependencies for Azure migration assessment.
Rate this question

Topics

Migration Assessment and Strategy

More questions from this topic