PL-400 — Power Platform Developer Associate
I treat PL-400 as a developer-tier exam, not a maker-tier one. The questions go past drag-and-drop flows and into Dataverse plug-in execution pipelines, PCF control lifecycle, and ALM solution layering. If you have been living in the Power Apps canvas editor without touching TypeScript or the Dataverse SDK, this exam will find the gaps quickly.
Exam at a glance
| Detail | Value |
|---|---|
| Provider | Microsoft |
| Exam code | PL-400 |
| Full name | Microsoft Power Platform Developer Associate |
| Duration | 120 minutes |
| Question count | 40–60 (varies per form) |
| Passing score | 700 / 1000 |
| Exam fee | ~$165 USD |
| Validity | Annual renewal (Microsoft Learn assessment) |
| Delivery | Pearson VUE — in-person or online proctored |
| Retake policy | 24-hour wait after first fail; 14 days after second; capped at 5 attempts in 12 months |
What's tested
Microsoft weights PL-400 across six technical areas. The percentages shift slightly between exam versions but these ranges have been stable.
Create a technical design (20–25%). Selecting the right component for a business requirement — when a canvas app beats a model-driven app, when a plug-in beats a Power Automate flow, when a PCF control is warranted versus a standard column. This section rewards breadth.
Configure Microsoft Dataverse (15–20%). Table types (standard, virtual, elastic), column data types, calculated and rollup columns, relationships, security roles, field-level security, business rules, and the Dataverse Web API. Know the difference between server-side and client-side logic execution points.
Create and configure Power Apps (15–20%). Model-driven app customization (forms, views, charts, sitemap), canvas app formulas and connectors, responsive layouts, component libraries. Expect questions that mix both app types in a single scenario.
Configure business process automation (10–15%). Dataverse plug-ins (pre/post-operation, sync/async), Power Automate cloud flows, business process flows, and workflows (classic). The exam still includes classic workflow questions even though they are being deprecated — read the exam guide before assuming they dropped them.
Extend the user experience (10–15%). Power Apps Component Framework (PCF) — the full lifecycle: manifest, control class, init/updateView/getOutputs/destroy, virtual vs standard controls, test harness. TypeScript fluency is assumed here.
Extend the platform (15–20%). Custom connectors (OpenAPI definition, OAuth authentication, throttling policies), plug-in registration tool, service endpoints, Azure integration via Dataverse. Also covers Azure Functions as integration middleware.
Develop integrations (5–10%). Connecting Dataverse to external systems — Azure Service Bus, webhooks, virtual tables backed by OData sources. Lighter domain but the questions tend to be scenario-based and time-consuming.
Common exam traps
Plug-in vs Power Automate for the same requirement. Both can trigger on a Dataverse record create. The distinction is execution context: plug-ins run synchronously inside the Dataverse transaction (can roll back), Power Automate flows run outside the transaction (cannot roll back data changes). Questions will describe a scenario that needs transactional integrity and expect you to choose the plug-in — but frame it in a way that makes the flow look simpler. Simpler is wrong here.
PCF virtual controls vs standard controls. A virtual control renders entirely in React and does not produce a DOM element in the traditional sense; a standard control does. Virtual controls perform better in model-driven apps but have restrictions on what APIs they can call (no navigation API, limited dataset). The exam tests whether you know when each restriction matters.
Solution layers and ALM order. Managed vs unmanaged solutions get tested in deployment scenarios. A common trap: importing an unmanaged layer on top of a managed base layer for a customization — this works in dev but breaks when you try to export and deploy the customization separately. The safe pattern (customization layer as managed on top of managed base) is the answer Microsoft expects.
The typeof gap in canvas formula language. Canvas Power Apps uses Power Fx, not JavaScript. Formulas like IsBlank, IsEmpty, Coalesce behave differently than their JavaScript equivalents, and questions test edge cases — specifically IsBlank("") (true in Power Fx, unlike most languages) versus IsEmpty([]) (true only for empty tables/collections).
Dataverse environment variables vs hardcoded connection references. Any solution that uses a connection to an external service should use connection references and environment variables — not hardcoded values. The exam tests whether you can identify a solution design that would break at deployment because the developer skipped this. Forum posts consistently flag this as the most common failure point for people with practical experience but no formal ALM training.
How ARIA prepares you for PL-400
My evaluation covers all six PL-400 domains with CAT-calibrated questions. Most candidates land in one of two profiles: strong on app building, weak on platform extension (PCF + plug-ins), or the reverse. The CAT identifies which within the first 10 questions and weights the roadmap accordingly.
For a developer with Dataverse experience but no PCF background, expect a 4-phase roadmap. Phase 1 covers Dataverse internals and the plug-in execution model. Phase 2 goes into Power Fx depth and ALM. Phase 3 focuses on PCF, custom connectors, and integration patterns. Phase 4 is scenario drilling — the mixed-requirement questions that make up the bulk of the harder exam items.
Timeline by baseline: a developer who works with Power Platform daily typically needs 5–7 weeks. Someone coming from a pure .NET background without Power Platform exposure should plan for 10–12 weeks.
Pass guarantee for PL-400
PL-400 qualifies for the ClaudeLab pass guarantee under the standard five conditions: CAT evaluation completed, all roadmap milestones passed, readiness score at or above 80 before the attempt, at least 21 days of active prep, and the milestone history showing no repeated failures. Check the five conditions in detail.
Related certifications
If you are building toward the Power Platform solution architect track, PL-900 (Power Platform Fundamentals) establishes the vocabulary before PL-400 goes deep. On the Dynamics 365 side, MB-910 (Dynamics 365 Fundamentals CRM) covers the business applications that Power Platform extends — useful context for the integration domain. The expert-level path after PL-400 includes PL-600 (Solution Architect), which is not yet in the ClaudeLab catalog but is on the roadmap.
Start your PL-400 roadmap
Start your PL-400 roadmap with ARIA → claudelab.me
ARIA runs the CAT evaluation first, maps your actual level against all six PL-400 domains, and generates a roadmap built around what you do not know yet — not a generic study guide. The PCF and plug-in sections are where most developers lose points; that is where the roadmap will focus.