Overview
Domain 3 accounts for 20–25% of PL-900 and has two functional groups. Describe Power Apps capabilities and use cases asks about canvas apps, model-driven apps, Plan designer and code apps. Describe how to build basic apps by using Power Apps asks how AI creates a canvas app, how AI creates a model-driven app, and how to create AI-powered apps with the vibe experience.
The July 2026 revision replaced the older hands-on groups for building canvas and model-driven apps with these AI-first descriptions, and Microsoft lists the domain's share as decreased. You still need to recognize app components, but the exam now favors choosing the right app approach and describing AI-assisted creation over step-by-step control configuration.
How it's tested
Most items describe users, devices, data and the level of design control required, then ask which app approach or AI-assisted path fits. Others ask what Plan designer or the vibe experience produces. Read for clues about layout freedom, Dataverse dependence and whether the builder is a business maker or a professional developer.
-
Pick the app type
Layout needs, data source and user role decide between canvas, model-driven and code apps.
-
Start from a problem
A scenario with a business goal but no defined app design points to Plan designer generating a plan first.
-
Describe the AI path
Questions ask what Copilot generates when a maker describes an app, such as tables, screens or a full solution.
An insurer needs agents to manage claims linked to policies, customers and payments, with consistent screens and role-based access, and the data already lives in Dataverse. Layout freedom is not a priority, but structured navigation and security are. A model-driven app fits because it is generated from Dataverse tables, forms and views. A canvas app would need every screen designed by hand.
Functional groups 2
Official functional groups from the Microsoft outline, in outline order.
3.1 Describe Power Apps capabilities and use casesUse cases for canvas apps, model-driven apps, Plan designer and code apps.
- What it means
- This group asks you to describe the use cases and capabilities of four ways to build in Power Apps: canvas apps, model-driven apps, Plan designer, and code apps.
- What to understand
- Canvas apps start from a blank screen or template, give pixel-level control of layout, connect to many data sources through connectors and suit task-focused mobile or tablet apps. Model-driven apps are built from Dataverse components such as tables, forms, views and dashboards; layout is largely determined by those components, giving consistent, responsive, process-heavy apps. Plan designer takes a business problem in natural language and uses Copilot to produce a solution plan with user roles, requirements, a data model and suggested apps, flows and agents. Code apps let developers build apps in code-first frameworks in their own tools while running on Power Platform with its connectors, authentication and governance.
- How it shows up
- Expect a scenario with layout, data and builder clues; choose the approach whose strengths match, and recognize Plan designer as a planning starting point.
- Common confusion
- Believing model-driven apps can use any data source directly; they are built on Dataverse, while canvas apps reach many sources.
3.2 Describe how to build basic apps by using Power AppsUsing AI to create canvas and model-driven apps, and creating AI-powered apps with the vibe experience.
- What it means
- This group covers AI-assisted creation in Power Apps: using AI to create a canvas app, using AI to create a model-driven app, and creating AI-powered apps by using the vibe experience.
- What to understand
- From the Power Apps home page a maker can describe an app in natural language; Copilot proposes a Dataverse table with columns and sample data, then generates a canvas app the maker refines with further prompts. Model-driven apps can be created with AI by describing the business need or through Plan designer, which proposes tables and relationships and builds the app on them. The vibe experience is a conversational, AI-first way to create a complete app: it drafts a plan, a data model and a working app together, and the maker iterates by chatting. In every path, makers review generated data structures, security and logic before sharing.
- How it shows up
- Expect questions on what each AI path generates, such as a table plus canvas app, or a plan, data model and working app.
- Common confusion
- Assuming AI-generated apps skip Dataverse or governance; they still create tables and run inside environments.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Canvas app
An app designed screen by screen with full control of layout and controls.
- Remember
- It connects to Dataverse, SharePoint, SQL and many other sources through connectors.
- Tested as
- The answer for custom, task-focused mobile or tablet experiences.
- Trap
- Assuming canvas apps must use Dataverse.
-
Model-driven app
An app generated from Dataverse tables, forms, views, charts and dashboards.
- Remember
- Layout follows components, giving responsive, consistent screens with little design work.
- Tested as
- Chosen for complex processes over related data with role-based security.
- Trap
- Expecting pixel-level layout control in a model-driven app.
-
Plan designer
A Copilot experience that turns a business problem into a solution plan.
- Remember
- Plans include user roles, requirements, data tables and proposed apps, flows and agents.
- Tested as
- The answer when the scenario starts from a goal rather than a known app design.
- Trap
- Thinking it only builds a single canvas app.
-
Code apps
Apps written in code-first web frameworks that run on Power Platform.
- Remember
- Developers use their own tools yet gain connectors, Microsoft Entra authentication and admin governance.
- Tested as
- Fits a professional developer who wants code control inside Power Platform.
- Trap
- Assuming code apps bypass data policies and sharing controls.
-
Vibe experience
An AI-first, conversational way to create a full app in Power Apps.
- Remember
- It drafts plan, data model and app together, refined by chat.
- Tested as
- Questions may ask how makers create AI-powered apps from natural language end to end.
- Trap
- Treating it as only a chatbot rather than an app-building experience.
-
Copilot app creation
Describing a canvas app on the home page so Copilot drafts a table and app.
- Remember
- Makers keep refining with prompts and the designer.
- Tested as
- Matches bullets on using AI to create a canvas app.
- Trap
- Believing the first draft is final and needs no review.
-
Controls and screens
Canvas building blocks such as galleries, forms, buttons and labels on screens.
- Remember
- Galleries list records; edit forms change one record.
- Tested as
- Basic recognition still appears in canvas descriptions.
- Trap
- Confusing a canvas gallery with a model-driven view.
-
Power Fx in canvas apps
Formulas that set control behavior and data operations.
- Remember
- Functions such as Filter, Patch and Navigate drive app logic.
- Tested as
- Canvas capability questions may mention formulas as the logic layer.
- Trap
- Thinking canvas logic must be written in JavaScript.
-
Responsive design
Apps that adapt to screen sizes.
- Remember
- Model-driven apps are responsive by default; canvas apps need containers and layout choices.
- Tested as
- Device scenarios test which app type adapts with least effort.
- Trap
- Assuming canvas apps resize automatically like model-driven apps.
-
Sharing apps
Granting users access to run an app.
- Remember
- Users also need data access, such as Dataverse security roles, and suitable licenses.
- Tested as
- Scenarios where users open an app but see no data hinge on this.
- Trap
- Sharing the app without granting a security role.
-
App solution packaging
Placing apps with tables and flows into a solution.
- Remember
- Solutions are the unit moved between environments.
- Tested as
- Links app building to ALM in the environment domain.
- Trap
- Building production apps outside any solution.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Power Apps approaches
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Canvas app | Screen-by-screen design with connectors to many sources. | Maximum layout control, any supported data source. | Picking it for complex Dataverse processes needing consistent forms. |
| Model-driven app | Component-driven app on Dataverse. | Layout comes from tables, forms and views. | Expecting custom screen design freedom. |
| Code app | Code-first web app hosted on Power Platform. | Developers write code but keep platform governance. | Offering it to business makers who do not code. |
| Plan designer | AI planning from a business problem. | Produces a plan and proposed solution parts before building. | Treating it as an app type rather than a starting experience. |
AI-assisted creation paths
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Copilot canvas creation | Describe an app; get a table and canvas app. | Starts from a single app idea. | Assuming it creates flows and agents too. |
| AI model-driven creation | Describe the need; get tables, relationships and a model-driven app. | Centers on Dataverse data model first. | Forgetting the model-driven app depends on Dataverse tables. |
| Vibe experience | Conversational build of plan, data and working app together. | One AI-first flow from idea to running app. | Confusing it with Copilot Studio agent building. |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Canvas for every app
- What candidates pick
- A canvas app for a multi-table case management process
- Why it looks right
- Canvas apps are the most visible Power Apps option.
- Why it's wrong
- Complex, related Dataverse data with standard forms, views and security fits model-driven apps with far less design effort.
Clue to watch for Several related tables, business process stages, consistent screens.
-
Model-driven on SharePoint
- What candidates pick
- A model-driven app over a SharePoint list
- Why it looks right
- Model-driven apps sound suited to any structured data.
- Why it's wrong
- Model-driven apps are built on Dataverse; a SharePoint list source points to a canvas app.
Clue to watch for Data stays in SharePoint or another external source.
-
Plan designer as final app
- What candidates pick
- Plan designer to adjust one canvas control
- Why it looks right
- It is a new AI feature and seems to do everything.
- Why it's wrong
- Plan designer starts from a business problem and proposes a whole solution; small app edits happen in the app designer or with Copilot there.
Clue to watch for The app already exists and only needs a tweak.
-
Code apps for citizen makers
- What candidates pick
- Code apps for a business user with no coding skills
- Why it looks right
- Code apps are listed alongside other Power Apps options.
- Why it's wrong
- Code apps target developers writing code in their own tools; business makers are better served by canvas, model-driven or AI creation.
Clue to watch for Who builds the app and their skills.
-
AI output needs no review
- What candidates pick
- Share the Copilot-generated app immediately
- Why it looks right
- The draft runs and looks complete.
- Why it's wrong
- Generated tables, logic and security still need checking before sharing with users.
Clue to watch for Words such as validate, review or production.
-
Vibe equals agent
- What candidates pick
- Copilot Studio when asked about the vibe experience
- Why it looks right
- Both are conversational and AI driven.
- Why it's wrong
- The vibe experience is in Power Apps and produces an app; Copilot Studio produces agents.
Clue to watch for The output requested is an app, not a conversational assistant.
Answer framework
Use these steps to choose a Power Apps approach or AI creation path from a scenario.
- Check whether the requirement is a clear app or still a business problem; an undefined solution with several roles suggests starting in Plan designer.
- Identify the data source, because Dataverse-centric processes favor model-driven apps while SharePoint, SQL or mixed sources favor canvas apps.
- Weigh layout needs: custom, task-focused or branded screens point to canvas, while standard forms and views point to model-driven.
- Consider who builds it; professional developers who want code-first frameworks with platform governance point to code apps.
- If AI creation is mentioned, match the output: table plus canvas app from a description, Dataverse-based model-driven app, or the vibe experience for a complete app built through conversation.
Practice question
Want more like this? The PL-900 practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Get hands-on early. In a developer environment, describe a simple app on the Power Apps home page and watch Copilot create a table and canvas app, then refine it with two or three prompts. Next, build a model-driven app from the same table, adding a form and a view, and notice how much layout comes for free.
Then explore the newer experiences. Give Plan designer a short business problem, such as onboarding new hires, and read every part of the plan it proposes: roles, requirements, tables, apps and flows. Try the vibe experience if it is available in your region, and compare its output with the Copilot canvas path. Read the code apps overview so you can explain who uses it and what governance it keeps.
Finish with a comparison table in your own words covering data source, layout control, builder skills and typical use case for each approach. Use practice questions to test app selection, since that judgment drives most items in this domain.
FAQ
How much of PL-900 does Demonstrate the capabilities of Power Apps cover?
Demonstrate the capabilities of Power Apps is weighted at 20–25% of PL-900. Microsoft lists its share as decreased in the July 24, 2026 revision, but it remains one of four equally weighted large domains.
Do I still need to build canvas apps by hand?
The hands-on canvas and model-driven build groups were removed. You should still recognize screens, controls and forms, but the focus is describing capabilities and AI-assisted creation.
What is the difference between Plan designer and the vibe experience?
Plan designer turns a business problem into a solution plan with roles, data and suggested apps, flows and agents. The vibe experience conversationally builds a working app with its plan and data model.
Are code apps on a fundamentals exam?
Yes, at the use case level. Know that developers build them with code-first web frameworks while Power Platform provides connectors, authentication and governance.
Can a model-driven app use SharePoint data directly?
Model-driven apps are built on Dataverse tables. External data can be surfaced through virtual tables, but for a plain SharePoint list scenario the expected answer is usually a canvas app.
Is Power Pages tested in this domain?
No. Power Pages now appears only as a value statement in Domain 1 after its own skill area was removed in 2026.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 3 knowledge
Check that you can pick the right Power Apps approach and describe each AI creation path before you continue.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PL-900 AI tutor Get any concept explained your way