Configure and manage automation of tasks →hardMultiple Select

DP-300 Configure and manage automation of tasks Practice Question

Which THREE actions can be performed by using Elastic Database Jobs in Azure SQL Database? (Choose three.)

⚠ Common exam trap

It's easy for candidates to assume Elastic Database Jobs can perform any administrative task, but they are strictly limited to executing T-SQL scripts and cannot perform resource-level operations like creating databases or changing service tiers.

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

✓

Run a T-SQL script to update statistics across multiple databases.

Elastic Database Jobs in Azure SQL Database are designed to run T-SQL scripts against a target group of databases, so option A is correct: a job can execute a T-SQL script that runs UPDATE STATISTICS across multiple databases in the target group. Option B is correct because jobs can run T-SQL that queries catalog views such as sys.databases and sys.dm_db_resource_stats and inserts the results into a table for centralized metadata collection. Option E is correct because index maintenance, including ALTER INDEX ... REBUILD, is a T-SQL operation that can be executed by a job against every database in an elastic pool used as the job target. Option C is not correct because creating a new Azure SQL Database is a control-plane operation performed through the Azure portal, PowerShell, CLI, or REST API, not through the T-SQL execution model of Elastic Database Jobs. Option D is not correct because changing the service tier objective (SLO) is also a management/control-plane action, not a T-SQL statement that Elastic Database Jobs can run against target databases.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Run a T-SQL script to update statistics across multiple databases.
Why this is correct
Elastic Database Jobs run T-SQL against a target group of databases, so a statistics-update script can execute across many Azure SQL databases from one job definition. This satisfies the stem's requirement for cross-database administrative scripting.
✓
Collect metadata about databases and store it in a table.
Why this is correct
Elastic Database Jobs can query each target database and write the returned rows into a central results table, enabling metadata collection across the fleet. This satisfies the stem's requirement for gathering and storing per-database information.
✗
Create a new Azure SQL Database.
Why it's wrong here
Elastic Database Jobs run T-SQL scripts against existing databases in a target group; they cannot provision a new Azure SQL Database, which requires control-plane operations via portal, CLI, PowerShell or ARM templates. It is tempting because jobs orchestrate fleet-wide database tasks, but creation sits outside their T-SQL execution scope.
✗
Change the service tier objective (SLO) of a database.
Why it's wrong here
Elastic Database Jobs execute T-SQL against target databases; altering a database's service tier is a management-plane operation performed through Azure portal, CLI, PowerShell or ARM, not job T-SQL. It is tempting because jobs run scheduled commands across many databases, but scaling is not one of them.
✓
Rebuild indexes on all databases in an elastic pool.
Why this is correct
Elastic Database Jobs run T-SQL against a target group, so a single job can iterate every database in the pool and execute ALTER INDEX ... REBUILD. This satisfies the stem's requirement for pool-wide index maintenance without external orchestration, since the job's target group defines the databases and the job step supplies the rebuild command.

Go deeper

DP-300 Configure and manage automation of tasks Practice Question

Why each option matters

Option-by-option breakdown

Related to this question