Power Platform Components for SharePoint and External Access
You are designing a Microsoft Power Platform solution for a customer. The customer is developing an application that needs to use an existing Microsoft SharePoint list. The application must be able to: • allow view access for external customers. • use out-of-the-box processes for access for employees. You need to recommend components for the application. Which two components should you recommend? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Community Votes
67% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core trap is confusing Model-driven apps (which require Dataverse) with Canvas apps (which can connect directly to SharePoint). Additionally, recognizing Power Pages as the dedicated portal solution for external users is critical.
This question evaluates the selection of appropriate Power Platform components to integrate with SharePoint lists while supporting both internal employees and external customers. The solution requires a canvas app for internal data manipulation and Power Pages for secure external viewing.
Many candidates choose Option C (Model-driven app) because it handles business processes well, but they fail to realize that Model-driven apps are built on Dataverse and do not natively support direct SharePoint list integration without complex workarounds.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct components are Canvas App (B) and Power Pages (D). A Canvas app is ideal for connecting directly to existing data sources like SharePoint lists, allowing custom UI design for employee workflows. Power Pages is Microsoft's dedicated low-code portal solution designed specifically for providing secure web access to external users (customers) who do not have Microsoft Entra ID licenses.Why the Other Options Are Wrong
Option A (Custom pages) are sub-components within Model-driven apps, not standalone solutions for this scenario. Option C (Model-driven app) is incorrect because it relies on the Dataverse platform; it cannot directly consume a SharePoint list as its primary data source in the way required here, making it unsuitable for an existing SharePoint-based architecture.Community Comment Notes
Community consensus heavily favored BD, with several users noting that "If your data source is a SP List, then you need a canvas app" due to the lack of native Dataverse support in SharePoint lists. Others highlighted that Power Pages is the obvious choice for external access, reinforcing the split between internal (Canvas) and external (Power Pages) needs.Exam Strategy
Always check the underlying data model first. If the requirement mentions 'existing SharePoint' or 'Excel', think Canvas Apps. If it mentions 'Dataverse' or 'built-in security models', think Model-driven Apps. For external portals, Power Pages is the standard answer.
Frequently Asked Questions
Why can't I use a Model-driven app with SharePoint?
Model-driven apps are built on Dataverse. While connectors exist, they are not native to the same degree as Canvas apps, and SharePoint is not a supported primary data source for Model-driven app creation.
Is Power Pages free for external users?
No, Power Pages requires specific licensing for external visitors. It is distinct from standard Power Apps which rely on user-specific licenses.