Examkin

Question

Difficulty: HardMigration Assessment and Strategy

A company is planning to migrate a legacy inventory application to Azure. The application's frontend web tier runs on VMware vSphere virtual machines, while its backend Microsoft SQL Server database runs on a dedicated physical Windows server cluster. The SQL Server database relies on cross-database queries and SQL Server Agent jobs. All servers are located in a secure network zone with no direct internet access, but they can route traffic through an outbound HTTPS proxy. You need to design an Azure Migrate assessment to map the application's network dependencies and determine the correct target database tier in Azure. Which two actions should you include in the assessment design? (Choose two.)

  1. Install the Azure Monitor Agent and the Dependency Agent on the physical SQL Server machines to map dependencies.Answer
  2. B
    Enable agentless dependency mapping on the physical SQL Server machines by deploying the Azure Migrate appliance.
  3. Assess the SQL Server database for migration to Azure SQL Managed Instance.Answer
  4. D
    Recommend Azure SQL Database elastic pools as the target for the SQL Server database migration.
  5. E
    Deploy Active Directory Federation Services (AD FS) on-premises to support identity synchronization to Microsoft Entra ID.

Answer

Installing the Azure Monitor Agent and Dependency Agent on the physical SQL Server machines to map dependencies, and assessing the SQL Server workload for migration to Azure SQL Managed Instance.
The correct strategy involves installing the Azure Monitor Agent and Dependency Agent on the physical servers, and assessing the SQL database for migration to Azure SQL Managed Instance. Physical servers do not support agentless dependency analysis in Azure Migrate, making the installation of agents necessary to map dependencies. Additionally, because the legacy database relies on SQL Server Agent jobs and cross-database queries, it must be migrated to Azure SQL Managed Instance, as Azure SQL Database does not support these features.

Step-by-Step Solution

1
Analyze the database requirements.
Identify that the database relies on cross-database queries and SQL Server Agent jobs.
These features dictate which Azure SQL database service tier must be selected for compatibility.
2
Select the appropriate Azure SQL service tier.
Determine that Azure SQL Managed Instance is the required target database tier.
Azure SQL Database single database and elastic pools do not support SQL Server Agent or cross-database queries, making Azure SQL Managed Instance the minimum compatible fully managed tier.
3
Analyze the virtualization environment for dependency mapping.
Identify that the database runs on physical servers, whereas the web tier runs on VMware VMs.
Azure Migrate has different dependency mapping capabilities depending on whether the source server is a virtual machine or a physical server.
4
Determine the dependency mapping method for the physical servers.
Select agent-based dependency mapping by installing the Azure Monitor Agent and Dependency Agent.
Azure Migrate does not support agentless dependency mapping for physical servers; agentless mapping is restricted to VMware and Hyper-V VMs.

Key Concept

Designing a migration assessment strategy that accounts for physical server dependency mapping limitations and database platform feature compatibility.
Estimated Time:2m 30s
Rate this question

Topics

Migration Assessment and Strategy

More questions from this topic