Free PL-900 practice questions

A maker wants to build an app whose screens pull records from a SharePoint list, an Excel workbook held in OneDrive, and a Salesforce account, combining all three on one screen. Which Power Apps app type supports binding to that range of data sources?

• AA canvas app, which connects to many data sources through connectorscheck_circle Correct
• BA model-driven app, which reads its records from Dataverse tables only
• CA model-driven app, which pulls external sources in through connectors too
• DA canvas app, which binds to only one Dataverse table at a time

Why A is correct: Correct. Canvas apps start with the user experience and connect to a wide variety of data sources through connectors, so SharePoint, Excel, and Salesforce records can all be surfaced on the same screen.

Why B is wrong: Model-driven apps are a real app type, but their data platform is Dataverse only, so they cannot bind directly to SharePoint, Excel, and Salesforce as the scenario requires.

Why C is wrong: Model-driven apps use Dataverse as their only data platform; they do not pull external sources in through connectors on their screens, so this misstates how model-driven apps get data.

Why D is wrong: Canvas apps are not limited to a single Dataverse table; they connect to many sources through connectors, so this understates canvas data binding.

An organisation is deciding which Power Apps app type to start with for a new application. They are told the chosen type cannot be created at all unless a particular data platform is already in place. Which app type carries that requirement?

• AA canvas app, because its screens always read and write through Power Fx expressions
• BA model-driven app, because it is built on a data model housed within Dataversecheck_circle Correct
• CA canvas app, because its galleries must be bound to imported Excel tables
• DA model-driven app, because its forms render only inside the Teams client

Why A is wrong: Canvas apps do use Power Fx, but they can be built against many sources and do not require Dataverse, so they have no such hard prerequisite.

Why B is correct: Correct. Model-driven apps are built up from the shape of core business data in Dataverse, and the grounding states you cannot create one without a data model housed within Dataverse.

Why C is wrong: Excel is only one of many sources a canvas app may use, and galleries can bind to any connected source, so no single platform is mandatory.

Why D is wrong: Model-driven apps run in a browser and on mobile, not solely in Teams, so this misstates where the app runs rather than its real data prerequisite.

A maker is comparing model-driven apps with canvas apps before choosing an approach for a data-dense process app. Which statements correctly describe model-driven apps? (Select 2 answers)

• AThey are built up from the shape of business data and processes modelled in Dataversecheck_circle Correct
• BNavigation between related records is automatic where relationships exist between tablescheck_circle Correct
• CThey give the maker full control over the layout of every screen on a blank design surface
• DThey can connect directly to more than 200 data sources through connectors
• EBehaviour is set mainly by writing Power Fx expressions against control properties

Why A is correct: Correct. They are built up from the shape of business data and processes modelled in Dataverse is one of the keyed answers. Model-driven apps build up from a Dataverse data model, and navigation between related records is automatic wherever relationships exist between the tables, which together make them suited to data-dense process apps.

Why B is correct: Correct. Navigation between related records is automatic where relationships exist between tables is one of the keyed answers. Model-driven apps build up from a Dataverse data model, and navigation between related records is automatic wherever relationships exist between the tables, which together make them suited to data-dense process apps.

Why C is wrong: Full control over layout on a blank surface describes canvas apps; in model-driven apps much of the interface is determined by the components added, so layout control is limited.

Why D is wrong: Connecting to many sources through connectors is a canvas app trait; model-driven apps use Dataverse only as their data platform.

Why E is wrong: Manipulating control properties with Power Fx is the canvas app design experience; model-driven design is no-code and component focused.

A retail analyst is learning how Microsoft Dataverse organises the data their loyalty app uses. In Dataverse, what is the structure that holds a set of rows and columns, where each column is designed to store a certain type of data?

• AA table, which is a set of rows and columns that models business datacheck_circle Correct
• BA business rule, which validates entered data across the columns it covers
• CA solution, which packages the components that makers build and ship
• DA dataflow, which transforms source data on its way into the store

Why A is correct: Correct. The grounding defines a table as a set of rows (records) and columns (fields), with each column designed to store a certain type of data such as name, age or salary; tables are how Dataverse organises stored business data.

Why B is wrong: A business rule is real Dataverse logic for validation, but the grounding describes it as server-side logic applied to a table, not the structure that stores the rows and columns themselves.

Why C is wrong: Solutions are a genuine Power Platform construct referenced in the grounding for importing definitions, but they package components for deployment rather than store the rows and columns of business data.

Why D is wrong: Power Query dataflows do bring data into Dataverse per the grounding, but they are an import mechanism and not the structure that holds the stored rows and columns.

A field-service app stores each work order in one table and each customer site in another. A maker wants every work order to point to exactly one site, with many work orders allowed to reference the same site. Which column data type should the maker add to the work order table to create this many-to-one relationship?

• AChoice column, holding one option selected from a defined list of values
• BLookup column, holding a reference to a single row in the related tablecheck_circle Correct
• CCustomer column, holding a reference to either an account or a contact row
• DChoices column, holding several values selected at once from a list

Why A is wrong: A Choice column stores one value chosen from a maker-defined option set, but those options are static values rather than references to rows in another table, so it creates no relationship.

Why B is correct: Correct. Per the grounding, when you create a Lookup column you create a Many-to-One (N:1) relationship between your table and the lookup's target row type, and the column holds a reference to a single row of that target type.

Why C is wrong: Customer is a real lookup type, but the grounding limits it to referencing an account or a contact row, not an arbitrary custom site table the maker has built.

Why D is wrong: A Choices (multi-select) column stores multiple option values from a list, which neither references another table nor models a single many-to-one link.

A retail chain stores supplier data in a Dataverse table that feeds both a canvas app used in stores and a model-driven app used by head office. A maker needs the same validation logic to run no matter which app records are entered through, without writing code. Which Dataverse business logic option meets this requirement?

• AA business rule defined for the table, which applies to both canvas apps and model-driven apps that use the tablecheck_circle Correct
• BA business process flow defined for the table, which guides users through the same ordered steps in every app that uses it
• CA real-time workflow defined for the table, which runs automated steps whenever a record in the table is created or updated
• DA desktop flow defined for the table, which records and replays the manual entry steps a user performs in the app

Why A is correct: Correct. Business rules let you apply logic and validations without writing code or plug-ins, and a business rule defined for a table applies to both canvas apps and model-driven apps if the table is used in the app, running at the server level.

Why B is wrong: Tempting because it also enforces consistency, but business process flows are currently only supported for model-driven apps, so the canvas app would not get the logic.

Why C is wrong: Workflows automate business processes without user interaction, but they are not the no-code form-validation mechanism that surfaces warnings and errors as users type across both app types.

Why D is wrong: Desktop flows automate playback of manual steps on legacy software through robotic process automation; they do not provide reusable in-form table validation across canvas and model-driven apps.

A new retail operations maker wants to build an approval flow quickly and does not want to assemble every trigger and action manually from an empty canvas. Which Power Automate feature gives a prebuilt starting point that can be searched for a matching scenario and then modified to fit the maker's needs?

• ATemplates, which give prebuilt flows you search by scenario, then edit by adding or removing actionscheck_circle Correct
• BSolutions, which package related components together so they can be moved between environments as a unit
• CConnectors, which provide the prebuilt links to the apps and services the flow needs to reach
• DProcess mining, which provides prebuilt analysis of how a process is actually executed in practice

Why A is correct: Correct. The grounding describes using or tweaking an existing template as a way to get started, where you search the list of templates for your scenario and then create and modify a flow by adding, editing, or removing triggers and actions.

Why B is wrong: Solutions are a real Power Platform feature shown in the navigation, but they package and move components between environments; they are not the prebuilt-flow starting points the maker is asking for.

Why C is wrong: Connectors are real prebuilt links to apps and services, but they supply the integration points inside a flow, not a ready-made starting flow the maker can search by scenario and modify.

Why D is wrong: Process mining is a genuine Power Automate capability, but it visualises and analyses existing processes from event data; it does not hand the maker a prebuilt flow to start from and tweak.

A retail chain runs an expense-report approval flow and wants to know where the assigned manager can respond and where the approval records are held. Which statement matches how Power Automate approvals work?

• AManagers respond from an Outlook email, a Teams adaptive card, or the action centre, and records are saved in Dataversecheck_circle Correct
• BManagers respond only inside Power Apps Studio, and approval records are stored in a SharePoint document library
• CManagers respond from the Power Automate mobile app alone, and approval records are stored in an Azure SQL database
• DManagers respond only through a Microsoft Forms response page, and approval records are stored in OneDrive folders

Why A is correct: Correct. After an approval is assigned, the approver can respond directly from an Outlook email, a Microsoft Teams adaptive card, or the Power Automate action centre, and approval flows are saved in Dataverse.

Why B is wrong: Tempting because both products are real and SharePoint is a common store, but approvers respond via Outlook, Teams, or the action centre, and approvals are saved in Dataverse, not SharePoint.

Why C is wrong: Tempting because the mobile app is genuine, but the documented response channels are Outlook, Teams, and the action centre, and approvals are saved in Dataverse rather than Azure SQL.

Why D is wrong: Tempting because Forms collects responses elsewhere in Power Automate, but approvers respond via Outlook, Teams, or the action centre, and approvals live in Dataverse, not OneDrive.

Because the approvals connector is a standard connector, any licence that grants access to Power Automate and the ability to use standard connectors is sufficient to create approval flows. Is this statement correct?

• AYescheck_circle Correct
• BNo

Why A is correct: Correct. The approvals connector is a standard connector, so any licence that grants access to Power Automate and the ability to use standard connectors, including Office 365, is sufficient to create approval flows.

Why B is wrong: Answering No is wrong because the approvals connector is documented as a standard connector, and licences such as Power Automate, Office 365, and qualifying Dynamics 365 plans grant the standard-connector rights needed to create approval flows; no premium connector licence is required.

A logistics company manually re-keys delivery confirmations between two systems every day, and staff often forget to send the customer notification. Which Power Platform service is designed to optimise this business process by running an automated workflow between the apps and services involved?

• APower Automate, which creates automated workflows between apps and services to synchronise files, collect data, and send notifications.check_circle Correct
• BPower Apps, which builds custom business applications that let users enter and view organisational data through a tailored interface.
• CPower Pages, which creates and hosts secure external-facing websites that customers and partners use across browsers and devices.
• DDataverse, which securely stores and manages the data used by business applications across the Power Platform.

Why A is correct: Correct. Power Automate optimises business processes and automates repetitive tasks by creating automated workflows between apps and services to synchronise files, get notifications, and collect data, which is exactly the re-keying and notification work described.

Why B is wrong: Tempting because an app could capture the confirmations, but the grounding scopes Power Apps to building applications, not to running automated workflows between systems on a schedule.

Why C is wrong: Power Pages is for external-facing business websites per the grounding, not for automating an internal re-keying and notification process between back-office systems.

Why D is wrong: Dataverse is the data store per the grounding; it holds the data but does not itself run the workflow that moves and notifies between the two systems.

A hospital pulls patient-intake data from three separate systems and wants a single secure cloud store, organised into tables with role-based access, that Power Apps and Power Automate can both build on without re-integrating each source. Which Power Platform service delivers this?

• AMicrosoft Dataverse, which securely stores and manages business data in tables and integrates data from multiple sources into a single store.check_circle Correct
• BPower Automate, which optimises business processes by running automated workflows that synchronise files and move data between systems.
• CPower Apps, which lets makers build rich cross-platform business applications on top of the organisation's stored business data.
• DPower Pages, which creates and hosts the secure external-facing websites that partners and the public use across browsers and devices.

Why A is correct: Correct. Dataverse securely stores and manages data in a set of tables, applies role-based security, and integrates data from multiple sources into a single store that Power Apps and Power Automate can use, removing the need to re-integrate each source.

Why B is wrong: Power Automate can synchronise data per the grounding, but it automates processes rather than being the single secure table-based store the apps build on directly.

Why C is wrong: Power Apps consumes the data per the grounding, but it builds the application interface and is not itself the secure cloud store organised into tables.

Why D is wrong: Power Pages builds external websites per the grounding and reuses Dataverse data, but it is not the underlying store that consolidates the three source systems into tables.

A retail analyst wants Power Automate flows to read and write data held in the organisation's Salesforce, Dropbox and Office 365 accounts without anyone writing API integration code. Which Power Platform component is designed to link those external software-as-a-service applications to Power Platform products?

• AConnectors, which let apps, data and devices in the cloud be reached by Power Platform productscheck_circle Correct
• BPower Fx, the low-code language used to express formulas and business logic across Power Platform
• CDataverse, the cloud data service that stores rows and columns for enterprise-grade apps
• DPower Pages, the low-code platform for building external-facing business websites

Why A is correct: Correct. Connectors are the SaaS integration layer that lets apps, data and devices in the cloud talk to Power Platform products, with named examples including Salesforce, Office 365 and Dropbox.

Why B is wrong: Tempting because Power Fx is a core Power Platform capability, but it is the formula language for writing logic, not the integration layer that reaches external SaaS services.

Why C is wrong: Tempting because Dataverse stores business data, but it is internal storage for tables; it is connectors that expose actions and triggers against external services like Salesforce.

Why D is wrong: Tempting because it is external-facing, but Power Pages builds public websites; it does not provide the action-and-trigger bridge to Salesforce, Dropbox or Office 365.

A retail maker on the Power Pages home page cannot find a business-need template that matches the customer portal they want, and they prefer to design every page themselves from the ground up. Which option lets them start the site with nothing pre-built?

• ABlank page, which lets the maker customise the whole website from scratchcheck_circle Correct
• BPreview template, which opens device views of a selected starter layout
• CStarter layout, which applies a cross-industry solution to the new site
• DChoose this template, which provisions the highlighted business template

Why A is correct: Correct. When none of the business-need templates fit, the design studio lets makers choose a Starter layout or choose Blank page to customise the website from scratch, so Blank page is the start-with-nothing option.

Why B is wrong: Preview template only shows how a chosen template looks across devices; it previews an existing design rather than starting an empty site.

Why C is wrong: A Starter layout supplies a ready cross-industry solution, so the site is not blank; it is the choice for a generic head-start, not for building from scratch.

Why D is wrong: Choose this template confirms a specific business-need template and provisions it, which is the opposite of starting with nothing pre-built.

A retail loyalty website built on Power Pages lets shoppers sign in with their Microsoft account. When a shopper successfully signs in, which Power Pages web role is the resulting contact assigned to automatically?

• AThe Authenticated Users web role, which every signed-in contact receives by defaultcheck_circle Correct
• BThe Anonymous Users web role, which every contact receives until a maker reassigns it
• CThe System Administrator web role, which every contact receives for full site access
• DThe Restricted Access web role, which every contact receives until an invitation is redeemed

Why A is correct: Correct. Power Pages automatically assigns every authenticated user (contact) to the Authenticated Users web role, which then links them to the table and page permissions that grant access to protected content.

Why B is wrong: Tempting because it is the other built-in role, but the grounding ties the Anonymous Users web role to unauthenticated visitors, not signed-in contacts.

Why C is wrong: System administrator is a Dataverse or Entra role for makers and admins, not a web role automatically granted to ordinary site visitors who sign in.

Why D is wrong: No such default role exists in the grounding; the only two built-in web roles named are Authenticated Users and Anonymous Users.

In Power Pages, Microsoft Dataverse contact records represent the authenticated users of a site. Is this statement correct?

• AYescheck_circle Correct
• BNo

Why A is correct: Correct. The grounding states that Microsoft Dataverse contact records represent Power Pages users and that users gain access to the site through authentication, so a contact record stands in for each authenticated user.

Why B is wrong: Answering No is wrong because Power Pages does not store authenticated users in a separate identity store; it uses Dataverse contact records to represent them, and authenticated contacts are then assigned web roles.