HOTSPOT -
You have an Azure Data Factory pipeline that has the activities shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: succeed -
Box 2: failed -
Example:
Now let's say we have a pipeline with 3 activities, where Activity1 has a success path to Activity2 and a failure path to Activity3. If Activity1 fails and Activity3 succeeds, the pipeline will fail. The presence of the success path alongside the failure path changes the outcome reported by the pipeline, even though the activity executions from the pipeline are the same as the previous scenario.
Activity1 fails, Activity2 is skipped, and Activity3 succeeds. The pipeline reports failure.
Reference:
https://datasavvy.me/2021/02/18/azure-data-factory-activity-failures-and-pipeline-outcomes/
The answers are correct. The second question is "failed" because web1 has both a success and failed path. web1 would have to have only a failed path for the second question to be considered successful.
Agree. Second is "Fail" because Success connector presented.
Second should also be succeeded.
The second answer should be "Succeeded". You are providing false information to other members. The reason why it is a success is because Set Variable 2 happened because of the failure of Web 1. Therefore, this red pipeline is deedmed a success.
You are incorrect. https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#do-if-else-block
Yes, as Wanchihh mentions, you are wrong. Upper branch status are fail => skipped => skipped. According to the logic in the url below, this is deemed as a failed pipeline.
where did you find skipped?
This was on my test on 26-Jun with 930+ score, I chose Succeeded for both. Test it for first one I'm damn sure its succeed and for second one also kind of sure
The second answer should be Succeeded as 'Set Variable 2' has failed dependency on Web1.
It should be Suceeded in both. The reference article says: The failure dependency means this pipeline reports success.
Updated: Correct ans as 1. Success and 2. Failed The failure dependency means this pipeline reports success. But, the presence of the success path alongside the failure path changes the outcome reported by the pipeline: Web-1 fails, Set-var-1 is skipped, and Set-var-2 succeeds --> The pipeline reports failure.
See https://docs.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#do-if-else-block
This is all you need for the right answer. Its well explained in the link.
Agreed!
I agree with you too
The answer is correct! It's actually pretty neat how ADF determines that. If an activity fails but there was a subsequent OnSuccess activity that never runs, it's a fail. To handle that, you also need an OnSkipped activity to follow the OnSuccess activity in case it never ran! https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#do-if-else-block
Thanks @chryckie for this explanation. Finally it's clear!
There are so many wrong high voted answers. READ THIS.
Using this microsfot doc: https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#try-catch-block that claims ""We determine pipeline success and failures as follows: -)Evaluate outcome for all leaves activities. If a leaf activity was skipped, we evaluate its parent activity instead -)Pipeline result is success if and only if all nodes evaluated succeed"" I used this logic When web1 activity fails: node setVariable2 succeeds and setVariable1 is skipped and its parent node web1 failed; overall pipeline fails
second box should be succeeded https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#do-if-skip-else-block
Both should be succeed https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling#summary-table
1. Success and 2. Failed
In any scenario pipeline will show success status, cause we are catching the failure
The answers are correct.
when PL has a success and fail path if any of those completes the PL is succeeded. So second is succeeded
as of skip - it is used in debug mode
Both Success
Both are success 100% sure about this
I think both are successful bcz i think when web activity fail it will pass to the set variable and the purpose of the set varible will beCOMPLETED so pipeline will be success
Do If Skip Else block In this approach, customer defines the business logic, and defines both the Upon Failure path, and Upon Success path, with a dummy Upon Skipped activity attached. This approach renders pipeline succeeds, if Upon Failure path succeeds.