PL-100 · Question #258
Drag and Drop Question Multiple departments in your organization use a model-driven app to manage corporate data. Users from one department request that all their department's custom tables be…
The correct answer is Create a new area for the department.; Create a new group for the department.; Create a new subarea for the department. The question tests knowledge of model-driven app site map hierarchy, requiring the correct sequence to create a new area, group, and subarea for department-specific custom tables.
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Create a new area for the department.
- Create a new group for the department.
- Create a new subarea for the department.
Explanation
The question tests knowledge of model-driven app site map hierarchy, requiring the correct sequence to create a new area, group, and subarea for department-specific custom tables.
Approach. The scenario requires separating a department's custom tables into their own area within a model-driven app. This involves updating the app's site map. The site map in a model-driven app has a hierarchical structure: Area > Group > Subarea. To establish a new dedicated section for the department's tables, these components must be created in the correct sequence. First, a 'new area' is needed to serve as the top-level container for the department's content. Second, within that area, a 'new group' is typically created to logically organize related subareas. Finally, a 'new subarea' is created within the group to link directly to the department's custom tables (entities) or other relevant content. Therefore, the correct sequence of actions is: 1. Create a new area for the department. 2. Create a new group for the department. 3. Create a new subarea for the department.
Common mistakes.
- common_mistake. A common mistake would be to include 'Create a dashboard for the department.' in the sequence or to arrange the selected actions in an incorrect order. While dashboards can be subareas, the primary request is to separate custom tables using their own area. Creating a dashboard is not a direct or mandatory step to establish the fundamental hierarchical navigation for entity lists. Placing actions out of sequence, such as creating a subarea before a group or a group before an area, would also be incorrect because the site map navigation structure must follow the Area-Group-Subarea hierarchy.
Concept tested. The underlying technical concept being tested is the understanding of the site map structure and navigation hierarchy in Microsoft Power Apps model-driven apps, specifically the roles and relationships of Areas, Groups, and Subareas in organizing and presenting app content.
Topics
Community Discussion
No community discussion yet for this question.
