PL 400 PCF Controls (Power Apps Component Framework)

Question 1

What is the primary purpose of the Power Apps Component Framework (PCF)?

Accepted Answer

To create custom, reusable UI controls for canvas and model-driven apps

Answer

PCF enables pro developers to build custom, reusable UI controls that extend the default controls available in Power Apps canvas and model-driven apps.

Question 2

Which Power Apps CLI command is used to initialize a new PCF component project?

Accepted Answer

pac pcf create

Answer

The `pac pcf create` command scaffolds a new PCF project with the required folder structure, manifest, and TypeScript stub files.

Question 3

Which file serves as the contract between a PCF control and its host application by declaring properties and resources?

Accepted Answer

ControlManifest.Input.xml

Answer

ControlManifest.Input.xml defines the PCF control's properties, resources, and metadata that the host application uses to bind data and load the control.

Question 4

Which TypeScript interface must every PCF control class implement?

Accepted Answer

ComponentFramework.StandardControl<IInputs, IOutputs>

Answer

All PCF controls must implement `ComponentFramework.StandardControl<IInputs, IOutputs>`, which mandates the required lifecycle methods: init, updateView, getOutputs, and destroy.

Question 5

What is the role of the `init` method in a PCF control's lifecycle?

Accepted Answer

To create DOM elements, set initial state, and register event listeners the first time the control loads

Answer

The `init` method is invoked exactly once during a control's lifetime and is used to build the initial DOM structure, configure event listeners, and perform any one-time setup.

(PL 400) Microsoft Certified Power Platform Developer Associate Practice Test

(PL 400) Microsoft Certified Power Platform Developer Associate Practice Test

PL 400 PCF Controls (Power Apps Component Framework)