Northern Trail Outfitters has the Case Object set to private. The support manager raised a concern the reps have a boarder view of data than expected and can see all cases on their groups…

Question

Options

• ADashboard Filters
• BDashboard Subscriptions
• CDynamic Dashboards
• DPublic Dashboards.

• A
  10% (2)
• B
  20% (4)
• C
  65% (13)
• D
  5% (1)

Explanation

Dynamic Dashboards (C) run as a specific user - typically an admin or manager - meaning all viewers see data through that user's access level, bypassing the Case object's private sharing model. Even though reps shouldn't see all cases based on OWD settings, the dashboard renders data as if they were the "run as" user, exposing records they'd never access directly.

• A (Dashboard Filters) - Filters narrow down what's displayed; they don't expand data access beyond what the running user can already see.
• B (Dashboard Subscriptions) - Subscriptions schedule dashboard snapshots to be emailed; they don't change who the data is visible to or override sharing rules.
• D (Public Dashboards) - Salesforce doesn't have a "Public Dashboard" feature in the same sense; public folder access controls visibility of the dashboard itself, not the underlying record data permissions.

Memory tip: Think "Dynamic = Dangerous" - Dynamic Dashboards dynamically impersonate a fixed user, so they can silently blow past field/object-level sharing. On the exam, whenever you see a mismatch between OWD/sharing rules and what users actually see on dashboards, Dynamic Dashboards are the prime suspect.

No community discussion yet for this question.