Exam PL-400 topic 1 question 35 discussion

While timelines (activity controls) can affect performance, they are not a control type you typically evaluate in the same way as quick view forms, iFrames, or lookups. Also, timeline is more of a form component than a standalone control type that can be optimized directly.

The correct answers are: **B. quick view form**, **C. iFrame**, and **D. lookup**. ### Explanation: To improve form loading performance in a model-driven app, you should use lightweight controls that load efficiently or defer loading until needed: 1. **B. Quick View Form** – Displays related entity data without loading a separate form, reducing initial load time. 2. **C. iFrame** – Can be configured to load asynchronously (lazy load), preventing delays in the main form rendering. 3. **D. Lookup** – Efficiently retrieves related records without embedding heavy controls. ### Why not **A. Timeline**? - The timeline control can be resource-intensive and slow to load, especially with many activities. It is **not** recommended for performance optimization. ### Best Practices: - Replace heavy controls (like timelines, subgrids with many records) with quick views or lookups. - Use asynchronous loading for iFrames. - Minimize the number of tabs and sections to reduce rendering time. **Final Answer:** **B, C, D**

✅ A. Timeline ✔️ Correct — Timeline controls (like Activities) can significantly impact performance, especially if there are many related records. It's recommended to defer loading or limit the data shown. ✅ B. Quick View Form ✔️ Correct — Quick View Forms load related entity data, and if used excessively or inefficiently, they can slow down form loading. Evaluate how many are being used and optimize their data source and visibility rules. ✅ C. iFrame ✔️ Correct — iFrames load external content which can delay form rendering depending on the page being loaded. Avoid loading them on the main form tab if not necessary. ❌ D. Lookup ❌ Incorrect — Lookup controls by themselves do not significantly impact load time unless they're configured with complex filtering logic or have performance issues in the related entity.

This is a very confusing and tricky question. All of these controls are mentioned in the documentation as factors that may affect performance (https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/design-performant-forms#data-driven-controls). So, based on the documentation timeline and quick view form must be for sure, but iFrame and Lookup are in the same category of controls "that are less impactful than the data-driven controls but can still participate in the above layout strategy in order to achieve the best performance". So, I choose iFrame because based on experiences, it may causes more issues than lookup fields

GPT ❌ A. Timeline Timeline Controls display activity records (emails, notes, tasks) related to a record. Performance Impact: Timeline loads are deferred, meaning they load after the main form has finished loading. It doesn’t significantly affect the initial load performance. Optimization Tip: Not a primary control to adjust for performance issues.

Every control in this issue affects performance! I think the wording of the question is unclear. It is completely unclear what needs to be done. By the way, I research a piece of information: "An IFrame control embeds content from another website or application within the form. This can significantly impact loading performance due to the need to load external content. It is generally not recommended for use in forms where performance is a concern." According to this if we have problems with the performance I would not use iFrame as it is not recommended for heavy pages. However, I don't urge anyone to listen to me. This is just my opinion.

I believe all could be relevant for the loading performance. But could it be as simple as A, C and D, because "Qucik View Form" is not.. directly a control? Its supposed to be Quick View Control? haha...

Correct for me