Microsoft Power Platform Developer (PL-400) — Free Practice Questions
10 free sample questions from a bank of 446, with the correct answers and explanations. No signup required — start practising right now.
1A company manages capital equipment for an electric utility company. The company has a SQL Server database that contains maintenance records for the equipment.
Technicians who service the equipment use the Dynamics 365 Field Service mobile app on tablet devices to view scheduled assignments. Technicians use a canvas app to display the maintenance history for each piece of equipment and update the history.
Managers use a Power BI dashboard that displays Dynamics 365 Field Service and real-time maintenance data.
Due to increasing demand, managers must be able to work in the field as technicians.
You need to design a solution that allows the managers to work from one single screen.
What should you do?
Add the maintenance history app to the Field Service Mobile app.
Add the manager Power BI dashboard to the Field Service mobile app.
Create a new maintenance canvas app from within the Power BI management dashboard.
Add the maintenance history app to the Power BI dashboard.
Answer: D
The short version
D — Embed the maintenance canvas app in the Power BI manager dashboard. Managers need Field Service context plus real-time maintenance history in one view. The settled key is D because Power BI can host the app where managers already work.
Key concepts in this question
Field Service mobile: technician app for assignments on tablets in the field.
Maintenance canvas app: history display plus update tool built for equipment records.
Power BI dashboard: manager view joining Field Service and real-time maintenance signals.
Embedding pattern: surfacing a canvas app inside Power BI so actions happen without app switching.
Reverse embed: putting dashboards in mobile adds manager overhead instead of meeting them in BI.
Why D is correct
D is correct because managers live in Power BI for cross-equipment insight, yet need to act on maintenance history. Adding the maintenance app to that dashboard gives one place to see Field Service plus SQL-backed history and update it. Building a new app from BI or stuffing BI into mobile misses the settled workflow of enhancing the manager surface.
Why the others are wrong
A. Adding history to Field Service mobile helps techs, not managers who monitor in Power BI.
B. Adding manager BI to mobile forces managers into field workflows instead of their dashboard.
C. Creating a new app from BI duplicates the working maintenance app without integration gain.
PL-400 exam tip
Meet managers in Power BI by embedding the canvas app; meet techs in Field Service mobile.
2You are implementing custom business logic in a Power Apps portal.
You need to use Liquid templates to display dynamic content.
To which three entities can you include Liquid code? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Content snippet
Web page
Web template
Page template
Portal settings
Answer: A, B, C
The short version
ABC — Content snippet, web page and web template accept Liquid. Portals render dynamic content wherever HTML or text is allowed. The settled key is ABC because those three are the documented Liquid hosts.
Key concepts in this question
Liquid templates: portal language for dynamic lists, conditions and record values.
Content snippet: reusable HTML or text fragment shown across portal pages.
Web page: portal content node that can carry copy plus Liquid for dynamic display.
Web template: layout plus logic wrapper where Liquid controls structure and data.
Page template and portal settings: configuration records, not content surfaces for Liquid rendering.
Why ABC is correct
ABC is correct because Microsoft Learn states Liquid can be used anywhere portals accept HTML or text, including web templates, webpages and content snippets. Those three expose content bodies that the portal engine parses for Liquid tags. Page templates and portal settings store layout choice or config values rather than renderable content, so they fall outside the settled trio.
Why the others are wrong
D. Page template selects layout structure but is not itself a Liquid content host here.
E. Portal settings hold key-value config, not dynamic HTML content for Liquid.
PL-400 exam tip
For portal Liquid think snippet plus page plus web template; settings and page template are out.
3You are configuring a custom connector for a web service. The web service is hosted in two different regions. The web service URL includes a common domain name and a unique sub-domain for each region.
The custom connector must allow the region to be entered for additional regions when creating the connection.
You need to create a policy template.
Which template type should you use?
Set HTTP header
Route request
Set host URL
Set query string parameter
Answer: C
The short version
C — Set host URL handles regional subdomains correctly. Policy templates transform requests, and Set host URL rewrites the hostname from connection parameters. With one common domain plus per-region subdomains, parameterizing the host lets makers enter current and future regions without rebuilding. Header, route, and query templates address other layers and cannot compose the host.
Key concepts in this question
Connector: Wraps REST service exposing actions to apps with connection parameters.
Host template: Resolves parameterized hostname such as region subdomain plus domain per connection.
Route contrast: Forwards to a fixed backend, not a variable host from input.
Query and header: Append parameters or metadata while host stays static.
Why C is correct
Late-bound hostname is required when regions are entered dynamically. Set host URL stores the domain once and injects the subdomain at runtime, so new regions work by typing a value. Other templates would need redeploys or misuse HTTP layers. The settled template alone meets the dynamic-region demand.
Why the others are wrong
A. header adds tracking or auth metadata without changing the regional host.
B. route request pins a fixed endpoint, opposite of supporting future regions.
D. query string adds defaults, never reconstructing a subdomain host.
PL-400 exam tip
Variable subdomain plus common domain equals Set host URL.
4A company is migrating from an on-premises Dynamics 365 installation to a Power Platform solution. You are creating plug-ins for the new solution.
You need to register the plug-ins.
Which isolation mode should you use?
None
Global Assembly Cache (GAC)
Sandbox
Disk
Answer: C
The short version
C — Register online plug-ins in Sandbox isolation. Power Platform cloud forbids full-trust or GAC deployment. The settled key is C because Sandbox is the only supported online mode.
Key concepts in this question
Plug-ins: .NET logic that runs on Dataverse events for validation and automation.
Sandbox isolation: partial-trust worker that secures cloud execution and resource use.
None and Disk: on-premises or legacy options tied to server filesystem access.
GAC deployment: machine-wide assembly sharing unsuitable for multi-tenant online.
Migration context: moving from on-premises to Power Platform requires re-registration under cloud rules.
Why C is correct
C is correct because all online plug-ins must run isolated in Sandbox to protect the shared service. None would mean full trust, while GAC and Disk assume access to server storage that online does not grant. Choosing Sandbox satisfies the platform registration validator and aligns with Always C guidance for Dataverse online.
Why the others are wrong
A. None implies no isolation and is rejected for online Dataverse plug-ins.
B. GAC requires server-wide install rights unavailable in the online multi-tenant cloud.
D. Disk assumes local file deployment paths that online registration does not use.
PL-400 exam tip
For online plug-ins always choose Sandbox; GAC, Disk and None belong to on-premises.
5An organization uses a public-facing Power Apps portal.
You need to change the layout of a specific web page.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Select the Portal Management app and then select Edit.
Select the Portal Management app and then select Play.
Select the portal app and then select Manage.
Select the portal app and then select Edit.
Answer: B, D
The short version
BD — Edit the portal via Portal Management Play or portal app Edit. Layout of a specific web page can be reached from studio or management paths. The settled key is BD because those two navigation pairs open the designer.
Key concepts in this question
Portal Management app: model-driven admin surface for portal records and content.
Play action: run path that can surface editing for portal content in this bank flow.
Portal app Edit: maker-studio entry that opens the selected portal for page layout work.
Portal app Manage: administrative settings area, not the page-layout editor here.
Portal Management Edit: plausible but not the settled path for this layout task.
Why BD is correct
BD is correct because the settled flags mark Portal Management plus Play and portal app plus Edit as the two working routes to the page layout. One path uses the management app runtime to reach content, the other uses the maker studio edit experience. Manage and the alternate Edit combo do not lead to the page canvas in this key, leaving B plus D as complete solutions.
Why the others are wrong
A. Portal Management plus Edit is not a flagged route to the page layout in this key.
C. Portal app plus Manage opens administration rather than the page design surface.
PL-400 exam tip
For portal page layout remember Management-Play and portal-Edit as the two settled routes.
6You are building a custom application in Azure to process resumes for the HR department.
The app will monitor submissions of resumes and parse the resumes.
You need to parse the resumes and save contact and skills information into the Common Data Service.
Which mechanism should you use?
Power Automate
Common Data Service plug-in
Web API
Custom workflow activity
Answer: A
The short version
A — Power Automate parses resumes into Dataverse contact and skill rows. Monitoring submissions plus AI extraction plus data writes fits a cloud flow. The settled key is A because it covers trigger, parsing and save without custom code.
Key concepts in this question
Resume intake: file or email arrival that should start an automated pipeline.
AI Builder plus parsing: extraction of contacts, skills and experience from unstructured docs.
Dataverse save: creation of contact and skill records for HR search and reporting.
Plug-ins: sync Dataverse logic for validation, not for watching Azure file drops.
Web API and custom workflow: building blocks that need a host process rather than being the end-to-end mechanism.
Why A is correct
A is correct because Power Automate can monitor submissions, call resume parsing, and write contact plus skill entities to Dataverse in one flow. That matches the need to process HR documents continuously with low code. Plug-ins react inside Dataverse rather than polling intake, while raw Web API or custom workflow activity would require extra orchestration that Power Automate already provides.
Why the others are wrong
B. Dataverse plug-in runs on record events and does not monitor external resume submissions.
C. Web API is an interface to call, not the monitoring plus parsing pipeline itself.
D. Custom workflow activity extends logic but still needs a flow or process to drive intake.
PL-400 exam tip
For monitor plus parse plus save to Dataverse choose Power Automate with AI extraction.
7You are a Power Apps maker creating a chat bot for a website.
The chat bot must recognize geographic attributes to enable additional functionality.
You need to recommend a feature.
What should you recommend?
Fallback topic
Power Automate Flow
Bot Service compliance
Slot filling
Answer: D
The short version
D — Slot filling recognizes geographic attributes for the bot. Bots use entities and slot filling to pull city, country, or postal values from free text. Once the geographic slot fills, the bot branches or personalizes by location. Fallback handles unmatched input, flows act after extraction, and compliance governs handling, none performing extraction itself.
Key concepts in this question
Slot filling: Prompts across turns until each required entity has a usable value.
Geo entities: Prebuilt or custom models resolving abbreviations and full names to one value.
Fallback: Triggers on no match, not parsing attributes from matched intents.
Flow: Consumes extracted slots but needs capture to have happened first.
Why D is correct
Slot filling declaratively recognizes city or country without code. The bot clarifies until geography is present, then region logic enables extra functionality. Other options react afterward or handle failure rather than extraction, making the settled recommendation the complete answer.
Why the others are wrong
A. fallback catches misunderstandings without extracting structured geography.
B. flow consumes location but first needs slot filling to recognize it.
C. compliance addresses retention, not language understanding.
PL-400 exam tip
Recognize attributes from chat equals slot filling with entities.
8A Power Platform solution includes the following Web API call:
GET http://contoso.crm.dynamics.com/api/data/v9.1/RelationshipDefinitions?$select=SchemaName
You need to explain what this line of code is doing.
What does the code do?
Retrieve the list of relationships between tables.
Retrieve a list of tables that are related to each other.
Retrieve a list of one-to-many relationships with other tables.
Retrieve a list of tables that have more than one relationship.
Retrieve a list of many-to-many relationships with other tables.
Answer: A
The short version
A — The call lists relationship definitions between tables. RelationshipDefinitions with SchemaName returns metadata for every relation. The settled key is A because that entity set is relationship-centric.
Key concepts in this question
Web API metadata: queryable definitions for tables, columns and relations in Dataverse.
RelationshipDefinitions: entity set exposing one-to-many, many-to-many and related metadata.
SchemaName select: projection that returns the logical name of each relationship.
Table lists: retrieved from EntityDefinitions, not from this relationship feed.
Filtered subsets: more specific navigation queries would be needed for only one cardinality.
Why A is correct
A is correct because docs show GET on RelationshipDefinitions with select SchemaName enumerating all relationship metadata available to the caller. The response includes one-to-many, many-to-one and many-to-many entries rather than just tables or a single cardinality. Options about tables or single-type subsets therefore understate what the line returns.
Why the others are wrong
B. Tables themselves come from entity metadata, not from the relationship-definition feed.
C. One-to-many only is too narrow; the feed covers all cardinalities.
D. Having more than one relation describes a filter not present in this broad query.
E. Many-to-many only is likewise a subset of the full relationship list returned.
PL-400 exam tip
RelationshipDefinitions means all relationships; EntityDefinitions means tables themselves.
9You develop and deploy a Power Apps solution.
The following changes must be made to the solution:
• Delete a column of data.
• Modify several views.
• Add several charts to dashboards.
You need to re-deploy the app.
What should you do?
Update the solution.
Upgrade the solution.
Create a new solution.
Patch the solution.
Answer: B
The short version
B — Upgrade the solution to delete the column and roll up changes. Solution lifecycle offers update, upgrade, and patch, where only upgrade replaces the target while removing absent components and merging patches. Deleting a column needs that removal semantic, while views and dashboards ride in the new version. Update would orphan the column and patch suits small additive fixes.
Key concepts in this question
Upgrade: Installs new version as active layer, drops removed parts, merges prior patches.
Update contrast: Overlays without deleting missing parts, so deleted columns persist.
Patch contrast: Minor additive changes atop a base, unsuitable for deletions and broad rework.
New solution: Loses lineage and complicates dependencies without benefit.
Why B is correct
Because the set deletes a column, deployment must use the operation whose contract includes deletion. Upgrading drops the column, refreshes views and dashboards, and collapses history for clean servicing. Update would strand the column and patch would violate constraints, so the settled action follows documented semantics.
Why the others are wrong
A. update retains the deleted column because absent parts are never removed.
C. new solution discards lineage and forces dependency rework.
D. patch cannot carry deletions or broad rework and fragments versions.
PL-400 exam tip
Delete plus consolidate equals upgrade, retain equals update.
10You are creating a canvas app to retrieve user sign in information from Microsoft Azure Active Directory (Azure AD) when someone searches for information about an end user.
You create an Azure Function to retrieve the required information by using JSON.
You need to ensure that the application functions correctly.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Create a Power Automate flow to import data.
Create a custom connector by using the Azure Function API.
Use app designer in the Power Platform admin center.
Use Azure Service Bus.
Create an API definition for the Azure Function.
Answer: B, E
The short version
BE — Create an API definition then a custom connector from the Azure Function. Canvas apps reach Azure AD data through a typed connector, not a data import flow. The settled key is BE because both steps wire the function to the app.
Key concepts in this question
Azure Function: JSON API that looks up sign-in info from Azure AD for the canvas app.
API definition: OpenAPI description that details operations, params and responses.
Custom connector: Power Platform wrapper that exposes the function as a canvas data source.
Power Automate import: batch data movement, unnecessary when the app calls live JSON.
Service Bus and app designer: messaging fabric and admin tooling, not the app-to-function bridge.
Why BE is correct
BE is correct because the function must first be described with an API definition so the platform knows its contract. Creating a custom connector from that API then lets the canvas app call it securely and bind JSON results to search. Flows, Service Bus and admin-center designer do not establish that typed app-to-function link.
Why the others are wrong
A. Import flow is for bulk loads, not for live per-search JSON lookup from the app.
C. App designer in admin center manages apps, but does not expose the function to canvas.
D. Service Bus decouples messages and adds no canvas-callable function binding here.
PL-400 exam tip
For canvas plus Azure Function remember API definition first, custom connector second.