Filtering and Securing Records in Model-Driven Apps
Short answer
CE Apply security roles to restrict view access and Configure view filters to limit displayed records in the model-driven app.
Question
Sales representatives report that too many records are displayed, including inactive and unrelated accounts where the sales representative isn't the record owner.
You need to ensure only relevant records are displayed for the users.
What are two ways to complete the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Key Takeaways
The trap is confusing column visibility with record visibility; you must use both View Filters for data criteria and Security Roles for ownership/access boundaries.
Learn how to restrict record visibility in Microsoft Power Platform model-driven apps using view filters and security roles to show only relevant data.
Common mistake: Choosing 'Configure record status columns' because the problem mentions inactive records, but this option only affects display formatting, not the actual filtering logic.
Expert Analysis
The requirement is to limit the dataset displayed in a model-driven app view so that sales representatives only see relevant records, specifically excluding inactive accounts and those where they are not the owner. This involves two distinct layers of data visibility control: filtering based on record attributes and restricting access based on user permissions.
Option E, configuring view filters, addresses the first part of the problem. By adding filter conditions to the view definition (e.g., Status Code = Active), you ensure that inactive records are never returned in the query results, regardless of who views them. This is a direct solution to the "too many records" issue caused by irrelevant data states.
Option C, applying security roles, addresses the second part. Dataverse security roles define what users can do with records and which records they can see. By assigning appropriate security roles that restrict read access to records owned by the user or within their team hierarchy, you prevent users from seeing unrelated accounts they do not own. This enforces the ownership constraint mentioned in the scenario.
Option A (Define view columns) only changes which fields are visible, not which records appear. Option B (Configure app settings) generally controls UI behavior like theme or startup pages, not specific record visibility per view. Option D (Configure record status columns) relates to how status values are displayed or managed, not to filtering logic. Therefore, combining view-level filtering with role-based security provides the complete solution.
Official Reference
- https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-security-role
- https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/edit-view#add-filters-to-a-view
- https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/security-overview
These links open the official vendor documentation in a new tab.
Exam Strategy
When asked to limit data visibility, always check if the question implies both 'what data' (filters) and 'who sees it' (security). In model-driven apps, views control the query scope, while security roles control the row-level access. Combine these two mechanisms for comprehensive data governance solutions.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
exam_upskill 👍 1C. Apply security roles to restrict view access. E. Configure view filters.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.