DP-900 Practice Question: Identify considerations for relational data on Azure
A company is migrating a SQL Server database to Azure SQL Database. The database uses CLR (Common Language Runtime) integration for business logic and has database mail configured. The company needs full instance-level functionality while still benefiting from the platform-as-a-service model. Which Azure SQL deployment option should they choose?
⚠ Common exam trap
It's easy for candidates to confuse Azure SQL Database Hyperscale as a separate deployment option that adds instance features, when in fact it is merely a scaling tier for single databases and does not enable CLR or Database Mail.
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
✓
Azure SQL Managed Instance
Azure SQL Managed Instance is the correct choice because it provides near 100% compatibility with SQL Server on-premises, including support for CLR integration and Database Mail, while still offering a platform-as-a-service (PaaS) model. Single databases and elastic pools lack these instance-scoped features, and Hyperscale is a scaling option for single databases, not a separate deployment type that adds instance-level functionality.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure SQL Database (single database)
Why it's wrong here
Azure SQL Database (single database) is a PaaS offering that hosts one logical database on a multi-tenant logical server, but it exposes no instance-level scope. Features like SQL Agent jobs, instance-level logins, CLR integration, and database mail are either unsupported or significantly limited, so applications relying on them will fail during migration. It is best suited for modern, cloud-optimized apps that do not require instance-level dependencies.
When this WOULD be correct
A company needs a fully managed, scalable database with minimal administrative overhead, does not require CLR or database mail, and wants to migrate a single database without instance-level features.
- ✗
Azure SQL Database elastic pool
Why it's wrong here
Azure SQL Elastic Pool is not a separate database engine but a resource-governance mechanism that lets multiple single databases share a fixed pool of vCores or DTUs on one logical server. While it provides cost efficiency by multiplexing idle databases, it does not add any instance-scope features or closer SQL Server compatibility. An elastic pool still runs on the same Azure SQL Database platform, so CLR, database mail, and SQL Agent remain unavailable; it simply changes how capacity is allocated among databases.
When this WOULD be correct
A company needs to manage multiple databases with varying and unpredictable usage patterns, and wants to optimize cost by sharing resources among them. They do not require CLR, database mail, or instance-scoped features.
- ✓
Azure SQL Managed Instance
Why this is correct
Azure SQL Managed Instance is a Platform-as-a-Service deployment that provides the broadest SQL Server engine compatibility among managed offerings, including support for instance-scoped features like SQL Server Agent, CLR integration, database mail, Service Broker, and cross-database queries. This makes it the appropriate migration target for an existing SQL Server instance that depends on instance-level objects or features. Unlike single databases, it exposes a full SQL Server instance boundary, so logins, server roles, and instance-level permissions are preserved.
- ✗
Azure SQL Database Hyperscale
Why it's wrong here
Azure SQL Database Hyperscale is a highly scalable service tier for a single database that decouples compute from storage to support databases up to hundreds of terabytes. However, it is still a single-database deployment, not a managed instance, and thus it does not expose instance-level features such as SQL Server Agent or CLR integration. Its purpose is to address performance and scale challenges, not to resolve compatibility limitations of the Azure SQL Database platform.
When this WOULD be correct
A question where the scenario involves a large database with high transaction throughput, requiring rapid scaling and storage up to 100 TB, and the workload does not need CLR or database mail. For example: 'A company has a 50 TB database with heavy read/write operations and needs to scale quickly. Which Azure SQL option provides the best performance and scalability?'
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Azure SQL Managed InstanceCorrect answer▾
Why this is correct
Azure SQL Managed Instance is a Platform-as-a-Service deployment that provides the broadest SQL Server engine compatibility among managed offerings, including support for instance-scoped features like SQL Server Agent, CLR integration, database mail, Service Broker, and cross-database queries. This makes it the appropriate migration target for an existing SQL Server instance that depends on instance-level objects or features. Unlike single databases, it exposes a full SQL Server instance boundary, so logins, server roles, and instance-level permissions are preserved.
✗Azure SQL Database (single database)Wrong answer — click to see why▾
Why this is wrong here
Azure SQL Database (single database) does not support CLR integration or database mail, which are required by the company for full instance-level functionality.
★ When this WOULD be the correct answer
A company needs a fully managed, scalable database with minimal administrative overhead, does not require CLR or database mail, and wants to migrate a single database without instance-level features.
Why candidates choose this
Candidates may think 'single database' is the simplest PaaS option and assume it supports all SQL Server features, overlooking the limitations on CLR and instance-scoped configurations.
✗Azure SQL Database elastic poolWrong answer — click to see why▾
Why this is wrong here
Azure SQL Database elastic pool does not support CLR integration or database mail, which are required for the migration. It also lacks full instance-level functionality, such as SQL Agent and cross-database queries.
★ When this WOULD be the correct answer
A company needs to manage multiple databases with varying and unpredictable usage patterns, and wants to optimize cost by sharing resources among them. They do not require CLR, database mail, or instance-scoped features.
Why candidates choose this
Candidates may confuse elastic pools with managed instances, thinking that pooling provides instance-level control, or they may overlook the specific requirements for CLR and database mail.
✗Azure SQL Database HyperscaleWrong answer — click to see why▾
Why this is wrong here
Azure SQL Database Hyperscale is designed for large-scale, high-throughput workloads with fast scaling, but it does not support CLR integration or database mail, which require instance-level features only available in Azure SQL Managed Instance.
★ When this WOULD be the correct answer
A question where the scenario involves a large database with high transaction throughput, requiring rapid scaling and storage up to 100 TB, and the workload does not need CLR or database mail. For example: 'A company has a 50 TB database with heavy read/write operations and needs to scale quickly. Which Azure SQL option provides the best performance and scalability?'
Why candidates choose this
Candidates may confuse Hyperscale's advanced scalability and performance features with full instance-level functionality, assuming that a premium tier would include all SQL Server features.
Analysis generated from the official DP-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Azure SQL Services
Key term
Azure SQL Database
Azure SQL Database is a fully managed relational database-as-a-service (DBaaS) in Microsoft Azure, based on the SQL Server engine, that handles scaling, backups, patching, and high availability automatically.
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-900 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-900 exam.