Examkin

Question

Difficulty: HardMigration Assessment and Strategy

A company plans to migrate its on-premises customer relationship management (CRM) application, currently hosted on Hyper-V virtual machines, to Azure. The on-premises environment consists of the following components:
- Three web servers running IIS that communicate frequently with the database.
- A backend database server running SQL Server 2022 that relies heavily on SQL Server Agent jobs and cross-database queries.
- An identity structure where users authenticate against the local Active Directory Domain Services (AD DS). The company does not use smart cards and has no requirement for federated identity.

You need to design the migration assessment and target architecture to ensure zero disruption in database compatibility and identity integration, while also mapping server interdependencies.

Which two actions should you include in your recommendation? (Choose two.)

  1. Recommend Azure SQL Managed Instance as the migration target for the SQL Server database to maintain support for cross-database queries and SQL Server Agent jobs.Answer
  2. Use Azure Migrate dependency analysis to map all network connections and interdependencies for the Hyper-V virtual machines before planning the migration groups.Answer
  3. C
    Migrate the SQL Server database to Azure SQL Database single databases to optimize costs and minimize administrative overhead.
  4. D
    Configure Active Directory Federation Services (AD FS) on Azure virtual machines to enable user authentication for the migrated workloads.
  5. E
    Group workloads and schedule migration runs immediately after virtual machine discovery, bypassing the dependency analysis phase to accelerate the project timeline.

Answer

Recommending Azure SQL Managed Instance ensures compatibility for cross-database queries and SQL Server Agent jobs. Utilizing Azure Migrate dependency analysis maps VM dependencies to prevent network latency and disconnects during migration.
Selecting Azure SQL Managed Instance ensures compatibility for cross-database queries and SQL Server Agent jobs. Performing dependency analysis in Azure Migrate identifies all interconnected application components to ensure a seamless migration without network disconnects.

Step-by-Step Solution

1
Analyze database feature requirements
Identify that the backend SQL Server requires cross-database queries and SQL Server Agent jobs.
This constraints the target relational database service options in Azure.
2
Evaluate Azure SQL migration targets
Select Azure SQL Managed Instance because it supports instance-level features like SQL Server Agent and cross-database queries, whereas Azure SQL Database single database does not.
To ensure database compatibility without modifying application code.
3
Evaluate VM assessment strategy
Run dependency analysis within Azure Migrate to identify network communication between the IIS web servers and the backend database.
To prevent high latency or connection loss by keeping dependent VMs in the same migration group.
4
Evaluate identity requirements
Rule out AD FS as the primary recommendation since there is no requirement for federation, meaning a simpler sync mechanism like Microsoft Entra Connect with PHS is optimal.
To reduce design complexity and operational overhead.

Key Concept

Azure Migrate dependency mapping and database target alignment based on legacy SQL feature dependencies.
Rate this question

Topics

Migration Assessment and Strategy

More questions from this topic