The answer is to configure the job step’s ‘Retry attempts’ and ‘Retry interval (minutes)’ settings in the SQL Agent job step properties. This is correct because SQL Agent jobs in Azure SQL Database include native, built-in retry logic at the step level, allowing you to specify exactly how many times a failed step should be retried and how long to wait between attempts—no external services or custom code required. On the DP-300 exam, this question tests your knowledge of SQL Agent’s native capabilities versus relying on Azure Monitor alerts or Power Automate, which can notify or trigger retries but are not the direct, built-in solution. A common trap is assuming you need Azure Monitor or automation tools for retries, when the simplest answer is already inside the job step properties. Memory tip: think of the job step properties as the “one-stop shop” for retry—just set the numbers and let SQL Agent handle the rest.
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 have an Azure SQL Database that uses a SQL Agent job to run a critical ETL process every night. The job recently started failing intermittently. You need to automate the monitoring and alerting of job failures, and automatically retry the job twice with a 10-minute interval between retries. What should you configure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the job step's 'Retry attempts' and 'Retry interval (minutes)' settings in the SQL Agent job step properties.
Option C is correct because SQL Agent jobs have built-in retry settings in the job step properties. Option A is wrong because Azure Monitor alerts can notify but do not automatically retry the job. Option B is wrong because it would require custom logic. Option D is wrong because Power Automate can trigger retries but requires additional setup and is not native to SQL Agent.
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.
✗
Modify the job to use a T-SQL loop that checks job history and re-runs the job step.
Why it's wrong here
This requires custom T-SQL code and is not a native SQL Agent feature.
✗
Use Microsoft Power Automate to poll the job history and re-run the job if failed.
Why it's wrong here
Power Automate is external and not integrated with SQL Agent natively.
✗
Create an Azure Monitor alert on the job failure event and use a webhook to trigger a PowerShell script that retries the job.
Why it's wrong here
Azure Monitor alerts do not automatically retry the job; they only trigger notifications.
✓
Configure the job step's 'Retry attempts' and 'Retry interval (minutes)' settings in the SQL Agent job step properties.
Why this is correct
SQL Agent job steps have built-in retry configuration.
Related concept
Static NAT maps one inside address to one outside address.
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: Configure the job step's 'Retry attempts' and 'Retry interval (minutes)' settings in the SQL Agent job step properties. — Option C is correct because SQL Agent jobs have built-in retry settings in the job step properties. Option A is wrong because Azure Monitor alerts can notify but do not automatically retry the job. Option B is wrong because it would require custom logic. Option D is wrong because Power Automate can trigger retries but requires additional setup and is not native to SQL Agent.
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.