PL-600 · Question #169
You are designing an integration between an Azure SQL database and a model-driven app. You have the following requirements: - Audit updates to the data. - Assign security role access to tables at…
The correct answer is C. Add and update data. D. Assign security role access to tables at the organization level. Virtual tables in Dataverse allow for CUD (Create, Update, Delete) operations on external data and support security role access at the organization level.
Question
Options
- AEnable change tracking.
- BAssign security role access to tables at the user level.
- CAdd and update data.
- DAssign security role access to tables at the organization level.
- EAudit updates to the data.
How the community answered
(17 responses)- A12% (2)
- B6% (1)
- C76% (13)
- E6% (1)
Why each option
Virtual tables in Dataverse allow for CUD (Create, Update, Delete) operations on external data and support security role access at the organization level.
Virtual tables do not support Dataverse's built-in change tracking capabilities as the data resides externally in the Azure SQL database.
Virtual tables do not support row-level or user-level security directly from Dataverse; security is typically managed at the organization level or within the external data source.
Virtual tables support CUD (Create, Update, Delete) operations, enabling users to add and update data in the external Azure SQL database through the model-driven app.
Security role access can be assigned to virtual tables at the organization level, allowing all users with the appropriate role to access the external data.
Virtual tables do not support Dataverse's built-in auditing features, as the actual data updates and audit trails occur within the external system.
Concept tested: Dataverse Virtual Table Capabilities
Source: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/create-edit-virtual-tables
Topics
Community Discussion
No community discussion yet for this question.