PL-900 Practice Question: Describe the business value of Microsoft Power Platform
Your organization has a Power Apps app that uses the Microsoft Dataverse connector. Users report that the app loads slowly. You review the app and find that it loads all records from a large table (over 500,000 rows) into a gallery. What is the best action to improve performance?
⚠ Common exam trap
Test-takers frequently confuse client-side caching or row limits with the core delegation concept, mistakenly believing that increasing limits or clearing caches solves performance issues, when the real solution is to ensure queries are processed on the server via delegable filters.
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 gallery's Items property to use a delegable filter, such as Filter(Table, Condition).
Modifying the gallery's Items property to use a delegable filter (e.g., Filter(Table, Condition)) ensures that the query is processed server-side by Microsoft Dataverse, retrieving only the subset of records that match the condition. This avoids loading all 500,000+ rows into the client app, which is the root cause of the slow performance. Delegation allows Power Apps to offload data processing to the data source, significantly reducing network payload and client memory usage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the data row limit in the app settings.
Why it's wrong here
Raising the row limit lets the gallery pull even more of the 500,000 rows, worsening load time and memory use. It is tempting because the limit appears to be the blocker, but the fix is delegating filtering and paging to Dataverse so only needed records are retrieved.
- ✓
Modify the gallery's Items property to use a delegable filter, such as Filter(Table, Condition).
Why this is correct
Delegable filters translate into Dataverse queries executed server-side, so only matching rows return to the app instead of all 500,000. This satisfies the performance constraint by avoiding the non-delegable row limit that forces client-side processing of the full table.
- ✗
Clear the app cache on the client devices.
Why it's wrong here
Clearing the client cache removes locally stored app data but does not change the query that retrieves all 500,000 rows, so load time stays the same. It is tempting because cache clearing resolves stale-data and sync issues, and would be the right action when users see outdated records rather than slow galleries.
- ✗
Reduce the delegation limit in the environment settings.
Why it's wrong here
Lowering the delegation limit restricts how many records Power Apps processes locally, so the gallery still requests the full 500,000 rows and performance worsens. It is tempting because delegation thresholds govern query behaviour, and raising them suits smaller datasets where non-delegable filters must run client-side.
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.