Exam PL-600 topic 3 question 16 discussion

Actual exam question from Microsoft's PL-600

Question #: 16
Topic #: 3

You are a Microsoft Power Platform architect supporting the go live phase of a canvas app. The canvas app accesses data on premises and in the cloud.

Users are reporting the app is very slow to respond, especially upon initial launch.

You need to optimize the performance of the app.

Which three actions should you complete? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

A. Move data calls from the OnStart event to the OnLoad event.
B. Move data calls from the OnLoad event to the OnStart event.
C. Increase data row limits.
D. Review the settings of the data gateway for on-premises data sources.
E. Reduce data row limits.

Show Suggested Answer

Suggested Answer: ADE 🗳️

by MrWood47 at Feb. 23, 2023, 5:58 p.m.

Comments

Submit Cancel

MrWood47

Highly Voted 1 year, 10 months ago

Selected Answer: ADE

Correct!

upvoted 7 times

...

stalex

Highly Voted 1 year, 4 months ago

Selected Answer: BDE

The others users are right: there is no onLoad event in a canvas app: this is also confirmed by Bing AI search: https://sl.bing.net/es7jYEacx3I. While asking ChatGpt which is better - A or B - it says B. But when pointing to chatgpt that onload event does not exist the response is still B and probably the answer is written poorly. ChatGPT explanation: The original options should be revised as follows: A. Move data calls from the "OnVisible" property to the "OnStart" property. B. Move data calls from the "OnStart" property to the "OnVisible" property. The recommendation from my previous response still holds true: you should move data calls from the "OnVisible" property to the "OnStart" property. So I vote for BDE (B probably is written differently)

upvoted 5 times

...

loftuscheek

Most Recent 3 months ago

Selected Answer: BDE

it's BDE dont believe the hype: OnStart vs. OnLoad: OnStart runs once when the app launches, making it ideal for pre-loading critical data (e.g., user settings, reference tables) that is needed globally. OnLoad fires every time a screen is loaded, leading to repeated data calls if used for non-screen-specific data. This redundancy slows down navigation. Performance Gains: Centralizing data calls in OnStart with Concurrent() allows parallel data fetching during app initialization, hiding latency behind the app’s loading screen.

upvoted 2 times

loftuscheek

3 months ago

best way to increase performance is to move to onStart and use "Concurent"

upvoted 1 times

loftuscheek

3 months ago

"upon initial launch" both are called Onstart and Onload(first screen) , moving from ONstart to Onload will make it worse

upvoted 1 times

...

naoms

3 months, 2 weeks ago

Selected Answer: ADE

The options are incorrect, but... A.Move data calls from the OnStart event to the "OnVisible" event. https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/common-performance-issue-resolutions

upvoted 2 times

...