DP-300 Configure and manage automation of tasks Practice Question
You have an Azure SQL Managed Instance. You need to automate the execution of a stored procedure every hour to clean up historical data. What is the most appropriate solution?
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
✓
SQL Agent Job
SQL Agent Jobs are a built-in feature of Azure SQL Managed Instance, providing native scheduling for T-SQL jobs like executing a stored procedure every hour. Option B is less appropriate because Azure Logic Apps is an external service that adds complexity and latency. Option C is designed for executing tasks across multiple databases, not a single instance. Option D is external and less integrated compared to the native SQL Agent Job.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
SQL Agent Job
Why this is correct
SQL Agent Jobs are the native scheduling mechanism in Azure SQL Managed Instance, supporting recurring T-SQL steps such as executing a stored procedure hourly. Unlike Azure Automation or Elastic Jobs, it runs in-instance with no external orchestrator, satisfying the hourly cleanup requirement directly.
- ✗
Azure Logic Apps with SQL connector
Why it's wrong here
Logic Apps runs on a schedule trigger but executes the T-SQL through a connector, adding latency and requiring a separate Azure resource outside the managed instance. It suits orchestrating multi-service workflows with conditions and approvals. Hourly in-database cleanup is served by the instance's own built-in job scheduling.
- ✗
Elastic Database Job
Why it's wrong here
Elastic Database Jobs target Azure SQL Database pools and require a job database plus credentials, and they are not the scheduling mechanism for Azure SQL Managed Instance. They are correct when coordinating T-SQL across many Azure SQL databases. A managed instance uses SQL Server Agent for recurring in-instance work.
- ✗
Azure Automation runbook with T-SQL
Why it's wrong here
An Azure Automation runbook executes T-SQL remotely over the network using a hybrid worker or the SQL connection, so it depends on external compute and connectivity rather than the instance itself. Automation suits cross-platform orchestration. Recurring in-database cleanup belongs to the instance's native agent scheduler.
Go deeper
Related to this question
Learn chapter
Implementing High Availability for Azure SQL Databases
Key term
Azure SQL Managed Instance
Azure SQL Managed Instance is a fully managed cloud database service that gives you nearly all the features of Microsoft SQL Server on your own server, without you having to manage the hardware or operating system.
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.