PL-300 Question 68

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose D3

  * Answer: D. Split the visuals onto multiple pages. * Explanation: - The PBIX file is 550 MB with 12 million rows and 25 visuals (15 AppSource + 10 default) on a single page. - Having too many visuals on one page causes slow rendering and query execution, especially in shared capacity. - Splitting visuals across multiple pages reduces the number of queries and visual rendering per page, improving performance. * Why not the others: - A. Change any DAX measures to use iterator functions → Iterators (SUMX, etc.) are usually slower than aggregators (SUM), so this would hurt performance. - B. Enable visual interactions → This adds complexity and more queries, not less. - C. Replace default visuals with AppSource visuals → AppSource visuals often perform worse than default visuals.

• Chose D2

  In case you are not sure about D, you could also simply dismiss the solutions A, B and C and this would confirm D solution A- there are not details about what measures are set for the report so not clear improving DAX measures would improve visuals load B- no indication visual interactions are disabled (by default they are not). In cas ethey would be disabled , enbling them I think would even make worse the visual interaction as there would be more details for PBI to take care of C-no details on what visuals are used in the report and what are the AppSource visuals either so again it's not clear how this could improve visual load (I would say default PBI visuals should have better performance than AppSource ones though) D- spliting all visuals onto multiple pages would result in redied number of visuals to be loaded/refreshed when users would be moving page to page, so this should improve visuals load

• Chose D1

  D - Split the visuals onto multiple pages