How to pass Microsoft Power Platform Fundamentals (PL-900)
22 min read5 domains coveredFree practice, no sign-up
Microsoft Power Platform Fundamentals (PL-900) tests one thing above all: knowing which Power Platform component solves a given business problem. Microsoft hands you a short workplace scenario, usually a team drowning in a manual or repetitive task, and asks which service fits. Power Automate to run a workflow, Power Apps to build an interface, Power Pages to publish an external site, Copilot Studio for a conversational agent, or Dataverse to hold the shared data underneath. The exam is not about building anything; it is about matching a need to the right tool and knowing how the pieces connect.
It suits people who are new to the low-code world: business analysts, citizen developers, project managers, sales and operations staff, and students or career changers proving baseline Microsoft cloud literacy before moving on to a role-based certification such as PL-100 or PL-200. There is no coding requirement and no prerequisite. What carries you is having seen, even briefly, what each service looks like and being able to read a scenario and name the component that belongs to it.
The questions reward clear definitions and clean boundaries, not deep configuration. Many items are single-best-answer scenarios where two or three options describe real services and only one matches the verb in the question, automate, build an app, publish a site, store data. A good chunk are yes or no statements that test whether you know a precise fact, such as which encryption protects data in transit versus at rest, or whether sharing a model-driven app sends an email. Practising on scenario questions with a worked explanation, and a reason every wrong option is wrong, beats memorising marketing descriptions of each product.
PL-900 is a match-the-tool exam: almost every question is a short business scenario, and the right answer is the Power Platform component built for the verb in the question - automate, build an app, publish a site, or store the shared data.
Difficulty
Foundational
Best for
Business users and newcomers to low-code: analysts, citizen developers, project managers, sales and operations staff, students, and career changers who want a credible baseline in Microsoft Power Platform before a role-based certification.
Prerequisites
None. No coding and no prior Microsoft certification is required. Any hands-on exposure to Power Apps, Power Automate, or the Microsoft 365 ecosystem makes the scenarios far easier to read, but the exam assumes you are starting from fundamentals.
Typically 40 to 60 questions
Questions
45 min
Time allowed
700 / 1000
Pass mark
$99
Exam cost (USD)
258
Practice questions
How this exam thinks
One habit decides this exam: read the scenario for the verb, then pick the component built for it. Almost every question is a short business situation where a team needs to do something - eliminate re-keying, give staff a tailored screen, let outside customers self-serve, answer questions automatically, or keep one shared set of records - and the answer is the Power Platform service whose job is exactly that. Several options will name real services that sound plausible. Only one matches what the scenario actually asks.
The core map is small and worth owning cold. Power Automate runs automated workflows that move data and send notifications between apps. Power Apps builds custom business applications: canvas apps that connect to many data sources for a tailored experience, and model-driven apps built on Dataverse for data-dense, process-driven work. Power Pages publishes secure external-facing websites for customers and partners, built on the same Dataverse records staff already use. Copilot Studio builds conversational agents. Underneath them all, Dataverse is the shared low-code data platform, so an app, a flow, and an agent can all read and write one record set rather than copying data around.
The rest is a handful of precise distinctions the exam leans on. Canvas versus model-driven app turns on the data source and the kind of work. Standard versus premium versus custom connector turns on where the data lives and how you reach it. Automated versus instant versus scheduled flow turns on what starts the run. Environment Maker versus Environment Admin turns on whether you build resources or govern the environment. And on the governance side, know that TLS protects data in transit while Transparent Data Encryption protects it at rest, that data policies and tenant isolation reach Teams and Dataverse for Teams the same as other environments, and that each environment is bound to a geographic region. Name the verb or the precise fact, then choose the component or setting built for it.
What each domain tests and how to study it
The PL-900 blueprint is split across 5 domains. Weights are the official share of the exam; see the official exam guide for the authoritative breakdown.
What you must be able to do. Given a business problem stated in plain terms, identify which Power Platform service solves it, how the platform connects to Microsoft 365, Dynamics 365, Azure, and third-party apps, and which governance control applies.
In one sentenceThe why-and-which layer: matching a business need to the right Power Platform service and knowing how the suite is governed and connected.
Recall check: answer these from memory first
A team re-keys data between two systems daily and keeps forgetting to notify the customer. Name the service built to fix this and say why it is not Power Apps.
A council wants residents to self-serve against the same permit records staff already manage in Dataverse. Which service builds that external site, and why is no second copy of the data created?
Inside Microsoft Teams, which built-in component lets an app, a flow, and an agent all read and write one shared set of records?
What it tests. Whether you can read a business problem and name the service that solves it without writing code. It covers the business value of each service (Power Automate for workflow automation, Power Apps for custom applications, Power Pages for external sites, Dataverse as the shared store, and Dataverse for Teams as the in-Teams low-code platform); how Power Platform connects to Microsoft 365, Dynamics 365, Azure, and third-party applications through connectors; and platform administration and security, including environments, data policies, and tenant isolation that govern what makers can build and where data can flow.
How to study it. Learn each service by the one-line job it does and the verb that signals it: automate a process means Power Automate, build a tailored app means Power Apps, publish an external site on existing records means Power Pages, store the shared data means Dataverse. Drill the scenario form by covering the options and naming the service from the need alone. For governance, fix three facts: data policies and tenant isolation apply to Teams and Dataverse for Teams the same as other environments, environments are how administration and data residency are scoped, and Dataverse for Teams is the single shared platform that Power Apps, Power Automate, and Copilot Studio all build against inside Teams.
Easy to confuse
Power Automate versus Power Apps. Power Automate runs an automated workflow that moves data and sends notifications between apps and services; Power Apps builds a custom interface for people to enter and view data. If the verb is automate a process, it is Power Automate; if the verb is build an app to use, it is Power Apps.
Power Pages versus Power Apps. Power Pages creates secure external-facing websites for customers and partners, reusing the same Dataverse records; Power Apps builds internal business applications for staff. The deciding signal is who the users are - external public visitors point to Power Pages, internal staff point to Power Apps.
Dataverse versus Dataverse for Teams. Dataverse is the full low-code data platform used across the whole tenant; Dataverse for Teams is the built-in, lighter version scoped inside a Teams environment that Power Apps, Power Automate, and Copilot Studio build against. Choose Dataverse for Teams when the scenario keeps staff working inside Teams.
Worked example from the PL-900 bank
lock_openFree sampleDescribe the Business Value of Microsoft Power Platformeasy
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.
Power Automate is the service for automating repetitive processes and workflows that move data and send notifications between apps and services. 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 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.
What you must be able to do. Given a data, integration, or governance need, identify the core Power Platform component that fits, from Dataverse tables to standard, premium, and custom connectors to AI Builder, environment roles, and the platform's security model.
In one sentenceThe building-blocks layer: Dataverse structure, the three kinds of connector, AI and Copilot capabilities, environment roles, and how the platform secures and locates data.
Recall check: answer these from memory first
In Dataverse, what is the structure made of rows and columns where each column stores one type of data, and how does it differ from a solution and a business rule?
Which environment role lets a citizen developer create apps, connections, custom connectors, and flows but grants no administrative control over the environment?
Which mechanism encrypts Power Platform data in transit and which encrypts it at rest, and why is it wrong to say TLS provides encryption at rest?
What it tests. The core components that everything else is built on. It covers Dataverse as the underlying data platform (tables made of rows and columns, each column holding one data type, plus business rules and solutions); connectors that integrate data sources, split into standard, premium, and custom; AI Builder and Copilot capabilities for adding intelligence without code; environment roles such as Environment Maker and Environment Admin that scope who can build versus govern; and the security and residency model, where environments are bound to a geographic region and data is protected by TLS in transit and Transparent Data Encryption at rest.
How to study it. Pin down the vocabulary, because the traps here are precise. A Dataverse table is rows and columns where each column stores one type; a solution packages components, a business rule validates form data, a dataflow transforms incoming data - do not confuse them. Learn the connector ladder: standard connectors are included, premium connectors need a premium licence, custom connectors reach a source with no prebuilt connector. Memorise that Environment Maker builds apps, connections, custom connectors, and flows but cannot administer the environment, while Environment Admin governs it. For security, separate the two encryption mechanisms cleanly: TLS 1.2 or higher encrypts data in transit between devices and datacentres; Transparent Data Encryption encrypts data at rest on disk. Attributing at-rest encryption to TLS is a classic false statement.
Easy to confuse
Environment Maker versus Environment Admin. Environment Maker is the build role - it creates apps, connections, custom connectors, and flows inside one environment; Environment Admin is the govern role - it provisions the Dataverse database and manages users and roles. If the scenario wants to build resources without tenant control, it is Environment Maker.
TLS versus Transparent Data Encryption. TLS 1.2 or higher secures the connection between user devices and Microsoft datacentres, encrypting data in transit; Transparent Data Encryption performs real-time encryption of data as it is written to disk, providing encryption at rest. They are two distinct mechanisms protecting two different states of the data.
Standard versus premium versus custom connector. Standard connectors come included for common services, premium connectors reach licensed or enterprise sources and need a premium plan, and a custom connector lets a service reach an external source that has no prebuilt connector at all. The deciding factor is whether a connector exists and what licence it needs.
Worked example from the PL-900 bank
lock_openFree sampleDescribe the Core Components of Microsoft Power Platformeasy
A retail company asks a citizen developer to build a stock-takedown canvas app, its supporting flows, and the connections those flows rely on, all inside one environment. Which built-in environment role grants exactly the access needed to create those resources without granting tenant-level administrative control?
AEnvironment Maker, which lets the assignee create apps, connections, custom connectors, and Power Automate flows within that environmentcheck_circle Correct
BEnvironment Admin, which lets the assignee provision the Dataverse database and add or remove other users from environment roles
CSystem Administrator, which is the Dataverse security role used to manage the environment after a database is provisioned
DPower Platform administrator, the Microsoft Entra ID role that opens the security scorecard for the whole tenant
Environment Maker is the build role: it permits creating apps, connections, custom connectors, and flows, but not environment administration. The Environment Maker role exists so makers can create resources within an environment, specifically apps, connections, custom connectors, and flows using Power Automate, without holding administrative control over the environment or tenant.
Why A is correct: Correct. The Environment Maker role exists so makers can create resources within an environment, specifically apps, connections, custom connectors, and flows using Power Automate, without holding administrative control over the environment or tenant.
Why B is wrong: Tempting because admins can also create resources, but the Environment Admin role grants far more than building apps. It performs all administrative actions, which exceeds the access the developer needs.
Why C is wrong: Plausible because it appears in the same grounding, but System Administrator is a Dataverse security role used in place of Environment Admin after the database exists, not the role for citizen-developer resource creation.
Why D is wrong: Plausible because it is a real administrative role, but it is a tenant-wide Entra ID role for centralised security management, not the per-environment role that authorises building apps and flows.
What you must be able to do. Given an app requirement, choose between a canvas app and a model-driven app based on the data sources, the kind of work, and the user experience needed, and recognise how Power Apps integrates with portals, mobile, and Teams.
In one sentenceThe biggest domain: telling canvas apps from model-driven apps by their data source and the work they suit, and knowing how Power Apps fits the wider suite.
Recall check: answer these from memory first
A maker must combine records from SharePoint, an Excel workbook, and Salesforce on one screen. Which Power Apps type binds to that range of sources, and why not a model-driven app?
A team manages a data-dense sales process where users move constantly between related opportunity, contact, and account records. Which app type does Microsoft recommend, and why?
After you share a model-driven app with users, what does the maker still have to do for those users to reach it?
What it tests. How Power Apps lets people build custom applications without traditional code. It covers canvas apps, which start from a blank canvas and connect to many data sources through connectors for a hand-designed experience; model-driven apps, which are built on Dataverse with structured, component-driven layouts that suit data-dense, process-driven work; and the broader capabilities and use cases, including business rules for no-code form logic, sharing behaviour, mobile apps, portals, and Teams integration. This is the heaviest domain by weight, so the canvas-versus-model-driven distinction is worth owning cold.
How to study it. Make the canvas-versus-model-driven call automatic, because it is the most tested distinction on the exam. Canvas apps bind to many data sources - SharePoint, Excel, Salesforce, Dataverse - through connectors and let the maker hand-place every control, so they win when the scenario combines varied sources or wants a tailored screen. Model-driven apps read from Dataverse tables and generate structured layouts, so they win when the scenario is data-dense and process-driven, with users moving between related records like opportunities, contacts, and accounts. Learn the precise facts the yes-or-no items lean on: business rules apply form logic without JavaScript or plug-ins, and sharing a model-driven app assigns access but sends no email, so the maker must distribute the link separately.
Easy to confuse
Canvas app versus model-driven app. A canvas app connects to many data sources through connectors and is hand-designed control by control, ideal for tailored experiences over varied sources; a model-driven app is built on Dataverse and generates structured layouts, ideal for data-dense, process-driven work across related records. The data source and the kind of work decide it.
Sharing a canvas app versus sharing a model-driven app. Sharing a canvas app sends users an email with a link; sharing a model-driven app assigns access but sends no email, so the maker must obtain the direct web link and send it separately. Do not assume both notify users the same way.
Business rule versus JavaScript or plug-in. A business rule applies model-driven form logic - showing, hiding, setting, locking, or validating columns - through a no-code interface of conditions and actions; JavaScript and plug-ins are the pro-code routes for logic beyond what business rules cover. If the scenario says without writing code, it is a business rule.
Worked example from the PL-900 bank
lock_openFree sampleDescribe Microsoft Power Appseasy
A team needs an app to manage a data-dense sales process where users constantly move between related opportunity, contact and account records. Which Power Apps app type does Microsoft describe as especially well suited to this kind of process-driven scenario?
AA canvas app, because the maker hand-places every screen control
BA model-driven app, because it suits data-dense process workcheck_circle Correct
CA Copilot-generated app, because natural language builds it
DA SharePoint-list app, because the records live in a list
Model-driven apps are the recommended choice for data-dense, process-driven work spanning related records. Microsoft states model-driven apps are especially well suited to process-driven apps that are data dense and make it easy for users to move between related records, giving managing a sales process as an example.
Why A is wrong: A canvas app is a real app type and tempting for tailored UI, but Microsoft frames model-driven apps, not canvas, as especially suited to data-dense process-driven scenarios.
Why B is correct: Correct. Microsoft states model-driven apps are especially well suited to process-driven apps that are data dense and make it easy for users to move between related records, giving managing a sales process as an example.
Why C is wrong: Copilot can generate an app and its data model, but it is an authoring method rather than the app type Microsoft names as suited to data-dense process scenarios.
Why D is wrong: An app built on a SharePoint list is a valid canvas data source, but Microsoft names model-driven apps, not list-backed apps, for data-dense process-driven work.
What you must be able to do. Given a process that needs automating, identify the right flow type by what starts it - automated, instant, or scheduled - and tell cloud flows apart from desktop flows and robotic process automation.
In one sentenceThe automation layer: choosing the flow type from what triggers the run, and knowing when cloud flows give way to desktop flows and RPA.
Recall check: answer these from memory first
A cloud flow must begin on its own the moment a new record appears in a connected service, with nobody pressing a button and no fixed clock time. Which trigger type fits?
After a trigger starts a cloud flow, what is the sign-off step the flow performs called, and how does it differ from the trigger?
From which Microsoft surfaces can an approver respond to a Power Automate approval request without leaving their normal working tools?
What it tests. How Power Automate automates repetitive work. It covers cloud flows and their three trigger types - automated flows that start by themselves in response to an event, instant flows a person starts manually, and scheduled flows that run on a recurrence - plus the building blocks of triggers, actions, templates, and connectors; and desktop flows with robotic process automation for automating legacy and user-interface-based tasks that have no connector. It also covers where approvals surface, such as a Teams adaptive card, an Outlook email, or the Power Automate action centre.
How to study it. Anchor everything on what starts the flow, because that is how the exam frames the trigger questions. An automated trigger fires by itself when an event happens in a connected service, an instant trigger waits for a person to press a button, and a scheduled trigger runs on a fixed recurrence. Separate the two core vocabulary terms cleanly: the trigger is the configured event that begins each run, and actions are the steps the flow performs afterwards, such as requesting an approval. Know that templates are prebuilt flows you search by scenario and then edit, not packaging or connectors. For RPA, remember desktop flows automate legacy and UI-based tasks that have no connector, which is the signal to leave cloud flows behind.
Easy to confuse
Trigger versus action. A trigger is the configured event that begins each run of a cloud flow, such as a new item being added to a list; an action is a step the flow performs after it starts, such as sending an approval request. One starts the flow, the others are everything it does next.
Automated versus instant versus scheduled trigger. An automated trigger starts the flow by itself in response to an event, an instant trigger waits for a person to start it manually, and a scheduled trigger runs on a fixed recurrence. Read the scenario for what begins the run - an event, a button press, or a clock.
Cloud flow versus desktop flow (RPA). A cloud flow connects apps and services through connectors and runs in the cloud; a desktop flow uses robotic process automation to drive legacy and user-interface-based tasks that have no connector. If the scenario describes automating a system through its screen with no API, it is a desktop flow.
Worked example from the PL-900 bank
lock_openFree sampleDescribe Microsoft Power Automatemedium
A retail operations team builds a cloud flow that must begin on its own the moment a new record appears in a connected sales service, with nobody pressing a button and no fixed clock time. Which cloud-flow component fits how this flow needs to begin?
AAn instant trigger, so a team member starts the flow manually on demand whenever a sale is recorded
BA scheduled trigger, so the flow runs on a fixed recurrence such as every hour to check for new sales records
CA Start and wait for an approval action, so the flow begins once an approver reviews each new sales record
DAn automatic trigger, so the flow begins by itself in response to the new record event in the connected servicecheck_circle Correct
An automatic trigger starts a cloud flow by itself in response to an event, unlike instant (manual) or scheduled (recurring) triggers. Microsoft Learn explains that a cloud flow can be triggered automatically, instantly, or via a schedule, and that actions are the events a flow performs after the trigger starts it. An automatic trigger is the type that starts a flow by itself in response to an event in a connected service, which is what a flow reacting to a new record requires.
Why A is wrong: Instant is a real cloud-flow trigger type, which makes it tempting, but it starts the flow only when a person chooses to run it. The team wants the flow to begin by itself when data changes, so a manual instant start does not fit.
Why B is wrong: Scheduled is a genuine cloud-flow trigger type and is tempting because it removes manual effort, but it fires on a fixed clock recurrence rather than the instant a record appears. The scenario rules out a fixed time, so this lags behind the event.
Why C is wrong: Start and wait for an approval is a real grounded component, but it is an action the flow performs after the trigger starts it, not the mechanism that begins the flow. It pauses for a response rather than initiating the run on a data event.
Why D is correct: Correct. Microsoft Learn explains that a cloud flow can be triggered automatically, instantly, or via a schedule, and that actions are the events a flow performs after the trigger starts it.
What you must be able to do. Given a need to publish an external-facing site, recognise Power Pages as the answer, know how the design studio builds and structures pages, and identify how visitors and staff sign in.
In one sentenceThe external-site layer: knowing when Power Pages is the right service and how its design studio builds, nests, and secures pages.
Recall check: answer these from memory first
A maker cannot find a template matching the customer portal they want and prefers to design every page from the ground up. Which start option gives them a site with nothing pre-built?
In the Pages workspace editor, what is the gesture for adding a new horizontal band to the canvas before dropping in text and image components?
Which built-in identity provider lets staff sign in to a Power Pages site with their existing organisation account, and is it OpenID Connect or OAuth 2.0?
What it tests. How Power Pages builds secure, external-facing business websites on top of Dataverse. It covers when Power Pages is the right choice for a customer or partner portal; how the design studio works, including starting from a business-need template or a blank page, adding sections through the WYSIWYG editor, and nesting subpages that inherit their parent's page template; and how authentication works, with built-in identity providers split between OpenID Connect providers such as Microsoft Entra ID and OAuth 2.0 providers such as Google, LinkedIn, and Facebook for consumer sign-in.
How to study it. First, lock the trigger for the service itself: external-facing website for customers or partners, built on existing Dataverse records, means Power Pages. Then learn the design studio basics the exam asks about. Starting a site, choose a business-need template, a starter layout, or a blank page when nothing fits and you want to build from scratch. Adding content, hover over an editable section area and select the plus sign to add a section, then drop components in. Structuring, a new subpage inherits its parent page's page template. For authentication, separate the two provider families: Microsoft Entra ID is built in as an OpenID Connect provider for staff signing in with their organisation account, while Google, LinkedIn, Facebook, and similar consumer logins are built-in OAuth 2.0 providers.
Easy to confuse
Blank page versus starter layout versus business-need template. A business-need template provisions a site preconfigured for a scenario, a starter layout applies a cross-industry base, and a blank page starts with nothing so the maker customises the whole site from scratch. Choose blank page only when no template fits and full hand-design is wanted.
Microsoft Entra ID versus Google, LinkedIn, and Facebook sign-in. Microsoft Entra ID is built into Power Pages as an OpenID Connect provider for organisation accounts; Google, LinkedIn, and Facebook are built-in OAuth 2.0 providers for consumer sign-in. The exam tests which protocol family each provider belongs to, not just that they exist.
Adding a section versus styling a page. Adding a section means hovering over an editable section area and selecting the plus sign to insert a layout band you can fill with components; styling means opening the Styling workspace to apply themes and visual settings. One adds structure, the other changes appearance.
Worked example from the PL-900 bank
lock_openFree sampleDescribe Microsoft Power Pagesmedium
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
Blank page lets a maker build a Power Pages site from scratch when no template matches their needs. 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 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 study plan that works
Map the blueprint and book a date
Day 1
Read the official Microsoft PL-900 skills outline and the five domains with their weights. Book a provisional date now: a fixed date turns open-ended study into a plan and is the strongest predictor of actually sitting. Note that Power Apps is the single heaviest domain, so it earns the most attention, with the core components and the business-value, automation, and pages domains close behind.
Own the service map
Week 1
Before drilling any domain, learn the one-line job of each service until you can name it from a verb: Power Automate automates a workflow, Power Apps builds a custom app, Power Pages publishes an external site, Copilot Studio builds an agent, and Dataverse stores the shared data. Use the recall prompts in this guide - cover the options, choose the service from the need alone, then reveal. If you cannot pick from the scenario alone, you do not own it yet.
Go deep on Power Apps
Weeks 1 to 2
This is the largest domain, so it gets the most time. Drill the canvas-versus-model-driven call until the data source and the kind of work decide it without hesitation, and memorise the precise facts: business rules apply form logic with no code, and sharing a model-driven app sends no email. Practise on scenario questions and read the worked explanation on every one, including the ones you got right, watching for the detail that picks the answer.
Lock the core components and governance
Week 2
Pin the Dataverse vocabulary - table, solution, business rule, dataflow - and the connector ladder of standard, premium, and custom. Drill the two roles, Environment Maker builds while Environment Admin governs, and separate the encryption facts cleanly: TLS protects data in transit, Transparent Data Encryption protects it at rest. These yes-or-no facts are reliable marks once they are precise.
Cover automation and pages
Week 3
Power Automate rewards anchoring the flow type on what starts the run - automated for an event, instant for a button, scheduled for a clock - and telling cloud flows from desktop-flow RPA. Power Pages rewards knowing the design-studio basics and the OpenID Connect versus OAuth 2.0 split between identity providers. Both are learnable and tie straight back to a clear trigger or fact, so they are dependable marks.
Drill weak domains, then space the review
Week 3 to 4
Use your per-domain accuracy to attack the domains dragging you down, not to re-read what you already know. Then space it: revisit each domain's recall prompts after a few days and again a week later. Spacing roughly doubles what sticks compared with cramming, which matters for the precise yes-or-no facts.
Sit a timed mock and calibrate
Week 4
Take at least one full timed mock under exam conditions to rehearse pacing and the flag-and-return habit. Treat the score as a per-domain readiness signal, not a single number, and review every missed question, naming the verb or fact you misread, before you book or sit.
Know when you're ready
Readiness for PL-900 is a score on fresh scenario questions you have not seen before, not a feeling that the products sound familiar. Those are different things, and the gap between them is where unprepared candidates lose marks. Re-reading product descriptions builds fluency, and fluency feels like knowledge, so confidence rises while real recall does not. The fix is to test yourself: if you can read a new scenario, spot the verb or the precise fact, and pick the right component while explaining why each other option is wrong, you know it; if you can only nod along to an explanation, you do not yet. Set the bar at clearing every domain comfortably on unseen questions across more than one session, with particular confidence on the canvas-versus-model-driven call and the governance yes-or-no facts, rather than scraping a single pass.
Ready to put this into practice?
Free PL-900 questions with worked explanations. No sign-up.
Read the scenario for its verb first. Automate a process, build an app, publish an external site, or store the shared data - the verb usually points straight at the one service that belongs to the question.
Tell canvas from model-driven apps by the data and the work. Many varied sources or a hand-designed screen means canvas; data-dense, process-driven work across related Dataverse records means model-driven. This is the most tested distinction, so make it automatic.
On flow questions, identify what starts the run. An event in a connected service means an automated trigger, a person pressing a button means instant, and a fixed clock time means scheduled.
Watch the yes-or-no facts closely. Items like TLS versus Transparent Data Encryption, or whether sharing a model-driven app sends an email, test one precise fact - read every word and do not answer on a vague impression.
Separate who builds from who governs. Environment Maker creates apps, connections, custom connectors, and flows; Environment Admin provisions the database and manages users. Match the role to whether the scenario builds resources or administers the environment.
Flag and move on. Cover every question once before you spend time on a hard one, so you collect the clear marks first and protect the ones you actually know.
Frequently asked questions
Is PL-900 hard?
No, it is a foundational, entry-level exam with no coding and no prerequisite. The difficulty is matching a business need to the right Power Platform service and knowing a set of precise facts about the core components, not deep configuration. Scenario practice with worked explanations matters far more than memorising product descriptions.
How long should I study for PL-900?
Most candidates are ready in two to four weeks of steady part-time study. Less exposure to Power Apps and Power Automate means more time on the service map and the canvas-versus-model-driven distinction, which is the single most tested decision on the exam.
Do I need to know how to code?
No. PL-900 is about understanding what each low-code service does and choosing the right one, not writing programs. It even tests that no-code features such as business rules apply form logic without JavaScript or plug-ins, so the emphasis is firmly on the low-code, no-code value of the platform.
Which domain should I focus on?
Power Apps is the heaviest domain by weight, so the canvas-versus-model-driven call deserves the most time. The core components domain is close behind and rewards precise vocabulary and the governance facts, so do not leave it short. Business value, automation, and pages round out the rest and tie back to a clear verb or fact.
Is hands-on practice required to pass?
It is not required, but even a little time clicking through Power Apps, building a simple Power Automate flow, and opening the Power Pages design studio makes the scenarios far easier to read. You can pass on study alone, but practical exposure turns abstract definitions into recognition.
What should I do the week before the exam?
Sit at least one full timed mock to rehearse pacing and the flag-and-return habit, then use your per-domain accuracy to drill only the domains dragging you down. Revisit the recall prompts for the precise yes-or-no facts, and review every missed question by naming the verb or fact you misread.
Does PL-900 lead anywhere?
Yes. It is the natural starting point before role-based Power Platform certifications such as PL-100 for app makers or PL-200 for functional consultants. Passing it proves a credible baseline in the suite and the vocabulary those later exams assume you already have.
Is the Power Platform Fundamentals certification worth it?
PL-900 is worth it for people entering or transitioning into roles that use the Microsoft Power Platform - including business analysts, administrators, and consultants working in Microsoft-centric organisations. It gives you a structured vocabulary for Power Apps, Power Automate, Power Pages, and Dataverse, and it provides credible grounding before the more demanding role-based certifications. For those new to the Microsoft ecosystem, it is a genuinely efficient foundation rather than a checkbox.
Examworthy is not affiliated with or endorsed by Microsoft. This guide is original study material based on the public exam blueprint. We never reproduce live exam items. PL-900 and related marks belong to their respective owners.
