PL-900 domain - 30% of the exam

Describe Microsoft Power Apps

Describe Microsoft Power Apps is 30% of the PL-900 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

77
Practice questions
3
Objectives
23
Easy
43
Medium
11
Hard

Where people go wrong

  • Giving model-driven apps canvas strengths

    The wrong answers pick a model-driven app for work that needs a canvas app, or credit model-driven apps with canvas strengths: connectors to SharePoint, Excel, Salesforce or SQL Server, Power Fx on control properties, and free placement of controls on a blank canvas. A canvas app starts from the user experience, gives the maker full control of layout and connects to many data sources at once. A model-driven app uses Dataverse as its only data platform, and its layout is largely determined by the components added.

    See it in a sample question
  • Crediting canvas apps with automatic behaviour

    The wrong answers credit canvas apps with behaviour that a model-driven app supplies on its own: a layout that adapts to each device, and navigation from a record to its related records. Canvas apps are responsive only if the maker designs them that way, and their relationship navigation is available only where it is designed with Power Fx. A model-driven app generates a responsive UI automatically and navigates through relationships automatically, provided the relationships exist.

    See it in a sample question
  • Confusing public, personal and system views

    The wrong answers offer a personal view or a system view where a public view is needed. A personal view is owned by one individual and is visible only to that person unless shared. System views, such as the Associated and Lookup views, are not shown in the view selector and cannot be used in a subgrid on a form. A public view is the general-purpose view that all app users reach through the view selector once it is made available, and it can feed a subgrid or a dashboard list.

    See it in a sample question
  • Stretching Co-Owner beyond use, edit and share

    The wrong answers stretch the Co-Owner permission past use, edit and share. They give a Co-Owner the right to delete the app or change its owner, or count running the app as something only a Co-Owner can do. The User permission lets a person run the app only. Co-Owner adds editing and re-sharing on top of that. Deleting the app and changing its owner stay with the original owner.

    See it in a sample question
  • Mixing up canvas layout controls and settings

    The wrong answers reach for a gallery, a plain Container, a component, Group, Split-screen or Sidebar when a canvas app needs child controls positioned automatically. A gallery repeats a template per record, children of a plain Container keep X and Y formulas, and Split-screen and Sidebar are screen layout templates. The Horizontal container and Vertical container place children and distribute space so no X or Y is set. Fill portions sets the ratio between sibling containers. Flexible width is an on or off toggle, and Align and Justify position children.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleDescribe Microsoft Power Appsmedium

A maker needs an app where they personally position every control on a blank design surface and set behaviour by writing expressions against control properties. Which Power Apps capability matches how this app is designed?

  • AA model-driven app, where the app designer assembles ready-made views and dashboards
  • BA model-driven app, where forms and layout are largely determined by the components added
  • CA canvas app, where the maker has full control of layout and uses Power Fx expressions Correct
  • DA canvas app, where the sitemap fixes the navigation order between standard tables
Canvas apps give full layout control on a blank surface, with behaviour driven by Power Fx expressions. In canvas apps the maker has total control over app layout on a blank canvas, and the design experience is the manipulation of control properties using Power Fx expressions.

Why A is wrong: Model-driven design is component focused and assembles forms, views, and dashboards, but it does not give the maker free placement of every control on a blank surface.

Why B is wrong: This correctly describes model-driven layout, where much of the interface is determined for you, which is the opposite of the free-form control the scenario asks for.

Why C is correct: Correct. In canvas apps the maker has total control over app layout on a blank canvas, and the design experience is the manipulation of control properties using Power Fx expressions.

Why D is wrong: A sitemap defining navigation between tables belongs to model-driven apps, not canvas apps, so this attributes the wrong mechanism to the right app type.

Free sampleDescribe Microsoft Power Appseasy

A model-driven app automatically generates a user interface that is responsive across devices and is accessible by default. Is this statement correct?

  • AYes Correct
  • BNo
Model-driven apps deliver responsive, accessible interfaces automatically without per-device design work. The grounding states that model-driven apps automatically generate a UI that is responsive across devices and that the apps are accessible and responsive automatically, so the maker does not design the layout per device.

Why A is correct: Correct. The grounding states that model-driven apps automatically generate a UI that is responsive across devices and that the apps are accessible and responsive automatically, so the maker does not design the layout per device.

Why B is wrong: Answering No is wrong because the grounding explicitly lists automatic responsiveness and built-in accessibility as benefits of the model-driven approach; it is canvas apps that are responsive only if designed that way.

Free sampleDescribe Microsoft Power Appsmedium

A bank's model-driven app for loan officers must offer one view of the loan table that every officer can pick from the view selector once the maker makes it available, and that can also feed a subgrid on a form. Which type of view meets all of these requirements?

  • AA personal view, owned by the individual officer and invisible to colleagues unless that officer shares it
  • BA public view, available to all app users through the view selector and usable in a subgrid on a form Correct
  • CA system view, such as Quick Find or Lookup, that the application depends on for built-in search behaviour
  • DAn associated view, the default that lists the related tables shown for a single open record
Public views are general-purpose, selectable by all app users, and reusable in subgrids and dashboards. The grounding describes public views as general-purpose views that all app users can access through the view selector when made available, and that public views can be used in subgrids on a form or as a list in a dashboard.

Why A is wrong: Tempting because officers can save their own filtered lists. Wrong because the grounding says personal views are owned by individuals and only visible to that person unless shared, so they are not available to every officer by default.

Why B is correct: Correct. The grounding describes public views as general-purpose views that all app users can access through the view selector when made available, and that public views can be used in subgrids on a form or as a list in a dashboard.

Why C is wrong: Tempting because system views exist for every table. Wrong because the grounding says system views are not shown in the view selector and cannot be used in sublists in a form, so officers could not pick one or feed a subgrid with it.

Why D is wrong: Tempting because it appears on forms. Wrong because the grounding classes the associated view as a system view that lists related tables for a record; it is not the selectable, general-purpose view the officers need.

Free sampleDescribe Microsoft Power Appsmedium

When you share a canvas app and grant a user the Co-Owner permission, that user can use, edit, re-share, and delete the app. Is this statement correct?

  • AYes
  • BNo Correct
Co-Owner permission on a canvas app allows use, edit, and re-share only; it does not allow deleting the app or changing its owners. No is correct. In the canvas app Share dialog the Co-Owner permission lets a user use, edit, and share the app, but explicitly not delete it or change owners. Only the User permission and Co-Owner are offered, and neither grants delete rights, so the claim that a Co-Owner can delete the app contradicts the grounding.

Why A is wrong: Answering Yes is wrong because it assumes Co-Owner means full control. A learner who knows Co-Owners can edit and re-share may wrongly extend that to deleting the app, but the grounding caps Co-Owner at use, edit, and share and withholds delete and change-owner rights.

Why B is correct: This option does not match the keyed mechanism. No is correct.

Free sampleDescribe Microsoft Power Appsmedium

A maker is building a canvas app for a retail stock-room dashboard and wants child controls placed inside a parent to be positioned automatically, with the available space distributed between them and their vertical and horizontal alignment handled for them, so that no X or Y coordinate has to be set on each child. Which control should the maker use as the parent?

  • AAn Auto-layout container control, which arranges its child controls and distributes space without per-child X and Y Correct
  • BA Gallery control, whose template repeats one row of child controls down the screen for each data record
  • CA plain Container control, where each child still needs X, Y and Width formulas written against the parent
  • DA Component, a reusable building block whose child controls size against Parent.Width and Parent.Height
Auto-layout container controls position child controls and distribute space automatically, so you do not set X and Y on each child. The grounding describes Auto-layout container controls as a feature that determines the position of child components so you never set X, Y for a component inside the container, distributes available space among children, and determines both their vertical and horizontal alignment.

Why A is correct: Correct. The grounding describes Auto-layout container controls as a feature that determines the position of child components so you never set X, Y for a component inside the container, distributes available space among children, and determines both their vertical and horizontal alignment.

Why B is wrong: Tempting because a gallery is also a parent that lays out child controls. Wrong because a gallery repeats its template per record using Parent.TemplateHeight and TemplateWidth; it does not distribute space or set alignment across distinct sibling controls the way an auto-layout container does.

Why C is wrong: Tempting because the Container control is a parent for headers and similar groupings. Wrong because the grounding shows children inside a plain Container still have their X, Y, Width and Height set with formulas; it does not auto-position or distribute space.

Why D is wrong: Tempting because a component is a parent you reuse across the app. Wrong because the grounding describes components as building blocks whose children base position and size formulas on Parent.Width and Parent.Height; they are not automatically laid out.

Other domains in this exam

See also the PL-900 cert hub, the study guide, and the cheat sheet.

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