hardMultiple Choice
PL-900 Practice Question: A Power Pages site is experiencing slow load…
A Power Pages site is experiencing slow load times for a page that displays a list of products from a Dataverse table. The page uses a Liquid template with a fetch query that retrieves all products without filtering. Which change would most improve performance?
⚠ Common exam trap
The trap is reaching for infrastructure-level fixes (CDN, caching) when the question explicitly describes an inefficient query — candidates must identify that the root cause is the unfiltered fetch, not delivery or caching.
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
✓
Modify the fetch query in the Liquid template to include a filter, such as only active products.
The Liquid template's fetch query retrieves all products from Dataverse without filtering, which means the server must query and render the entire table on every page load. Adding a filter such as 'only active products' reduces the result set returned by Dataverse, cutting query execution time and the amount of data transferred and rendered. This directly addresses the root cause of the slow load time — an inefficient, unbounded data retrieval — rather than masking it with caching or CDN.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable the content delivery network (CDN) for the site.
Why it's wrong here
A CDN caches static assets like images, scripts and stylesheets; it cannot reduce the Dataverse query cost of an unfiltered fetch returning every product row. It is tempting because CDNs genuinely accelerate page delivery, which is the right choice when slowness stems from static asset latency rather than query volume.
- ✗
Adjust the page caching settings in the Power Pages admin center.
Why it's wrong here
Page caching stores rendered output, but the underlying unfiltered fetch still executes on cache misses and returns the full product set. It is tempting because caching settings do reduce repeated rendering work, which is correct when the same page is requested unchanged by many anonymous users.
- ✗
Replace the Liquid template with the out-of-the-box list component.
Why it's wrong here
The out-of-the-box list component still queries Dataverse and offers no advantage over a fetch that returns every row; the unfiltered retrieval remains. It is tempting because list components handle paging and rendering automatically, which is correct when the problem is presentation rather than query scope.
- ✓
Modify the fetch query in the Liquid template to include a filter, such as only active products.
Why this is correct
Adding a filter to the fetch query reduces the number of rows Dataverse returns and Liquid renders, cutting server-side processing and payload size. This directly addresses the unfiltered retrieval causing slow load times for the product list.
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 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.