Exam PL-600 topic 2 question 45 discussion

I would choose C+D. It seems that B and E are excluded according to https://learn.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve#limitations-of-virtual-tables And A according to https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-virtual-entities

Requirements that cannot be fully met with virtual tables: B. Assign security role access to tables at the user level: Virtual tables do not support row-level security (e.g., user-level access) because the data is not stored in Dataverse. C. Add and update data: Most virtual tables are read-only unless the external data source and the virtual table provider support CRUD operations. Azure SQL virtual tables can support updates, but this requires custom providers or OData endpoints with write support. E. Audit updates to the data: Since the data is not stored in Dataverse, auditing does not apply to virtual tables.

Correct answer is BD

C & D is correct. Do not be confused about virtual tables. You cannot "Add and Update" data into dataverse because it basically acts as a pointer, but you can certainly add and update data; it just goes directly to the the external data source. That's the entire point of Virtual Tables. So you can create a model driven app with forms to add and update data so it updates the actual source. This helps in where you do not have to create a 2 way data sync. But, unfortunately Virtual tables features still do not exist in the PowerApps GCC (Government) or above environment. Trust, I feel this pain everyday in having to maintain 2 way syncs to Dataverse. Hopefully soon VT will be available.

Correct answer is CD

We have to choose options for virtual table in PP and only you can do B and D.

Links from camp test are it!

Which two requirements can you meet by using virtual tables? B and D would mean that 'virtual tables' are the means to assign 'security roles'? i don't get that. virtual tables primary means is to relate to other data in different systems. maybe A) in a very loos interpretation of 'change tracking' you add the change to the virtual table and this tracks the change. or to see 'track' the changes happening in the other system. but not like 'change tracking' like auditing. very weird wording.

B and D

My answer are B and D because a user can't modify the information on a virtual table, they can just read the information, so all the other option relate to some change can be done on the data. A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.

Everything you need in those two links, thanks camptest, saved me searching for the right links. https://learn.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve#limitations-of-virtual-tables https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-virtual-entities

Answe is AE