Power Apps: Canvas, Model-Driven & Code Apps

What is the fundamental starting point when building a canvas app, as opposed to a model-driven app?

• AA code-first project opened in Visual Studio Code
• BA set of business process flow stages that define the guided sequence
• CAn existing Dataverse table whose structure, columns, and relationships automatically generate the interface
• DA blank design canvas where the maker places controls, screens, and data connections✓

Answer: Canvas apps start from a blank design surface, just like a presentation tool, where the maker positions every control and connects the data. Model-driven apps instead start from the Dataverse data model and generate the interface automatically. A business process flow stage and a Visual Studio Code project describe model-driven and code app workflows, not the canvas app starting point.

Which formula language do canvas apps use to add logic such as conditional visibility and data filtering?

• APower Query M
• BPower Platform CLI scripts
• CPower Fx✓
• DDataverse business rules

Answer: Power Fx is the Excel-like formula language built into canvas apps, covering conditional visibility, filtering, aggregation, and navigation. Power Query M is a data transformation language used elsewhere in the Microsoft ecosystem, not for canvas app logic. Dataverse business rules and CLI scripts are unrelated mechanisms tied to model-driven apps and code apps respectively.

A field technician needs a mobile app that keeps working when there is no signal at a remote job site, then syncs once reconnected. Which Power Apps capability supports this?

• AOffline mode for canvas apps running on the Power Apps mobile app✓
• BBusiness process flows guiding technicians through case stages
• CPower BI dashboards embedded in a model-driven app
• DAutomatically generated responsive UI in model-driven apps

Answer: Canvas apps support offline mode through the Power Apps mobile app, letting field workers keep using the app without connectivity and sync once reconnected. A responsive UI describes how model-driven apps adapt to screen size, not connectivity. Business process flows and embedded Power BI dashboards are model-driven app features unrelated to offline access.

Which statement correctly distinguishes the data sources available to canvas apps versus model-driven apps?

• AModel-driven apps can connect to any data source with 200+ connectors, while canvas apps work with Dataverse only, requiring a manual custom connection
• BCanvas apps require Dataverse and cannot connect to SharePoint or SQL Server directly
• CBoth app types are restricted to Microsoft Dataverse as their only supported data source, with no support at all for SharePoint, SQL, or other connectors
• DCanvas apps can connect to SharePoint, SQL, Dataverse and hundreds of other connectors, while model-driven apps work with Microsoft Dataverse only✓

Answer: Canvas apps can draw on SharePoint, SQL Server, Dataverse and 200+ connectors in a single app, while model-driven apps are built on Microsoft Dataverse only. The claim reversing this pairing swaps the two app types incorrectly. Neither app type is limited to Dataverse alone, and canvas apps do not require Dataverse to function.

Which Power Apps type generates its user interface automatically from the underlying data model, adapting to any device without extra design work?

• ACode apps
• BCanvas apps
• CModel-driven apps✓
• DPower Automate cloud flows

Answer: Model-driven apps take a data-first approach, assembling a responsive interface automatically once tables, forms, and views are defined in Dataverse. Canvas apps require the maker to design the layout manually for each screen size. Code apps give developers full manual UI control, and cloud flows are a Power Automate concept, not an app type.

A sales team needs an app that guides sellers stage-by-stage through lead qualification, proposal, and closing. Which built-in model-driven app feature supports this?

• AReusable canvas app components
• BBusiness process flows✓
• CThe Power Apps Component Framework
• DOffline mobile synchronisation

Answer: Business process flows are guided, stage-based sequences built into model-driven apps that walk sellers through steps such as qualification, proposal, and closing. Reusable canvas app components are a canvas app feature for sharing design elements, not guided processes. The Power Apps Component Framework builds custom controls, and offline synchronisation concerns connectivity, not staged guidance.

What security model do model-driven apps use by default?

• AThey inherit Dataverse's security roles, business unit hierarchy, and row-level and column-level access controls✓
• BThey rely on app-level sharing permissions, configured entirely separately from Dataverse security and unrelated to roles or business units
• CThey require a custom Power Fx formula to restrict which users can view each record
• DThey use the same conditional access, and Data Loss Prevention policies, that govern code apps running in a Managed Environment

Answer: Model-driven apps automatically inherit Dataverse's full security model, including security roles, business unit hierarchies, and row- and column-level access, with no extra app-level configuration needed. Canvas apps, by contrast, are controlled at the app level rather than inheriting Dataverse security directly. Conditional access and Data Loss Prevention govern environment-level governance for code apps, and no custom Power Fx formula is needed to enforce record-level access in a model-driven app.

Which model-driven app feature lets users generate a Power BI report directly from a filtered, sorted list of records?

• AA generative page
• BThe Visualize this view option✓
• CThe Create new tables workspace
• DA business process flow stage

Answer: Selecting Visualize this view on a model-driven app view lets users generate a Power BI report directly from that filtered, sorted list of records. The Create new tables workspace is where Copilot builds and refines a data model, not reports. A generative page and a business process flow stage are unrelated model-driven app building blocks that don't produce Power BI reports.

What are code apps, as described for Power Apps?

• ACanvas apps generated automatically from an Excel spreadsheet, an existing SharePoint list, or another supported data source, without any manual design
• BModel-driven apps customised with Power Apps Component Framework controls
• CCustom web applications built with code by professional developers that use the Power Apps client library to connect to Power Platform connectors✓
• DDataverse tables exposed directly as a browsable web page

Answer: Code apps are custom web applications built in HTML, TypeScript, JavaScript, or a framework such as React, using the Power Apps client library to reach Power Platform connectors while running inside a governed environment. A canvas app built from an Excel spreadsheet is still a low-code canvas app, not a code app. A model-driven app with PCF controls and a bare Dataverse table exposed as a page both describe different, unrelated scenarios.

Where do developers build and manage code apps, according to the unit?

• AIn the model-driven app designer's Pages panel
• BThrough the Create new tables workspace in Copilot
• CLocally in a code-first IDE such as Visual Studio Code, then published with the Power Platform CLI✓
• DIn the Power Apps maker portal's canvas app designer, alongside other low-code screens and controls

Answer: Code apps are built locally on a developer's workstation using standard tooling such as Visual Studio Code, version-controlled in Git, and published to Power Platform with the Power Platform command-line interface. Code apps are explicitly not built in the Power Apps maker portal's canvas app designer. The model-driven app designer's Pages panel and Copilot's table workspace are used for entirely different app types.

Which governance controls do code apps inherit because they run inside a Power Platform environment?

• AAutomatically generated forms and views from the data model
• BManaged Environment policies, app sharing limits, conditional access, and Data Loss Prevention policies✓
• CBusiness process flow stages, and Dataverse timeline tracking, configured separately in each app that uses the table
• DReusable canvas app components shared across an app portfolio

Answer: Because code apps run inside a Power Platform environment, they inherit its governance controls, including Managed Environment policies, app sharing limits, conditional access, and Data Loss Prevention policies. Business process flows and activity timelines are model-driven app features, not governance controls a code app inherits. Reusable components and auto-generated forms belong to canvas apps and model-driven apps respectively.

What is the Power Apps Component Framework (PCF) used for?

• AEmbedding a canvas app inside a SharePoint site or Teams channel
• BPackaging code apps into Power Platform solutions for deployment through Power Platform Pipelines and CI/CD tooling in Azure DevOps or GitHub Actions
• CGenerating a Dataverse data model automatically from a natural language description typed into the Copilot conversation panel, table by table
• DBuilding reusable custom UI controls in TypeScript that professional developers can use in both canvas apps and model-driven apps✓

Answer: PCF lets professional developers build reusable custom UI controls in TypeScript that can then be used across both canvas apps and model-driven apps. Generating a Dataverse data model from a description is what Copilot does during conversation-driven creation, not PCF. Packaging code apps for pipeline deployment and embedding a canvas app in SharePoint or Teams are separate capabilities unrelated to building custom controls.

A development team is migrating an existing React web application to run under Power Platform governance without rewriting it from scratch. Which Power Apps type fits this scenario?

• ACustom pages inside a model-driven app
• BModel-driven apps with business process flows
• CCode apps✓
• DCanvas apps built from data

Answer: Code apps let organisations bring an existing web application, such as one built in React, onto Power Platform to gain governance without a full rewrite. A canvas app built from data is generated automatically from a source like Excel or SharePoint, not migrated from existing code. Model-driven apps with business process flows and custom pages inside a model-driven app are Dataverse-first constructs that don't host an existing React codebase.

An organisation wants to embed an app inside a SharePoint site, a Power BI report, and a Teams channel. Which Power Apps type is designed for this kind of embedding?

• AModel-driven apps
• BCopilot Studio agents
• CCanvas apps✓
• DCode apps

Answer: Canvas apps can be embedded into SharePoint sites, Power BI dashboards, and Teams channels, making it easy to surface their functionality within tools people already use. Model-driven apps and code apps are not described as embeddable in this way in the units. Copilot Studio agents are a separate Power Platform product built for conversational AI, not app embedding.

A support team needs to create, route, escalate, and resolve customer service cases, with a full history of every interaction visible on each record. Which Power Apps type and feature combination fits best?

• AA code app, using the Power Apps Component Framework
• BA canvas app, using its offline mode for field technicians
• CA model-driven app, using its built-in activity timeline✓
• DA canvas app, using reusable components shared across apps

Answer: Model-driven apps include a built-in activity timeline on every record, tracking emails, calls, tasks, and notes, which gives support teams full context for case history. Offline mode addresses connectivity for field technicians, not case history. The Power Apps Component Framework builds custom controls, and reusable canvas components share design elements, neither of which provides a record's interaction history.

Which statement correctly compares business process flow support between canvas apps and model-driven apps?

• ABoth app types natively include the exact same stage-based business process flow designer, with identical configuration options
• BCanvas apps natively include stage-based business process flows, while model-driven apps require a custom build to achieve the same guidance
• CModel-driven apps natively include stage-based business process flows, while canvas apps would need a custom build✓
• DNeither app type supports business process flows; only Copilot Studio agents do

Answer: Business process flows are built into model-driven apps as guided, stage-based sequences, whereas canvas apps would require a custom build to achieve similar guidance. Reversing which app type has native support states the comparison backwards. Business process flows are not shared equally by both app types, and they are a model-driven app feature rather than something limited to Copilot Studio agents.