Configuring Exponential Backoff Retry in ADF Activities
An Azure Data Factory pipeline runs multiple times daily, loading data from an on-premises SQL Server to Azure Blob Storage. You notice that the pipeline sometimes fails due to transient network errors. You need to implement a retry policy with exponential backoff. Which configuration should you apply?
Quick Answer
The correct answer is to set the activity’s retry property to 3 and enable exponential backoff. This configuration is correct because exponential backoff retry in ADF activities automatically increases the delay between retries—typically doubling after each attempt—which prevents overwhelming the source system during transient network errors while still recovering quickly. On the Microsoft Azure Data Engineer Associate DP-203 exam, this scenario tests your understanding of the distinction between pipeline-level retry (simple fixed interval) and activity-level retry with exponential backoff, a common trap where candidates confuse the two. Remember that the activity’s retry property supports both a simple count and the exponential backoff toggle, while the retry secs property only sets a fixed wait time. A useful memory tip: “Activity retry with exponential backoff = smart recovery; pipeline retry = just try again.”
⚠ Common exam trap
Candidates may assume that exponential backoff is not supported, but it is now available as a configuration option for activity retries in Azure Data Factory.
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
✓
Set the activity's retry property to 3 and enable exponential backoff.
Azure Data Factory activity retry now supports exponential backoff. You can enable it by setting the retry property and enabling exponential backoff. Option B correctly configures 3 retries with exponential backoff. Option C only sets a fixed interval without exponential backoff. Options A and D are incorrect because retry is configured at the activity level, not pipeline or trigger level.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the pipeline's retry property to 3 and retry interval to 60 seconds.
Why it's wrong here
Incorrect because pipelines in Azure Data Factory do not have a retry property; retry is configured at the activity level.
- ✓
Set the activity's retry property to 3 and enable exponential backoff.
Why this is correct
Incorrect because Azure Data Factory activity retry does not support enabling exponential backoff; the retry interval is fixed. The option describes a non-existent configuration.
- ✗
Set the activity's retry property to 3 and retry secs to 60.
Why it's wrong here
Correct because this sets the activity's retry count to 3 and the fixed retry interval to 60 seconds, which is the available retry mechanism in Azure Data Factory.
- ✗
Set the trigger's retry policy to 3 with exponential backoff.
Why it's wrong here
Incorrect because triggers do not have a retry policy; retry must be set on the activity itself.
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
Learn chapter
Introduction to Azure Data Engineering
Key term
Data Transformation Pipelines
Data transformation pipelines are automated sequences of steps that take raw data from a source, clean and reshape it into a usable format, and then load it into a destination for analysis or storage.
Key term
Azure Data Factory
Azure Data Factory is a cloud-based data integration service that lets you create, schedule, and orchestrate data pipelines to move and transform data from various sources to destinations.
About these practice questions
This DP-203 question is part of Courseiva's 760-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on DP-203
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You have an Azure Data Factory pipeline that copies data from an FTP server to Azure Blob Storage. The pipeline runs successfully most of the time, but occasionally fails with a 'FTP server connection refused' error during peak hours. You need to minimize these failures with minimal cost. What should you do?
easy- ✓ A.Add a retry policy to the copy activity with a backoff interval.
- B.Set up Azure ExpressRoute to improve network reliability.
- C.Migrate the FTP server to SFTP.
- D.Increase the parallel copy count in the copy activity.
Why A: Adding a retry policy with a backoff interval handles transient connection issues. Option D is wrong because increasing parallel copies does not solve connection refused errors. Option B is wrong because Azure ExpressRoute is costly and unnecessary for FTP. Option C is wrong because migrating to SFTP may not resolve connection refused if the server is overloaded.
Variation 2. You are monitoring an Azure Data Factory pipeline that runs daily. You notice that some runs are failing due to transient network errors. You want to automatically retry the failed activities with a 5-minute delay, up to 3 times. How should you configure this?
easy- A.Set the pipeline's 'Concurrency' to 3 and 'Retry' to 1.
- B.Leave the default settings as they are because Azure Data Factory automatically retries failed activities 3 times.
- ✓ C.On each activity, set 'Retry' to 3 and 'Retry interval' to 00:05:00.
- D.Configure a 'Retry' policy on the pipeline itself, setting maximum retries to 3 and retry interval to 5 minutes.
Why C: Azure Data Factory activities have a 'Retry' property that can be set to 3, and 'Retry interval' to 00:05:00. Option A is too low (1 retry). Option B is wrong because retry is per activity, not at pipeline level. Option D is wrong because the default retry is 0.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 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-203 exam.