Q: 3
You have a Fabric workspace that contains a takehouse and a semantic model named Model1.
You use a notebook named Notebook1 to ingest and transform data from an external data source.
You need to execute Notebook1 as part of a data pipeline named Pipeline1. The process must meet
the following requirements:
• Run daily at 07:00 AM UTC.
• Attempt to retry Notebook1 twice if the notebook fails.
• After Notebook1 executes successfully, refresh Model1.
Which three actions should you perform? Each correct answer presents part of the solution. NOTE:
Each correct selection is worth one point.
Options
Discussion
Probably A, C, E. Pipeline has the main schedule and retry logic, and you only want the semantic model to refresh if the notebook finishes successfully. Pretty standard Fabric pipeline setup.
Scheduling and retries only make sense at the pipeline level, so E is correct here rather than D. On success (C) for the dependency makes sure Model1 only refreshes if Notebook1 runs without error. A, C, E are it, pretty sure.
A. C, E for sure. Retry set directly on Notebook activity (A), use On success to link model refresh (C), and Pipeline schedule controls time zone (E). Unless they want something wild with direct notebook scheduling, this covers it.
B tbh, but check the official docs and try out a pipeline in the portal if you can. Sometimes these depend on how Fabric implements orchestration and retry. Practice tests helped me spot how the timing settings work.
Option A, C, E here. D looks like a common trap since scheduling should be managed on Pipeline1 not Notebook1, and linking on success makes sure the refresh only kicks in if Notebook1 works. Pretty sure this is what Fabric expects but feel free to check.
Makes sense, it's definitely A, C, E. The retry and schedule need to be set at the pipeline, not notebook level. And using On success ensures you only refresh after Notebook1 succeeds. Don’t see D applying here.
A C E tbh, see similar picks in exam dumps and the official DP-700 guide backs this approach.
Why are folks picking B for dependency? On success (C) is what actually makes sure the refresh only happens if Notebook1 works, On completion could trigger it even on fail.
Option A, C, and E. Set retry on the Notebook activity (A), link refresh with On success (C), and schedule at the Pipeline level with UTC (E). That's how you'd meet all the requirements here. Open to corrections if I missed a detail.
A, C, E is right imo. Retry belongs on the Notebook activity (A) and the schedule should be set at the Pipeline level (E), not Notebook1. Linking refresh with On success (C) makes sure it only runs if Notebook1 succeeds. Pretty sure that's what MS expects here, open to others' views.
Be respectful. No spam.
