hardMultiple Choice
PL-900 Practice Question: A medium-sized company uses Power Platform to…
A medium-sized company uses Power Platform to manage its customer service operations. They have a model-driven app built on Dataverse that tracks cases and customer interactions. Recently, the app has been experiencing slow load times when users open a case record. The Dataverse environment is in the same region as the users. The app uses several business rules and calculated fields. The IT team suspects that the issue might be related to the number of components on the form. They want to optimize performance without disabling necessary functionality. The app is used by 50 customer service agents. What should the IT team do to improve form load times?
⚠ Common exam trap
Watch out — candidates often think adding calculated fields (Option B) or switching app types (Option D) are valid performance fixes, when in fact they either worsen the problem or miss the root cause of form component bloat.
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
✓
Remove unused fields and columns from the main form
Removing unused fields and columns from the main form reduces the amount of data retrieved and processed when a case record loads. Fewer form components mean fewer calls to Dataverse and less client-side rendering, directly improving load times without disabling necessary business rules or calculated fields.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Remove unused fields and columns from the main form
Why this is correct
Each field on a model-driven form triggers its own metadata retrieval and control rendering, so removing unused fields and columns reduces the payload Dataverse must assemble, directly improving case record load times without disabling business rules.
- ✗
Add more calculated fields to precompute values
Why it's wrong here
Calculated fields are computed at retrieval time, so adding more increases the real-time calculation load each time a record opens, worsening the slow form load. It is tempting because calculated fields remove the need for manual data entry and can precompute derived values, which helps reporting scenarios rather than interactive form rendering.
- ✗
Disable all business rules
Why it's wrong here
Disabling all business rules removes required validation and logic the agents depend on, violating the requirement to preserve necessary functionality while leaving the underlying form component count unchanged. It is tempting as a quick diagnostic to isolate rule-related slowdowns, but it is not a sustainable optimisation.
- ✗
Switch the app to a canvas app
Why it's wrong here
Canvas apps bind to Dataverse through connectors and do not use model-driven forms, so rebuilding does not remove the underlying form component load and abandons model-driven business logic. It is tempting when a bespoke, pixel-perfect interface is required, but it does not address Dataverse form performance.
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.