Drag and Drop Question A company plans to use Microsoft Power Platform to modernize their business. Sales commissions are given only to the representatives who sell items from a designated category…

Question

Exhibit

Answer Area

Explanation

The question tests understanding of Dataverse table ownership types and their implications for data security management, specifically matching objects like manufacturer, model, and inventory to the most appropriate table types to minimize security management effort.

Approach. Drag 'Organization-owned standard table' to 'Item manufacturer' and 'Item model'. Drag 'User-owned standard table' to 'Item inventory'.

Common mistakes.

• common_mistake. Dragging 'User-owned standard table' to 'Item manufacturer' or 'Item model' would be incorrect because these are generally global data types that don't require record-level ownership for security. Assigning ownership to each manufacturer or model record would add unnecessary management overhead. Dragging 'Organization-owned standard table' to 'Item inventory' would make it difficult to implement the required record-level security for sales commissions without significant custom development or complex filtering, thus increasing security management effort. Dragging 'Activity table' or 'Virtual table' to any of these objects is incorrect as they serve different purposes: 'Activity tables' are for tracking actions, and 'Virtual tables' are for external data integration, neither of which directly addresses the core data storage and security requirements for these business objects.

Concept tested. Dataverse table ownership types (Organization-owned vs. User-owned) and their implications for implementing record-level security and minimizing administrative effort in Microsoft Power Platform.

No community discussion yet for this question.