Courseiva

DP-300 Plan and implement data platform resources Practice Question

A company is planning to migrate their on-premises SQL Server databases to Azure SQL Managed Instance. They have a database that uses SQL Server Agent jobs with proxies and also uses cross-database queries extensively. What is the main consideration for this migration?

⚠ Common exam trap

A common mix-up: candidates assume Azure SQL Database is always the cheaper or simpler option, overlooking that it lacks SQL Agent proxies and native cross-database query support, which are critical for this migration.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Migrate to Azure SQL Managed Instance as it supports SQL Agent and cross-database queries within the same instance.

Azure SQL Managed Instance is the correct target because it provides full support for SQL Server Agent, including proxies, and enables cross-database queries within the same instance. Unlike Azure SQL Database, Managed Instance maintains instance-level scope, allowing queries that reference other databases in the same instance without requiring external data sources or elastic queries.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Migrate to Azure SQL Managed Instance as it supports SQL Agent and cross-database queries within the same instance.

    Why this is correct

    Azure SQL Managed Instance preserves SQL Server Agent, including proxies, and supports cross-database queries within the same instance, unlike Azure SQL Database. This makes it the viable target for a database depending on both features.

  • ✗

    Migrate to SQL Server on Azure Virtual Machines for full control.

    Why it's wrong here

    SQL Server on Azure Virtual Machines runs the full engine, so Agent proxies and cross-database queries work, but the question asks for the main consideration when migrating to SQL Managed Instance, which already supports both features. IaaS suits lift-and-shift of unsupported engine features, not this scenario.

  • ✗

    Migrate to Azure SQL Database elastic query to handle cross-database queries.

    Why it's wrong here

    Elastic query targets Azure SQL Database, not SQL Managed Instance, and cannot replicate SQL Server Agent proxies or full cross-database query behaviour. It tempts because elastic query handles cross-database access in Azure SQL Database, but Managed Instance already supports native cross-database queries and Agent jobs.

  • ✗

    Migrate to Azure SQL Database instead to reduce costs.

    Why it's wrong here

    Azure SQL Database lacks SQL Server Agent job proxies and blocks three-part cross-database queries, so this database's dependencies would break. It is tempting because it is the lowest-cost PaaS tier, and it would be the right target for a standalone database with no Agent or cross-database dependencies.

Go deeper

Related to this question

About these practice questions

This DP-300 question is part of Courseiva's 574-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.