cert
cert-1
cert-2

Pass Microsoft PL-200 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
PL-200 Exam - Verified By Experts
PL-200 Premium Bundle
$29.98

PL-200 Premium Bundle

$79.99
$109.97
  • Premium File 328 Questions & Answers. Last update: Nov 02, 2026
  • Training Course 94 Video Lectures
  • Study Guide 800 Pages
 
$109.97
$79.99
accept 10 downloads in last 7 days
block-screenshots
Purchase Microsoft PL-200 Exam Training Products Individually
Microsoft PL-200 Premium File
Premium File 328 Q&A
$76.99$69.99
Microsoft PL-200 Video Training Course
Training Course 94 Lectures
$21.99 $19.99
Microsoft PL-200 PDF Study Guide
Study Guide 800 Pages
$21.99 $19.99
Microsoft PL-200 Practice Test 32

Question 310

A Microsoft Power Platform deployment team observes: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. Which TWO complementary steps are appropriate: the recommended configuration action and its most direct independent verification evidence? Select TWO answers.

  1. Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts.
  2. Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows.
  3. Build a supported custom page and configure navigation or record context using the intended model-driven application framework.
  4. Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list.
  5. Inspect the command definition, selection context, relevant Power Fx formulas and test cases for permitted and denied users.

Explanation

Correct Answers

A:

The most direct evidence is: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

B:

The required configuration response is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Incorrect Answers

C:

This response applies to the different subject of Model-driven custom pages and navigation, rather than directly to Power Pages table permissions and relationship scopes: Build a supported custom page and configure navigation or record context using the intended model-driven application framework.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

D:

This is an unsafe or unsupported shortcut: Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list. It fails to address Power Pages table permissions and relationship scopes. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

E:

This response applies to the different subject of Power Fx modern model-driven commanding, rather than directly to Power Pages table permissions and relationship scopes: Inspect the command definition, selection context, relevant Power Fx formulas and test cases for permitted and denied users.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Question 311

A business process owner describes this situation: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. Which evidence is MOST useful to verify the root issue rather than an unrelated feature? Select ONE best answer.

  1. Inspect the command definition, selection context, relevant Power Fx formulas and test cases for permitted and denied users.
  2. Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list.
  3. Inspect list and form table bindings, query behavior, portal contact identity and table-permission tests.
  4. Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts.

Explanation

Correct Answer

D:

The most direct evidence is: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Incorrect Answers

A:

This response applies to the different subject of Power Fx modern model-driven commanding, rather than directly to Power Pages table permissions and relationship scopes: Inspect the command definition, selection context, relevant Power Fx formulas and test cases for permitted and denied users.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

B:

This is an unsafe or unsupported shortcut: Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list. It fails to address Power Pages table permissions and relationship scopes. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

C:

This response applies to the different subject of Power Pages forms and lists on Dataverse, rather than directly to Power Pages table permissions and relationship scopes: Inspect list and form table bindings, query behavior, portal contact identity and table-permission tests.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Question 312

A Power Platform functional consultant receives this requirement: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. Which observable result BEST demonstrates that the requirement has been implemented successfully? Select ONE best answer.

  1. A signed-in test contact sees and edits only permitted rows through functional site components.
  2. A direct visit to protected content succeeds only for authorized web roles, regardless of menu visibility.
  3. Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.
  4. Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list.

Explanation

Correct Answer

C:

This is the observable acceptance result: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Incorrect Answers

A:

This response applies to the different subject of Power Pages forms and lists on Dataverse, rather than directly to Power Pages table permissions and relationship scopes: A signed-in test contact sees and edits only permitted rows through functional site components.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

B:

This response applies to the different subject of Power Pages page access and web role control, rather than directly to Power Pages table permissions and relationship scopes: A direct visit to protected content succeeds only for authorized web roles, regardless of menu visibility.. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

D:

This is an unsafe or unsupported shortcut: Grant the Anonymous Users web role Global read permission to a confidential table merely to fix an empty portal list. It fails to address Power Pages table permissions and relationship scopes. In this scenario: A portal list displays an access-denied result despite page access being allowed, because no Dataverse table permission exists. The relevant technical behavior is: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access. The appropriate implementation is: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows. Independent validation: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts. Accept only when: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Question 313

A Dataverse and business-apps implementation review finds: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. Which implementation action BEST meets the requirement? Select ONE best answer.

  1. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  2. Configure the supported Power BI dashboard or report integration and validate user permissions, licensing and refresh behavior.
  3. Invoke a properly shared cloud flow with explicit validated parameters and handle returned result and failure in the canvas interface.
  4. Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately.

Explanation

Correct Answer

D:

The required configuration response is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

B:

This response applies to the different subject of Power BI reports embedded in model-driven apps, rather than directly to Power Pages external identity and authentication: Configure the supported Power BI dashboard or report integration and validate user permissions, licensing and refresh behavior.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

C:

This response applies to the different subject of Canvas calling Power Automate cloud flows, rather than directly to Power Pages external identity and authentication: Invoke a properly shared cloud flow with explicit validated parameters and handle returned result and failure in the canvas interface.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 314

During user acceptance testing for a Power Platform solution: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. Which platform principle BEST explains the correct design decision? Select ONE best answer.

  1. Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing.
  2. Power Pages forms and lists expose Dataverse data through configured site components; component placement does not itself grant record access.
  3. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  4. A canvas app can call an associated Power Automate flow, but parameters, user connections and response contracts must be intentionally designed.

Explanation

Correct Answer

A:

The platform behavior that governs this design is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

B:

This response applies to the different subject of Power Pages forms and lists on Dataverse, rather than directly to Power Pages external identity and authentication: Power Pages forms and lists expose Dataverse data through configured site components; component placement does not itself grant record access.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

C:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

This response applies to the different subject of Canvas calling Power Automate cloud flows, rather than directly to Power Pages external identity and authentication: A canvas app can call an associated Power Automate flow, but parameters, user connections and response contracts must be intentionally designed.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 315

An organization asks its low-code implementation team to resolve the following: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. Which evidence is MOST useful to verify the root issue rather than an unrelated feature? Select ONE best answer.

  1. Inspect the step sequence, parent row references, search scope, upload target and anonymous/authenticated role tests.
  2. Inspect report workspace permissions, app component settings, dataset refresh, identity and representative viewer experience.
  3. Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions.
  4. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.

Explanation

Correct Answer

C:

The most direct evidence is: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This response applies to the different subject of Power Pages multistep forms search and documents, rather than directly to Power Pages external identity and authentication: Inspect the step sequence, parent row references, search scope, upload target and anonymous/authenticated role tests.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

B:

This response applies to the different subject of Power BI reports embedded in model-driven apps, rather than directly to Power Pages external identity and authentication: Inspect report workspace permissions, app component settings, dataset refresh, identity and representative viewer experience.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 316

A Microsoft Power Platform deployment team observes: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. Which observable result BEST demonstrates that the requirement has been implemented successfully? Select ONE best answer.

  1. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  2. Authorized users see current intended visuals while unauthorized users cannot retrieve restricted report data.
  3. Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.
  4. Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.

Explanation

Correct Answer

C:

This is the observable acceptance result: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

B:

This response applies to the different subject of Power BI reports embedded in model-driven apps, rather than directly to Power Pages external identity and authentication: Authorized users see current intended visuals while unauthorized users cannot retrieve restricted report data.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

This response applies to the different subject of Power Pages table permissions and relationship scopes, rather than directly to Power Pages external identity and authentication: Each contact reads or changes only the permitted Dataverse records, including related child rows, and protected rows remain inaccessible.. In this scenario: An external partner needs sign-in to a portal and the developer proposes making every visitor a Dataverse system user. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 317

A business process owner describes this situation: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. Which implementation action BEST meets the requirement? Select ONE best answer.

  1. Configure Power Pages list and form components against the intended Dataverse table and supported permissions.
  2. Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately.
  3. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  4. Configure the supported Power BI dashboard or report integration and validate user permissions, licensing and refresh behavior.

Explanation

Correct Answer

B:

The required configuration response is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This response applies to the different subject of Power Pages forms and lists on Dataverse, rather than directly to Power Pages external identity and authentication: Configure Power Pages list and form components against the intended Dataverse table and supported permissions.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

C:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

This response applies to the different subject of Power BI reports embedded in model-driven apps, rather than directly to Power Pages external identity and authentication: Configure the supported Power BI dashboard or report integration and validate user permissions, licensing and refresh behavior.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 318

A Power Platform functional consultant receives this requirement: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. Which platform principle BEST explains the correct design decision? Select ONE best answer.

  1. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  2. Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access.
  3. Page access control governs access to page resources, while visible navigation and table data permissions are separate concerns.
  4. Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing.

Explanation

Correct Answer

D:

The platform behavior that governs this design is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

B:

This response applies to the different subject of Power Pages table permissions and relationship scopes, rather than directly to Power Pages external identity and authentication: Portal table permissions control Dataverse row operations independently from page visibility, and their access scope determines which related rows a contact may access.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

C:

This response applies to the different subject of Power Pages page access and web role control, rather than directly to Power Pages external identity and authentication: Page access control governs access to page resources, while visible navigation and table data permissions are separate concerns.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 319

A Dataverse and business-apps implementation review finds: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. Which evidence is MOST useful to verify the root issue rather than an unrelated feature? Select ONE best answer.

  1. Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions.
  2. Inspect custom page placement, navigation parameters, user-role access and rendered app behavior for representative records.
  3. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.
  4. Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts.

Explanation

Correct Answer

A:

The most direct evidence is: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

B:

This response applies to the different subject of Model-driven custom pages and navigation, rather than directly to Power Pages external identity and authentication: Inspect custom page placement, navigation parameters, user-role access and rendered app behavior for representative records.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

C:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

This response applies to the different subject of Power Pages table permissions and relationship scopes, rather than directly to Power Pages external identity and authentication: Inspect table permission scopes, related lookup columns, associated roles and direct list or Web API access as two test contacts.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Question 320

During user acceptance testing for a Power Platform solution: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. Which TWO complementary steps are appropriate: the recommended configuration action and its most direct independent verification evidence? Select TWO answers.

  1. Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows.
  2. Inspect report workspace permissions, app component settings, dataset refresh, identity and representative viewer experience.
  3. Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions.
  4. Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately.
  5. Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables.

Explanation

Correct Answers

C:

The most direct evidence is: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

D:

The required configuration response is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Incorrect Answers

A:

This response applies to the different subject of Power Pages table permissions and relationship scopes, rather than directly to Power Pages external identity and authentication: Assign correctly scoped Power Pages table permissions to web roles and test contact, account or parent relationships against real rows.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

B:

This response applies to the different subject of Power BI reports embedded in model-driven apps, rather than directly to Power Pages external identity and authentication: Inspect report workspace permissions, app component settings, dataset refresh, identity and representative viewer experience.. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

E:

This is an unsafe or unsupported shortcut: Assume a portal sign-in automatically creates a privileged internal Dataverse user with unrestricted access to all tables. It fails to address Power Pages external identity and authentication. In this scenario: A portal site changes its identity provider but contacts become duplicated due to incorrect identity mapping. The relevant technical behavior is: Portal external users are represented through contact-linked identities and web roles; Power Pages authentication differs from model-driven app user licensing. The appropriate implementation is: Select supported Power Pages identity providers and configure authentication plus contact mapping and role assignment appropriately. Independent validation: Inspect identity-provider configuration, contact association, authentication redirects and access for signed-in versus guest sessions. Accept only when: Partners sign in to their existing authorized contact records while public pages remain available and sensitive data stays restricted.

Microsoft Power Platform Functional Consultant (PL-200) Practice Tests