PL-900 - Describe Microsoft Power Apps (30% of the exam) - Section 3.2

Describe model-driven apps and how they are built on Dataverse with structured layouts.

Describe model-driven apps as structured apps generated from Dataverse metadata, configured through the model-driven app designer with views, forms, and dashboards. Distinguish model-driven apps from canvas apps, and explain how business process flows guide users through multi-step processes.

model-driven app designerviews and formsbusiness process flowsdashboardsDataverse-based apps

Practice question for this objective

Free sampleDescribe Microsoft Power Appsmedium

A sales operations team is composing a model-driven app in the app designer and wants to add components to their Dataverse tables. Which components can they add to tables when building a model-driven app? (Select 3 answers)

AForms, used to enter and edit records Correct
BViews, used to list and filter records Correct
CDashboards, used to surface charts and data Correct
DConnectors, used to reach external data sources
EPower Fx formulas, used to set control properties

Model-driven apps are built by adding forms, views, charts, and dashboards to Dataverse tables in the app designer. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.

Why A is correct: Correct. Forms, used to enter and edit records is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.

Why B is correct: Correct. Views, used to list and filter records is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.

Why C is correct: Correct. Dashboards, used to surface charts and data is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.

Why D is wrong: Connectors are how canvas apps reach more than 200 data sources; model-driven apps use the Dataverse data model and do not add connectors as table components.

Why E is wrong: Power Fx expressions drive control properties in canvas apps; model-driven design is no-code and component-focused, so formulas are not the components added to tables.

See more PL-900 practice questions, answers explained.

Exam traps in Describe Microsoft Power Apps

Answers that look right on this material and are not. Each one is a distractor from a different question in the PL-900 bank for this domain.

They give the maker full control over the layout of every screen on a blank design surface
Why it is wrong: Full control over layout on a blank surface describes canvas apps; in model-driven apps much of the interface is determined by the components added, so layout control is limited.
A formula bar expression
Why it is wrong: The formula bar is where you set properties such as Items; it is part of authoring, not a data source you connect to with a connector.
A personal view, which she saves from the command bar and then shares with each buyer who needs it
Why it is wrong: Tempting because personal views can be shared, but a personal view is owned by one individual and is only visible to that person unless explicitly shared, so it is not the way to make a list available to all app users.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.