DP-300 Configure and manage automation of tasks Practice Question
Which THREE components are required to run Elastic Database Jobs for Azure SQL Database? (Choose three.)
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
✓
A job database
Elastic Database Jobs require a job database (A), which stores job definitions, execution history, and job step metadata, and it must reside in the same Azure SQL Database server as the job agent. They also require a job agent (C), the Azure resource that executes T-SQL against the target databases and is created in the job database's server. Target databases (B) are required because they are the members of the job group against which the job steps run. SQL Agent (D) is not used, since Elastic Database Jobs are an Azure SQL Database-native feature rather than an on-premises SQL Server Agent component. Azure Automation account (E) is also unnecessary, as scheduling and execution are handled by the job agent and job database, not by Azure Automation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A job database
Why this is correct
Elastic Database Jobs require a job database to store job definitions, execution history and step metadata. It holds the T-SQL scripts and schedules the job agent executes against target members, making it an essential component alongside the job agent and target group.
- ✓
Target databases (members of the job group)
Why this is correct
Target databases form the job group that the job agent executes T-SQL against. Without defined members, the job has no scope to run on, so target databases are a required component alongside the job database and job agent.
- ✓
A job agent
Why this is correct
The job agent is the Azure resource that connects to the job database, retrieves job definitions and executes them against target databases in the group. It is a mandatory component alongside the job database and target group members.
- ✗
SQL Agent
Why it's wrong here
Elastic Database Jobs execute through the Elastic Job agent, not SQL Agent, which is absent from Azure SQL Database. It is tempting because SQL Agent schedules jobs on SQL Server, but the Azure service replaces that role with the job agent and job database.
- ✗
Azure Automation account
Why it's wrong here
Elastic Jobs use a job database, a target database, and a job agent; an Automation account is not part of that architecture. It is tempting because Automation accounts run scheduled runbooks, but Elastic Jobs schedule T-SQL against Azure SQL Database through the job agent instead.
Go deeper
Related to this question
Learn chapter
Configuring Automation Tasks for Database Administration
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
About these practice questions
Courseiva writes every DP-300 question from scratch — 574 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-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.