DP-900 Practice Question: Identify considerations for relational data on Azure
Which TWO of the following are benefits of using Azure SQL Database over SQL Server on Azure Virtual Machines?
⚠ Common exam trap
The trap is mixing IaaS benefits (OS control, custom software) with PaaS benefits (automated patching, built-in HA); candidates who don't clearly distinguish the two models pick options that belong to the VM deployment.
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
✓
Built-in high availability with automatic failover
Option A is correct because Azure SQL Database is a fully managed PaaS offering that includes built-in high availability with automatic failover, typically using a 99.99% SLA and replicas managed by the service, whereas SQL Server on Azure VMs requires you to configure Always On availability groups or failover cluster instances yourself. Option B is correct because Azure SQL Database handles automated patching and updates of the database engine and underlying OS transparently, while SQL Server on Azure VMs leaves OS and SQL Server patching to the customer. Option C is not a benefit because Azure SQL Database does not let you choose any number of vCores arbitrarily; vCore counts are tied to specific hardware generations and service tiers, and cost depends on the chosen tier and compute size. Option D is incorrect because installing custom software on the database server is not possible in Azure SQL Database, but it is possible on SQL Server on Azure VMs. Option E is incorrect because full control over the operating system is a characteristic of SQL Server on Azure VMs (IaaS), not Azure SQL Database, which abstracts the OS away from the customer.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Built-in high availability with automatic failover
Why this is correct
Azure SQL Database's built-in high availability uses multiple synchronous replicas and automatic failover at the database level, so if a node fails, connections are transparently redirected to a healthy replica. This is provisioned and managed by Microsoft without you having to configure Always On Availability Groups or deploy additional VMs. Consequently, you receive a 99.99% uptime SLA while avoiding the operational burden of designing your own HA stack.
- ✓
Automated patching and updates
Why this is correct
With Azure SQL Database, Microsoft owns and executes the entire patching lifecycle: it applies security updates and service fixes to both the OS and the SQL engine, typically during a scheduled, non-arbitrary maintenance window. This means you no longer need to plan, test, or manually install patches as you would on a SQL Server VM. The automation also closes known vulnerabilities promptly, reducing your security overhead and helping meet compliance requirements.
- ✗
Lower cost because you can choose any number of vCores
Why it's wrong here
Choosing a specific number of vCores does not guarantee lower cost; your bill is driven by service tier, DTU/vCore model, storage size, and additional features like geo-replication or long-term backup retention. Moreover, the vCore options are discrete steps rather than any arbitrary value, and an IaaS SQL Server VM can also be scaled to a flexible vCore count. In many steady-state workloads, a SQL Server VM may even be cheaper, so vCore selection alone is not a cost benefit.
- ✗
Ability to install custom software on the database server
Why it's wrong here
Azure SQL Database is a fully managed PaaS offering, so there is no server OS or host environment to access—you cannot install software, agents, or middleware on the underlying server. Even features that seem extensible, such as custom CLR assemblies, are executed inside the database and cannot modify the server. If your application depends on running third-party software on the database server, you would need an IaaS VM instead.
- ✗
Full control over the operating system
Why it's wrong here
Because Azure SQL Database is a PaaS service, Microsoft abstracts the operating system and exposes only database-level management tools like T-SQL and the Azure Portal. You cannot RDP to the server, change Windows registry values, or configure OS-level security policies. Full OS control remains with Microsoft, so for workloads requiring complete administrative control, a SQL Server on an Azure VM is the appropriate choice.
Go deeper
Related to this question
Learn chapter
Cosmos DB Global Distribution and Failover
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
This DP-900 question is part of Courseiva's 851-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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.