mediumMultiple Choice
PL-900 Practice Question: Build a public-facing website for customer…
A company plans to build a public-facing website for customer support using Power Pages. They need to enable customers to view their open support tickets and submit new ones. What must be configured in the Power Pages design studio?
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
✓
Add a list and a form component bound to a Dataverse table
Power Pages design studio provides list and form components that can be bound directly to a Dataverse table to display and submit data. Option A is incorrect because embedding a canvas app is not a built-in component in Power Pages design studio; it would require custom development. Option B is incorrect because while you can use custom web templates with Dataverse connectors, it is not the standard or recommended approach for simple view/submit scenarios, and it is not a configuration in the design studio. Option D is incorrect because Power Automate flows are not components in the Power Pages design studio; they can be triggered but are not used for direct data viewing or submission.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Embed a canvas app
Why it's wrong here
A canvas app embedded in a page runs its own Power Apps session and cannot expose Dataverse ticket records to anonymous portal visitors. It is tempting because canvas apps build rich custom interfaces, and it would be correct for internal authenticated users needing bespoke app functionality.
- ✗
Configure a Dataverse connector in a custom web template
Why it's wrong here
Dataverse connectors belong to Power Apps and Power Automate, not the Power Pages design studio, which binds pages to Dataverse through built-in table permissions and basic forms rather than custom connector web templates. It is tempting because connectors genuinely integrate Dataverse elsewhere, but here the requirement is a customer-facing list and submission form, configured directly as a Dataverse-backed basic form.
- ✓
Add a list and a form component bound to a Dataverse table
Why this is correct
A list component renders Dataverse records, letting customers view their open tickets, while a form component bound to the same table handles submission of new tickets. Binding both to Dataverse satisfies the requirement to read and write support ticket data on the public site.
- ✗
Create a Power Automate flow
Why it's wrong here
Power Automate flows run background automation; they cannot render a customer-facing list of tickets or a submission form on a webpage. It is tempting because flows are the standard way to automate Dataverse record processing, and would be the right choice for triggering notifications or approvals after a ticket is created, not for building the interactive page itself.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.