mediumMultiple Choice
Optimizing Power Apps Canvas App Performance Using Delegation in Dataverse
A sales team uses a Canvas app to track leads. Users report that the app loads slowly when accessing on mobile devices. Which component should be optimized to improve performance?
⚠ Common exam trap
Many candidates confuse cosmetic or metadata changes (version, icon, color) with performance optimizations, overlooking that data source efficiency is the root cause of slow loading in Canvas apps on mobile devices.
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
✓
Optimize data source connections and queries
Optimizing data source connections and queries directly reduces the amount of data transferred and the number of round trips between the Canvas app and its data source (e.g., Dataverse, SharePoint, SQL). On mobile devices, network latency and bandwidth are often constrained, so inefficient queries (e.g., loading all records instead of using filters) cause significant slowdowns. This is the primary performance lever for Canvas apps, as per Microsoft's guidance on app optimization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Update the app version number
Why it's wrong here
The version number is metadata used for solution packaging and update tracking; it does not alter how controls, data sources or OnStart logic execute at runtime. It is tempting because versioning appears in the app's settings and seems like a general maintenance action, but it is only relevant when publishing managed solutions.
- ✓
Optimize data source connections and queries
Why this is correct
Slow mobile loading typically stems from inefficient queries and excessive data retrieval over constrained networks. Optimising data source connections and queries reduces payload size and round trips, directly addressing the performance constraint rather than cosmetic UI changes.
- ✗
Increase the app icon size
Why it's wrong here
Icon size affects only the launcher tile's visual dimensions and adds no runtime overhead reduction; slow loading stems from inefficient queries, excessive controls or synchronous OnStart calls. It is tempting because icons are a visible mobile-facing asset, so resizing them feels like mobile optimisation, yet it changes nothing in the load path.
- ✗
Change the app's background color
Why it's wrong here
Background colour affects only visual rendering and has no bearing on data retrieval, control loading or delegation, so it cannot reduce mobile load times. It is tempting because cosmetic properties are simple to change in the Canvas designer, and a designer might assume any property tweak improves the user experience.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.