Study Databricks DA-ASSOC Sharing, Refresh, and Alerts: key concepts, common traps, and exam decision cues.
Once the dashboard is correct, the next question is how people consume it. The exam checks whether you can reason about sharing, embedding, refresh scheduling, and alerts without mixing them together.
| Need | Best first answer |
|---|---|
| workspace users or groups need access | dashboard sharing permissions |
| external users need access | shareable link or supported external sharing pattern |
| app needs to display the dashboard | embedding |
| dashboard should refresh on a schedule | automatic refresh |
| notify someone when a threshold is crossed | alert |
| Piece | What it really means |
|---|---|
| source query | the data being evaluated |
| threshold or condition | the rule that triggers the alert |
| destination | where the notification goes |
| schedule | when Databricks checks the condition |
| Trap | Better rule |
|---|---|
| using a dashboard alone when the question asks for notification | alert is the threshold-notification feature |
| assuming refresh and alert are the same thing | refresh updates data; alert evaluates a condition and can notify |
| ignoring sharing mode in an external-consumption question | workspace sharing, external links, and embedding are different routes |
This lesson usually tests whether you can separate seeing fresh data from getting notified about conditions. Refresh updates what the dashboard shows. Alerts evaluate whether a threshold condition has been met and notify someone. DA-ASSOC often rewards keeping those two actions distinct instead of treating them as the same feature.