A company is considering implementing Power Platform. The company must minimize development costs. For which three scenarios should you consider implementing Power Apps Portals? Each correct answer presents a complete solution.

Power Apps Portals are designed to create external-facing websites that allow users outside an organization (e.g., customers, partners, community members) to interact with data stored in Microsoft Dataverse. Using portals for these scenarios significantly minimizes development costs compared to traditional custom web development by leveraging low-code templates and pre-built functionalities. A (Customer support website): This is a primary use case, supported by the Customer Self-Service portal template. B (Public community website): This aligns with the Community portal template, which includes features like forums and blogs for public engagement. D (Secure vendor website): This is a classic partner/vendor portal scenario, allowing secure, authenticated access for external stakeholders to relevant Dataverse data.

C: An application for internal users on a VPN is best built as a standard Power App (Canvas or Model-driven), which is designed and licensed for internal employee use. E: An internal website for employees is the primary use case for standard Power Apps (Canvas or Model-driven), not Power Apps Portals, which are optimized for external users.

1. Microsoft Learn

"What is Power Apps portals?": This document states

"Create external-facing websites that allow users outside your organization to sign in... and create and view data in Microsoft Dataverse." It explicitly lists templates that align with the correct answers: "Customer self-service portal" (supports option A)

"Partner portal" (supports option D)

and "Community portal" (supports option B).

2. Microsoft Learn

"PL-900: Introduction to Power Apps portals": This module in the official PL-900 learning path specifies

"Power Apps portals allow organizations to create websites which can be shared with users external to their organization either anonymously or through a commercial authentication provider." This directly contrasts with the internal user scenarios described in options C and E.

3. Microsoft Learn

"Portal application lifecycle management": In the "Portal development" section

the documentation outlines scenarios focusing on external audiences

such as "Customer Service

" "Partner Management

" and "Event Management

" reinforcing that the intended use is for non-employee access.