A marketing team wants to create a public Power Pages site to showcase upcoming events. They need to update event details frequently without developer assistance. What is the recommended approach?
Dataverse provides structured storage with a list component that renders records on the page, so marketers edit rows directly without developer involvement. This satisfies the frequent-update requirement while keeping the public site's event content maintainable by non-technical staff.
Why this answer
Power Pages integrates natively with Microsoft Dataverse, and list components can display Dataverse table records on a page. Storing event details in a Dataverse table lets marketing staff update records through model-driven apps or Power Apps without touching the portal's code, satisfying the no-developer requirement.
Exam trap
PL-900 often tests the misconception that SharePoint is the default data source for Power Pages — candidates familiar with SharePoint may pick it, but Dataverse is the native, recommended integration.
How to eliminate wrong answers
Option A is wrong because hardcoding event details in page source requires developer intervention for every update and is not maintainable. Option C is wrong because while SharePoint lists can be used as data sources in some Power Platform contexts, Power Pages' native and recommended data source is Dataverse; SharePoint integration adds complexity and is not the primary supported pattern for Power Pages lists. Option D is wrong because editing Liquid templates manually is a developer task and defeats the goal of frequent, no-code updates.