Building a reusable timer/buttons/icons block for custom pages with a canvas component
You are developing custom pages for a model-driven app. The app must display a timer control within a menu and include a mixture of buttons and icons. If a change is made to any of these elements, then the changes must cascade out automatically to all custom pages. You need to implement a solution. What should you implement?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Canvas components encapsulate layout and behavior and propagate changes to all consumers, which is the defining reason to use them here. A PCF control or web resource would not give the same automatic, low-code cascade across custom pages.
Custom pages need a timer control, buttons, and icons that stay in sync everywhere. A canvas component (maintained in a component library) is defined once and reused on every custom page; when you edit the component, every instance updates automatically — exactly the 'cascade' requirement.
Picking a PCF control (A) because both are 'reusable.' PCF controls are code components for model-driven apps, whereas custom pages are canvas-based; the automatic cascade to all custom pages is a canvas-component/component-library behavior, not a PCF behavior.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement that a change 'cascade out automatically to all custom pages' is the signature benefit of a canvas component stored in a component library. You design the timer, buttons, and icons once as a canvas component, drop it on each custom page, and any later edit to the component propagates to all instances without re-editing each page.Why the Other Options Are Wrong
A PCF control (A) is a code component aimed at model-driven apps and does not provide the same automatic, canvas-page-wide cascade described. A timer control (C) is just the single control, not a reusable composite. A web resource (D) is static HTML/JS and offers no built-in cascade to custom pages.Community Comment Notes
Juan0414 (likes=1) links the custom-page canvas-components documentation supporting canvas components. Some commenters (ee4a55e, PRash3566, each likes=4) guessed PCF, but the cascade requirement points to canvas components.Official Reference
Related Analysis
Practice All PL-400 Questions
Access 85 questions with complete answers and detailed explanations.
View Full PL-400 Practice Test →