Free Microsoft Data Engineering DP-700 Actual Exam Questions - Question 12 Discussion
HOTSPOT You have a Fabric workspace named Workspace1 that contains the items shown in the following table. 
For Model1, the Keep your Direct Lake data up to date option is disabled. You need to configure the execution of the items to meet the following requirements: Notebook1 must execute every weekday at 8:00 AM. Notebook2 must execute when a file is saved to an Azure Blob Storage container. Model1 must refresh when Notebook1 has executed successfully. How should you orchestrate each item? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
For Notebook1, scheduling it at 8 AM weekdays makes sense. Notebook2 should use the event trigger tied to the blob save. Model1 refresh looks like it needs a dependent trigger after Notebook1 runs successfully.
I agree with scheduling Notebook1 and event-triggering Notebook2; Model1 refresh depends on Notebook1’s success.
Since Model1’s auto-refresh is off, triggering it after Notebook1 finishes makes sense. For Notebook2, an event trigger on the blob storage save action fits perfectly. Scheduling Notebook1 on weekdays at 8 AM is straightforward.
I think the key detail is that disabling the "Keep your Direct Lake data up to date" on Model1 means it won’t refresh automatically based on source changes. So triggering Model1's refresh after Notebook1 makes sense because Notebook1 likely prepares or updates the data. For Notebook2, an event trigger tied specifically to the Azure Blob Storage container upload is the only way to meet the requirement of running on file save events, not a schedule. That leaves Notebook1 needing a scheduled weekday trigger at 8 AM. This setup fits all conditions logically without conflicts.
Model1 refresh can’t be event-triggered since the option is off; depends on Notebook1’s success.
For Notebook1, a schedule trigger on weekdays at 8:00 AM makes sense. Notebook2 should have an event trigger for blob storage changes. Model1 refresh depends on Notebook1’s successful run, so a dependent trigger fits best here.
I think Notebook1 should be scheduled with a daily trigger for weekdays, Notebook2 should use the event trigger tied to blob storage, and Model1’s refresh set to depend on Notebook1's success. This setup fits the requirements straightforwardly.