Power Pages Security Configuration for Store Managers
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are building a Power Pages site for a supermarket chain. The company plans to have the managers of individual stores use the site. Managers will authenticate on the site each week by using their corporate identity to update stock information for their store. Managers must be able to add and update stock information for their store only. You need to configure the site security. Solution: Configure table permissions. Does the solution meet the goal?
Community Votes
60% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The trap is assuming web roles alone are sufficient; however, table permissions are the mechanism that actually enforces record-level restrictions in Power Pages.
This question tests the correct configuration of security for a Power Pages site using table permissions. The solution meets the goal because table permissions restrict access to specific Dataverse records based on roles.
Many learners select 'No' (Option B), mistakenly believing that configuring table permissions is insufficient without explicitly mentioning web roles, or they overlook that table permissions are the primary control for data access.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Configuring table permissions is the correct and necessary step to meet the stated goals. In Microsoft Power Pages, table permissions are used to define which users can read, write, create, or delete records in Dataverse tables. By associating these permissions with the appropriate web roles (which represent the store managers), you ensure that each manager can only access and modify stock information relevant to their own store.Why the Other Options Are Wrong
Selecting 'No' implies that table permissions cannot achieve this goal. However, while web roles are required to group users, it is the table permissions that enforce the actual data boundaries (record-level security). Without table permissions, there is no restriction on what data a user can view or edit, regardless of their role.Community Comment Notes
The community is divided, but the most accurate comments support the 'Yes' verdict. One commenter correctly noted that table permissions allow control over access based on user roles. Another highlighted that access to Dataverse records is automatically restricted when using forms and lists, provided table permissions are configured. Comments suggesting 'No' often confuse the requirement of having both roles and permissions, missing the fact that the solution presented is the valid method to secure the data.Official Reference
Exam Strategy
When evaluating security configurations in Power Pages, always look for 'table permissions' as the key component for record-level access control. Remember that while roles identify who the user is, permissions define what they can do with specific data.
Frequently Asked Questions
Why is Option B incorrect in this scenario?
Option B is incorrect because table permissions are indeed the correct mechanism to enforce record-level security in Power Pages.
Do I need web roles if I have table permissions?
Yes, table permissions must be associated with web roles to apply the restrictions to the specific users (managers).