Courseiva
mediumMultiple Choice

PL-900 Practice Question: A Power Pages site uses Entity Lists to display…

A Power Pages site uses Entity Lists to display data from a Dataverse table. The requirement is that users should be able to click a row and navigate to a detail page for that record. What must be configured to enable this navigation?

⚠ Common exam trap

PL-900 often tests the confusion between Page Permissions, Web Roles, and the Details Page setting — candidates must recognize that only the Details Page setting directly enables row-click navigation.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Details page setting in the Entity List

In Power Pages, an Entity List can be configured with a 'Details Page' setting that specifies the target web page to navigate to when a user clicks a row. This setting, combined with the appropriate page permissions and web roles, enables the row-click navigation to a detail view.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Page permissions

    Why it's wrong here

    Page permissions govern which Dataverse records a web role can read, create, update or delete; they grant no row-click behaviour. They are tempting because Entity Lists do require table permissions to surface data at all, so they appear in every list configuration. Enabling navigation needs the list's target type and a detail page instead.

  • ✗

    List forms

    Why it's wrong here

    List forms define the create, edit and view forms used by an Entity List, but the click-through to a detail page is driven by the list's target type setting pointing at a web page. List forms are tempting because they do control record interaction, yet they govern form layout, not row navigation.

  • ✓

    Details page setting in the Entity List

    Why this is correct

    The Details page setting binds each Entity List row to a target web page and passes the record ID as a parameter, enabling row-click navigation to a detail view. Without this configured, rows render but remain non-clickable, so it directly satisfies the stated navigation requirement.

  • ✗

    Web roles

    Why it's wrong here

    Web roles grant table permissions to authenticated or anonymous users; they do not define row-click behaviour. They are tempting because every Entity List needs web roles and table permissions to return records, so they appear in any working list setup. Navigation instead requires the list's target type and a detail web page.

About these practice questions

This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Microsoft exam blueprint

This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.