PL-900 Demonstrate the capabilities of Power Apps Practice Question
Which THREE components are part of a model-driven app? (Choose three.)
⚠ Common exam trap
A common pitfall is selecting 'Screens' because they are prominent in canvas apps, but model-driven apps use forms and views instead.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Forms
In Power Apps, a model-driven app is composed of metadata-driven components rendered by the platform, and Forms (A) are one of them: they define the data-entry and display layout for a table's records, with types like Main, Quick Create, and Card forms. Views (B) are also core components, since they define how lists of records are filtered, sorted, and displayed in the app's grids. The Sitemap (E) is the component that defines the app's navigation structure, organizing tables, views, and other elements into areas, groups, and subareas shown in the app. Screens (C) belong to canvas apps, where the maker drags-and-drops UI controls onto a blank canvas, not to model-driven apps. Triggers (D) are not a model-driven app component; event-driven logic in model-driven apps is implemented through business rules, workflows, plug-ins, or Power Automate, not a 'Triggers' building block.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Forms
Why this is correct
Forms are a core component of model-driven apps, rendering the data model for user interaction. They satisfy the stem's requirement by binding directly to Microsoft Dataverse tables, defining how records are displayed and edited. Alongside views and charts, forms constitute the standard interface building blocks generated from the underlying data structure.
- ✓
Views
Why this is correct
Views define how records from a table are displayed and filtered, controlling columns, sorting and filtering criteria. They satisfy the model-driven app requirement by shaping the data presentation layer built on Microsoft Dataverse tables, letting makers surface relevant rows without writing code.
- ✗
Screens
Why it's wrong here
Screens are a canvas app component; model-driven apps are composed from tables, forms, views, charts, dashboards and app modules instead. It tempts because canvas apps are built by arranging screens, and both app types live inside the same Power Apps maker experience.
- ✗
Triggers
Why it's wrong here
Triggers belong to Power Automate cloud flows, not model-driven apps, whose components are tables, forms, views, charts, dashboards and business process flows. It tempts because triggers genuinely initiate automation, and model-driven apps commonly invoke flows that begin with one.
- ✓
Sitemap
Why this is correct
A sitemap defines the navigation structure of a model-driven app, controlling which tables, dashboards, and custom pages appear and how they are grouped. It is a required app component, satisfying the stem's constraint that the answer must be part of a model-driven app rather than shared platform infrastructure.
Go deeper
Related to this question
About these practice questions
One of 701 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.