mediumMultiple Choice
PL-900 Practice Question: A Power Pages site has a form that submits data…
A Power Pages site has a form that submits data to Dataverse. Users report that the form is slow to load because it contains many lookup fields. What is the best practice to improve form load performance?
⚠ Common exam trap
Many candidates confuse performance improvements that affect the initial load (like reducing lookups) with features that affect interaction or filtering (like cascading lookups or FetchXML filters), leading them to choose options that only help after the form is already loaded.
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
✓
Reduce the number of lookup fields on the form.
Reducing the number of lookup fields directly decreases the number of separate database queries and network round-trips required to load the form. Each lookup field in a Power Pages form triggers an individual request to Dataverse to retrieve the related record's display name and metadata, so fewer lookups means fewer requests and faster load times.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Reduce the number of lookup fields on the form.
Why this is correct
Each lookup field on a Power Pages form triggers a separate Dataverse query to populate its options, so load time scales with lookup count. Reducing lookup fields directly cuts those round trips, satisfying the stem's performance constraint. Filtered or dependent lookups, caching, and asynchronous loading do not eliminate the per-lookup query overhead that causes the slowness.
- ✗
Disable the cascading lookup feature.
Why it's wrong here
Cascading lookups control filtering between related lookup fields, not the number of lookups rendered, so disabling them does not reduce the load caused by many lookup fields. It tempts because cascading behaviour adds queries, but limiting visible lookups on the form is the actual fix.
- ✗
Enable client-side caching for lookups.
Why it's wrong here
Caching stores lookup results client-side but does not reduce the number of lookup queries a form issues on initial load, so the delay persists. It is tempting because caching genuinely helps repeat lookups within a session, which would be the right fix if users repeatedly opened the same records.
- ✗
Add FetchXML filters to each lookup to limit results.
Why it's wrong here
FetchXML filters narrow the records each lookup returns, yet every lookup still executes its own query, so load time is unchanged. Filtering is tempting because it is the correct approach when lookups return excessive rows and the problem is result volume rather than the number of lookups.
Go deeper
Related to this question
About these practice questions
One of 701 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.