You add a PCF component for image upload to the model-driven app. The component consists of the default image and the Upload button. When you click on the button, the component opens a file browser and asks you to select an image for upload. After the upload, the chosen image is rendered within a control instead of the default image. 
You create the manifest file and implement the component logic in a Typescript TSImageComponent class and save it to the index.ts file. The code creates the button, renders the initial image, opens browsers for upload, and renders the selected image. 
What manifest node would you use to define the required use of the file browser?

Answer options:

A.data-set
B.control
C.resources
D.feature-usage
E.property
F.type-group

Correct Answer: D 
The Components are reusable blocks that help you develop the Power Apps applications. Power Apps provides out-of-the-box standard controls (components) for creating applications, like HTML Text, Vertical Gallery, or Edit Form. If your Power Platform solution requires more than standard controls, Power Apps also provides tools to create and reuse the custom code components. Power Apps Component Framework (PCF) is a foundation for building these components. 
The code components include three parts: Manifest — is an XML document that defines the component`s metadata.
Component implementation — contains the code of the component in the index.ts file that defines the UI and functionality. You can code using TypeScript or Javascript.
Resources — the files needed to construct the component visualizations. The resource files defined in the Manifest file are required for the component.
The Manifest consists of several nodes: control, type-group, property, data-set, resources, and feature-usage. 
The feature-usage node defines the features that are used in the component. Most of the feature implementation depends on the device. Therefore, the feature methods belong to the Device APIs of PCF. Here is the manifest’s definition of the required device’s file browser to select the image. 

The list of the Device features includes: captureAudio, captureImage, captureVideo, getBarcodeValue, getCurrentPosition, and pickFile. 
Except for the "Device" API, the developers can use "Utility" and "WebAPI" features. The Utility provides a container for getEntityMetadata, hasEntityPrivilege, and lookupObjects methods. The WebAPI provides properties and methods for records management. 
All other options are incorrect. 
For more information about PCF manifest files, please visit the below URLs: 

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/custom-controls-overview
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/device
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/sample-controls/webapi-control