PL-900 Demonstrate the capabilities of Power Apps Practice Question
You are troubleshooting a canvas app that loads slowly. The app uses over 50 data sources and many formulas. Which action is most likely to improve performance?
⚠ Common exam trap
The trap is thinking that increasing the data row limit or removing data sources is the primary fix, but the core issue is often non-delegable queries that pull excessive data; delegation is the most effective performance improvement.
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
✓
Use delegable queries to filter data at the source
Using delegable queries to filter data at the source reduces the amount of data retrieved from the data source, which significantly improves performance. When queries are delegable, the filtering and sorting are performed by the data source (e.g., SQL, SharePoint) rather than in Power Apps, minimizing data transfer and processing. This is especially important with many data sources and complex formulas.
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 for each data source
Why it's wrong here
Raising the data row limit increases the volume each data source retrieves, adding load rather than reducing it. The setting exists to fetch more records when an app genuinely needs them, but with 50 data sources the bottleneck is the number of connections and formula evaluations, not row ceilings.
- ✓
Use delegable queries to filter data at the source
Why this is correct
Delegable queries push filtering to the data source rather than pulling entire tables to the client, so the canvas app retrieves only matching records. With over 50 data sources, this sharply cuts the volume transferred and processed locally, directly addressing the slow loading caused by non-delegable operations.
- ✗
Disable the formula-level error checking
Why it's wrong here
Disabling formula-level error checking only suppresses compile-time warnings; it does not reduce the number of data sources, delegable queries or formula evaluations that drive load time. It is tempting because it speeds up authoring in Power Apps Studio, which is the correct choice when editing large apps becomes sluggish, not when runtime performance suffers.
- ✗
Remove unused data sources from the app
Why it's wrong here
Removing unused data sources reduces the number of connections the app establishes at startup, which is a genuine performance lever. However, the stem's slow load stems from excessive data sources and formulas combined; eliminating unused ones alone leaves the heavy formula and delegation load unaddressed.
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.