Does Local Authentication Secure a Power Pages Site for Store Managers?

PL-200 By islever Editorial Last updated

Short answer

B Local authentication does not meet the goal; use a Power Pages external identity provider such as Microsoft Entra ID for corporate sign-in.

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are building a Power Pages site for a supermarket chain. The company plans to have the managers of individual stores use the site. Managers will authenticate on the site each week by using their corporate identity to update stock information for their store. Managers must be able to add and update stock information for their store only. You need to configure the site security. Solution: Use local authentication. Does the solution meet the goal?
  1. Yes
  2. No Correct Answer

Key Takeaways

This question tests whether local authentication satisfies a corporate-identity requirement in Power Pages; the trap is assuming that any working sign-in method meets the goal when the requirement explicitly demands corporate credentials.

Power Pages local authentication creates its own username and password accounts instead of validating the supermarket managers' corporate identity, so it cannot satisfy the weekly corporate sign-in requirement. The page confirms the solution does not meet the goal (B) and points to an external identity provider such as Microsoft Entra ID.

Common mistake: Choosing 'Yes' because local authentication sounds simpler; it ignores that managers must authenticate with their corporate identity, which locally stored Power Pages accounts cannot assert or federate with the company directory.

Expert Analysis

Why the Answer Is Correct

The solution fails because Power Pages local authentication creates and stores its own username and password in the site's contact records rather than validating the supermarket managers' corporate identity. The requirement states managers will authenticate each week using their corporate identity, which means the site must federate with the company directory, typically Microsoft Entra ID (Azure AD). Local authentication provides no trust relationship with that directory, so it cannot prove who the manager is within the corporate tenant. Additionally, local authentication is not recommended for production Power Pages sites because it shifts credential management and security to the site itself. Therefore 'No' (B) is the correct judgment.

Why the Other Options Are Wrong

Option A ('Yes') is wrong because it treats any sign-in mechanism as sufficient and ignores the explicit corporate-identity requirement. Choosing local authentication would create separate local credentials for each store manager and would not let the organization enforce its existing conditional access, MFA, or lifecycle controls. The stock-update restriction also needs authorization configuration, but authentication is the first unmet requirement; even a perfect table-permission setup would not fix the wrong identity provider. Because local authentication does not satisfy the stated goal, 'Yes' cannot be correct.

Community Comment Notes

As businesselements1 explains, Power Pages local authentication is built on ASP.NET Identity and lets users register with a local username and password or sign in through an external provider, and they note "this has nothing to do with adding/updating stock info." killionb12 states "Local authentication is not recommended for Power Pages sites" and recommends an external identity provider such as Azure AD or Azure AD B2C for secure and scalable corporate authentication. 4443f01 simply agrees with businesselements1. The community consensus aligns with the source key: local authentication is the wrong mechanism here, so the solution does not meet the goal.

Official Reference

https://learn.microsoft.com/en-us/power-pages/security/authentication/

This link opens the official vendor documentation in a new tab.

Exam Strategy

Read the identity requirement literally: 'corporate identity' points to federation with the company directory, not to locally stored credentials. In Power Pages and Power Platform questions, local authentication rarely satisfies enterprise scenarios, so choose the external identity provider option.

Frequently Asked Questions

Why is local authentication wrong for Power Pages store managers?

Local authentication issues its own username and password, so it cannot validate the managers' corporate identity or enable Microsoft Entra ID-based weekly sign-in.

How do I restrict managers to their own store's stock records?

Use Power Pages web roles and table permissions so each authenticated manager can only read and update rows tied to their store.

More PL-200 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. businesselements1 👍 2
    --NO--Returning site visitors can authenticate using local user credentials or external identity provider accounts. A new visitor can register for a user account either by providing a username and password or by signing in through an external provider.==> Power Pages provides authentication functionality built on the ASP.NET Identity API. ==> this has nothing to do with adding/updating stock info by managers. https://learn.microsoft.com/en-us/power-pages/security/authentication/set-authentication-identity
  2. killionb12 👍 1 Answered B
    No, using local authentication does not meet the goal (Option B). Local authentication is not recommended for Power Pages sites, especially when corporate identity authentication is required. Instead, you should use an external identity provider like Azure Active Directory (Azure AD) or Azure AD B2C. These providers offer secure and scalable authentication solutions that align with the requirement for managers to use their corporate identity
  3. 4443f01 👍 1 Answered B
    I agree with businesselements1

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How Do You Lock a Power Pages Chatbot to Entra ID Users?

S-grade

Preventing Table Display Name Changes in UAT

S-grade

Minimizing Dataverse Storage with SharePoint Integration

S-grade

Power Apps Environment Variable Resolution in Managed Solutions

S-grade

← Back to PL-200 Study Guide