DP-300 Configure and manage automation of tasks Practice Question
Which TWO actions can you perform using Elastic Database Jobs in Azure SQL Database?
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
✓
Schedule a job to rebuild indexes on a set of databases.
Options B and E are correct. Elastic Database Jobs in Azure SQL Database allow you to schedule and run T-SQL scripts across multiple databases, including those in an elastic pool. You can use them to schedule index rebuilding (B) and to update statistics via T-SQL (E). Option A is incorrect because firewall rules are managed through Azure SQL Server firewall settings, not Elastic Database Jobs. Option C is incorrect because creating users in Microsoft Entra ID (formerly Azure AD) is done through Active Directory, not Elastic Database Jobs. Option D is incorrect because scaling service tiers is an administrative operation handled by Azure SQL Database scaling commands or automation, not by Elastic Database Jobs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add a firewall rule to allow access from a specific IP address.
Why it's wrong here
Elastic Database Jobs execute T-SQL against target databases; they cannot modify server-level firewall rules, which are managed through the Azure portal, PowerShell or CLI. It is tempting because jobs run across many databases, yet adding an IP firewall rule is a server administration task, not a job action.
- ✓
Schedule a job to rebuild indexes on a set of databases.
Why this is correct
Elastic Database Jobs run T-SQL on a defined target group, so scheduling index rebuilds across a set of databases is a supported maintenance scenario. This satisfies the stem by automating recurring index maintenance without per-database scripting.
- ✗
Create users in Microsoft Entra ID for database access.
Why it's wrong here
Elastic Database Jobs run T-SQL within database scope, so they cannot create Microsoft Entra ID users, which is a directory operation. Creating Entra ID users is correct when provisioning identities for authentication rather than database-level logins.
- ✗
Automatically scale the service tier of a database based on CPU usage.
Why it's wrong here
Elastic Database Jobs execute T-SQL against target databases on a schedule; they cannot alter service tier or DTU settings, which requires Azure Automation, Logic Apps or the Azure portal. Autoscaling is correct when CPU metrics must drive tier changes.
- ✓
Run a T-SQL script to update statistics on all databases in an elastic pool.
Why this is correct
Elastic Database Jobs execute T-SQL against a target group of databases, so a single job can run UPDATE STATISTICS across every database in an elastic pool. This satisfies the stem by automating routine maintenance without connecting to each database individually.
Go deeper
Related to this question
Learn chapter
Implementing High Availability for Azure SQL Databases
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.