Building a reusable timer/buttons/icons block for custom pages with a canvas component

PL-400 By islever Editorial Last updated

Build Power Apps code apps

Short answer

B A canvas component in a component library lets you build the timer, buttons, and icons once and have changes cascade to every custom page.

Question

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?
  1. PCF control
  2. Canvas component Correct Answer
  3. Timer control
  4. Web resource

Key Takeaways

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.

Common mistake: 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.

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

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/page-canvas-components

This link opens the official vendor documentation in a new tab.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. ee4a55e 👍 4
    I also think it should be PCF control (A)
  2. Juan0414 👍 1 Answered B
    https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/page-canvas-components
  3. PRash3566 👍 4
    PCF Control

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Diagnosing the 'remote name could not be resolved' 404 for the Northwind Web API connector

S-grade

Solution for Long-Running Transactional Dataverse Operations

S-grade

Why exporting a custom connector directly from the maker portal fails to deploy it

S-grade

Preventing plug-in timeouts when calling a slow external web service

S-grade

Practice All PL-400 Questions

Access 85 questions with complete answers and detailed explanations.

View Full PL-400 Practice Test →

← Back to PL-400 Study Guide