Quick Answer
The answer is Dataverse tables, sitemap, and forms. These three components are required because a model-driven app in Power Apps is fundamentally a metadata-driven architecture: Dataverse tables provide the structured data schema and business logic, the sitemap defines the app’s navigation structure and which tables are accessible, and forms serve as the primary interface for viewing and editing individual records. On the Microsoft Power Platform Fundamentals PL-900 exam, this question tests your understanding of the core building blocks that differentiate model-driven apps from canvas apps. A common trap is selecting views or charts instead of forms, but remember that while views and charts are important, they are not mandatory—forms are the only required UI component because every record must have a form to be created or edited. A helpful memory tip is to think of the acronym “TSF” (Tables, Sitemap, Forms) as “The Simple Foundation” of any model-driven app.
This PL-900 practice question tests your understanding of demonstrate the capabilities of power apps. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE components are required to build a model-driven app in Power Apps? (Choose three.)
Dataverse tables
Tables define the data structure for the app.
Canvas controls
Why wrong: Canvas controls are for canvas apps, not model-driven apps.
Power Automate flows
Why wrong: Flows are optional and not required for a model-driven app.
Sitemap
Sitemap defines the navigation structure.
Forms
Forms provide the UI for viewing and editing data.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Dataverse tables
Dataverse tables are the core data storage and management layer in model-driven apps. They provide the structured schema, relationships, and business logic (such as calculated columns and rollups) that model-driven apps rely on for data operations. Without Dataverse tables, there is no data source to bind forms, views, or the sitemap to, making them a mandatory component.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Dataverse tables
Why this is correct
Tables define the data structure for the app.
Related concept
Read the scenario before looking for a memorised answer.
Canvas controls
Why it's wrong here
Canvas controls are for canvas apps, not model-driven apps.
Power Automate flows
Why it's wrong here
Flows are optional and not required for a model-driven app.
Sitemap
Why this is correct
Sitemap defines the navigation structure.
Related concept
Read the scenario before looking for a memorised answer.
Forms
Why this is correct
Forms provide the UI for viewing and editing data.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse canvas controls (used in canvas apps) with the form components of model-driven apps, or assume Power Automate flows are a core structural requirement rather than an optional add-on.
Detailed technical explanation
Under the hood, a model-driven app is defined by an app module that references a Dataverse environment, a sitemap (SiteMap.xml) that defines navigation, and one or more forms (Form XML) that define the UI layout for each table. The sitemap uses a hierarchical structure of areas, groups, and subareas to map to specific entity views and dashboards, while forms are stored as customizations in the Dataverse solution and are rendered server-side. A real-world scenario: when building a sales pipeline app, you must first create an Opportunity table (Dataverse), design a main form with fields and subgrids, and configure a sitemap so users can navigate to the Opportunity list and open records.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Demonstrate the capabilities of Power Apps — study guide chapter
Learn the concepts, then practise the questions
Demonstrate the capabilities of Power Apps practice questions
Targeted practice on this topic area only
All PL-900 questions
976 questions across all exam domains
Microsoft Power Platform Fundamentals PL-900 study guide
Full concept coverage aligned to exam objectives
PL-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PL-900 questions linked to Identify foundational components of Power Platform.
Practise PL-900 questions linked to Demonstrate capabilities of Power BI.
Practise PL-900 questions linked to Describe complementary Microsoft Power Platform solutions.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Automate.
Practise PL-900 questions linked to Describe the business value of Microsoft Power Platform.
Practise PL-900 questions linked to Manage the Microsoft Power Platform environment.
Practise PL-900 questions linked to Identify foundational components of Microsoft Power Platform.
Practise PL-900 questions linked to Demonstrate the capabilities of Power BI.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Apps.
Practise PL-900 questions linked to Demonstrate the capabilities of Microsoft Copilot Studio.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Pages.
Practise PL-900 questions linked to PL-900 fundamentals.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Demonstrate the capabilities of Power Apps — This question tests Demonstrate the capabilities of Power Apps — Read the scenario before looking for a memorised answer..
The correct answer is: Dataverse tables — Dataverse tables are the core data storage and management layer in model-driven apps. They provide the structured schema, relationships, and business logic (such as calculated columns and rollups) that model-driven apps rely on for data operations. Without Dataverse tables, there is no data source to bind forms, views, or the sitemap to, making them a mandatory component.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which THREE components are required to build a model-driven app in Power Apps? (Select three.)
hardWhy A: Option A is correct because tables in Dataverse are the foundation. Option C is correct because forms define how data is displayed and edited. Option E is correct because views define the list of records. Option B is wrong because canvas apps are separate. Option D is wrong because flows are automations, not required for the app itself.
Variation 2. Which THREE components are required to build a model-driven app in Power Apps? (Choose three.)
easyWhy A: Options A, C, and D are correct because a model-driven app requires a Dataverse database, tables, and views. Option B is wrong because flows are optional. Option E is wrong because canvas apps are a different type.
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.