Exam PL-600 topic 1 question 63 discussion

allow view access for external customers > use SP List as Virtual Table Power Pages relies on Microsoft Dataverse for data storage and integration, we can use Canvas, but Model Driven is out of the Box (?)

if we use power pages, SPO lis can only be accessed via dataverse virtual table. so we have dataverse, then why not use model driven? - ok Canvas is to one shop to go with SPO...

Why not the others? A. Custom pages: These are used to enhance model-driven apps, not standalone apps or portals. C. Model-driven app: Requires data in Dataverse, not ideal for direct SharePoint list integration or external access.

B. Canvas app D. Power Pages

Even if you put an Iframe in the model driven app it's not the best approach to include SharePoint data, so Canvas App it's my choice. BD

If your data source is a SP List, then you need a canvas app. We cannot use a model-driven app because there is no dataverse. Power Pages is obv the answer for external view access

Here's why the other options are not as suitable: A. Custom pages: Custom pages are components within model-driven apps. While they offer some customization, they are primarily intended for use within the context of a model-driven app and are not ideal for providing external access to a SharePoint list. C. Model-driven app: Model-driven apps are built on top of Dataverse and are primarily designed for internal users within an organization. While you could technically expose a model-driven app externally, it's not the recommended approach, especially for simply providing view access to a SharePoint list. Managing external user access and licensing for a model-driven app would be more complex than using Power Pages.

1- External users: D. Power Pages 2- Employees: C. Model-driven app

external: Power Pages employees - internal, oob processes: model driven

external customer acces:portal using existing processes: model driven (BPF)