DP-900 Practice Question: Identify considerations for relational data on Azure
You are designing a multi-tenant SaaS application using Azure SQL Database. Each tenant has its own database. You need to perform maintenance across all databases efficiently. Which feature should you use?
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
✓
Elastic Jobs
(Elastic Jobs) is correct because Elastic Jobs allows executing T-SQL scripts across multiple databases in Azure SQL Database. Option A (Elastic pools) is for resource pooling and sharing, not for running scripts across databases. Option B (Failover groups) is for high availability and disaster recovery. Option C (SQL Server Agent) is not available in Azure SQL Database; it is available in on-premises SQL Server or SQL Server on Azure VMs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Elastic pools
Why it's wrong here
Elastic pools are wrong because they only allocate a shared set of performance resources (e.g., eDTUs or vCores) to a group of databases, providing cost savings for varying utilization. They do not include any job scheduling or script execution functionality, so you cannot use them alone to perform maintenance across tenants. Pooling affects resource governance, not operational automation.
- ✗
Failover groups
Why it's wrong here
Failover groups are wrong because they are a high-availability and disaster-recovery feature for Azure SQL Database. They replicate databases to a secondary server and provide an automatic failover endpoint, but they have no mechanism to execute T-SQL scripts or schedule maintenance tasks across tenant databases. Therefore they don't address cross-database maintenance.
- ✗
SQL Server Agent
Why it's wrong here
SQL Server Agent is wrong because it is not offered in Azure SQL Database; it only exists in SQL Server on-premises, Azure SQL Managed Instance, or SQL Server on Azure VMs. Even though it can schedule maintenance jobs in those environments, it cannot be used for a multi-tenant solution built on Azure SQL Database services. You would need Elastic Jobs instead.
- ✓
Elastic Jobs
Why this is correct
Elastic Jobs is correct because it is the Azure SQL Database service purpose-built for orchestrating T-SQL scripts, index rebuilds, or schema migrations across a large set of databases. You create an Elastic Job Agent, define target groups that can include all tenant databases, and schedule jobs that run against each member in parallel. This makes it the appropriate tool for cross-database maintenance in a multi-tenant SaaS.
Go deeper
Related to this question
About these practice questions
This DP-900 question is part of Courseiva's 820-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 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.