Exam DP-203 topic 2 question 56 discussion

Actual exam question from Microsoft's DP-203

Question #: 56
Topic #: 2

You have an Azure Data Factory pipeline that performs an incremental load of source data to an Azure Data Lake Storage Gen2 account.
Data to be loaded is identified by a column named LastUpdatedDate in the source table.
You plan to execute the pipeline every four hours.
You need to ensure that the pipeline execution meets the following requirements:
✑ Automatically retries the execution when the pipeline run fails due to concurrency or throttling limits.
✑ Supports backfilling existing data in the table.
Which type of trigger should you use?

A. event
B. on-demand
C. schedule
D. tumbling window

Show Suggested Answer

Suggested Answer: D 🗳️

by Canary_2021 at Dec. 25, 2021, 3 a.m.

Comments

Submit Cancel

Canary_2021

Highly Voted 2 years, 7 months ago

Selected Answer: D

D is correct answer. https://www.sqlshack.com/how-to-schedule-azure-data-factory-pipeline-executions-using-triggers/ Azure Data Factory pipeline executions using Triggers: • Schedule Trigger: The schedule trigger is used to execute the Azure Data Factory pipelines on a wall-clock schedule. • Tumbling Window Trigger: Can be used to process history data. Also can define Delay, Max concurrency, retry policy etc. • Event-Based Triggers : The event-based trigger executes the pipelines in response to a blob-related event, such as creating or deleting a blob file, in an Azure Blob Storage

upvoted 27 times

...

steveo123

Most Recent 1 year, 1 month ago

Selected Answer: D

D is correct.

upvoted 1 times

...

Ankit_Az

1 year, 2 months ago

Selected Answer: D

Correct. As soon as you see backfill, its tumbling.

upvoted 1 times

...

Deeksha1234

1 year, 12 months ago

Selected Answer: D

D is correct

upvoted 1 times

...

Sriramiyer92

2 years ago

(D) Tumbling window trigger https://docs.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#tumbling-window-trigger Retry capability: Is Supported. Failed pipeline runs have a default retry policy of 0, or a policy that's specified by the user in the trigger definition. Automatically retries when the pipeline runs fail due to concurrency/server/throttling limits (that is, status codes 400: User Error, 429: Too many requests, and 500: Internal Server error).

upvoted 3 times

...

dev2dev

2 years, 6 months ago

Selected Answer: D

D is correct. Tumbling Window has more advance options for setting retry and concurrency policies which schedule doesnt have.

upvoted 2 times

...