The answer is an Azure Logic App with a recurrence trigger and a configured retry policy. This is the correct choice because Logic Apps natively support scheduled execution via the recurrence trigger and offer built-in retry policies that automatically re-run the workflow on failure, providing resilient maintenance task scheduling without custom code. On the Microsoft Azure Database Administrator Associate DP-300 exam, this scenario tests your understanding of Azure automation options for database maintenance, where the key trap is choosing Azure Automation Runbooks or Azure Functions—both require manual retry logic, while T-SQL Agent jobs lack native retry support. To remember this, think of Logic Apps as the "set-and-forget" solution: the recurrence trigger handles the schedule, and the retry policy handles the resilience, making it the most appropriate solution for a fault-tolerant Sunday 2:00 AM UTC task.
DP-300 Configure and manage automation of tasks Practice Question
This DP-300 practice question tests your understanding of configure and manage automation of tasks. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You manage an Azure SQL Database that must run a maintenance task every Sunday at 2:00 AM UTC. The task must be resilient to failures and automatically retry if it fails. You need to configure this using Azure automation. What is the most appropriate solution?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create an Azure Logic App with a recurrence trigger scheduled for Sunday at 2:00 AM UTC and configure a retry policy.
Option C is correct because Azure Logic Apps provides built-in retry policies and can be scheduled to run at specific times. Option A is wrong because Azure Automation Runbooks can be scheduled but require more custom error handling for retries. Option B is wrong because Azure Functions can be triggered by timer, but retry logic requires custom implementation. Option D is wrong because T-SQL Agent jobs in Azure SQL Database are limited and do not support retry policies natively.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Create an Azure Logic App with a recurrence trigger scheduled for Sunday at 2:00 AM UTC and configure a retry policy.
Why this is correct
Logic Apps provide built-in scheduling and retry policies.
Related concept
Static NAT maps one inside address to one outside address.
✗
Create an Azure Automation Runbook and schedule it to run weekly. Add custom error handling for retries.
Why it's wrong here
Runbooks can be scheduled but lack built-in retry policies.
✗
Use T-SQL Agent job in Azure SQL Database with a schedule and set up retry via Transact-SQL.
Why it's wrong here
T-SQL Agent in Azure SQL Database does not support retry policies.
✗
Create an Azure Function with a timer trigger and implement retry logic in code.
Why it's wrong here
Azure Functions require custom retry logic.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-300 NAT questions on configuration and troubleshooting.
Configure and manage automation of tasks — This question tests Configure and manage automation of tasks — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Create an Azure Logic App with a recurrence trigger scheduled for Sunday at 2:00 AM UTC and configure a retry policy. — Option C is correct because Azure Logic Apps provides built-in retry policies and can be scheduled to run at specific times. Option A is wrong because Azure Automation Runbooks can be scheduled but require more custom error handling for retries. Option B is wrong because Azure Functions can be triggered by timer, but retry logic requires custom implementation. Option D is wrong because T-SQL Agent jobs in Azure SQL Database are limited and do not support retry policies natively.
What should I do if I get this DP-300 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-300 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.