PL-400 study guide
The sections follow the official domains. "Extend the platform" is 30–35% of the exam, about as much as the next three domains combined, so it gets the most space.
Know Cold Vs Searchable On Learn
Know cold
Know these without lookup:
- which tool or layer is correct
- which execution stage is correct
- sync vs async choice
- Web API vs Organization service vs custom API choice
- plug-in vs webhook vs Service Bus vs cloud flow choice
- security role vs column security vs role-based form choice
- managed vs unmanaged vs active unmanaged layer choice
Searchable on Learn
Safe to confirm quickly once you already know the family of answer:
ScriptBase,Script,ExecuteAsyncx-ms-capabilities,x-ms-dynamic-valuesfeature-usage,uses-feature,Device.getCurrentPosition@odata.bind,Prefer: return=representationExecutePrivilegeName,IsPrivate,WorkflowSdkStepEnabledRetry-AfterWebhookKey
Do not memorize
Do not waste cycles on:
- long code samples
- full payloads beyond one anchor property
- answer-key memory without the decision rule
1. Create A Technical Design (10-15%)
Know cold
| Requirement shape | Default answer |
|---|---|
| Simplest native rule on forms/columns | Business rule |
| Immediate server-side validation/error in classic PL-400 framing | Real-time workflow |
| In-transaction Dataverse logic | Plug-in |
| Client/form/command behavior | JavaScript + Client API |
| Async orchestration or external-process automation | Cloud flow |
| Long-running or heavy external compute | Azure Function |
| External API surfaced into app/flow | Custom connector |
| External data stays outside Dataverse | Virtual table |
| High-scale Dataverse storage/workload | Elastic table |
Decision rules
- If the question says least customization, most native, or lowest operational burden, prefer the simplest built-in component that fully satisfies the requirement.
- If the question is really asking where does this logic belong, answer that before thinking about exact syntax.
- If the requirement is inside the Dataverse transaction, do not drift to cloud flow.
- If the requirement is surface an external API, the answer is often a custom connector, not "just write code."
- If the requirement is external data without copying it into Dataverse, think virtual tables.
- If the requirement is high-throughput Dataverse-backed storage, think elastic tables.
Exact anchors to keep searchable
elastic tablesvirtual tablesdata loss prevention (DLP) policiesAccess Dynamics 365 as organization users
2. Build Power Platform Solutions (10-15%)
Know cold
| Situation | Correct read |
|---|---|
| Build and edit components | Unmanaged solution |
| Ship downstream | Managed solution |
| Managed behavior looks wrong in target | Check active unmanaged layer |
| Dependency looks missing | Verify it was published and included |
| Grant table/record access | Security role |
| Restrict one field | Column-level security |
| Hide/show different UI to different audiences | Role-based form |
Decision rules
Unmanagedis for authoring.Managedis for transport and downstream protection.- If prod or test behavior differs from what you shipped, suspect an active unmanaged layer before reinventing the bug.
- If a classic workflow or solution component seems missing, suspect publish/dependency problems before assuming deployment corruption.
- For environment variables:
Current Valuewins if present.Default Valueis fallback.- If you do not want a target environment to inherit the current value, remove that value from the solution before export.
- For solution cloud flows, changed environment-variable values can keep the old value until the flow is saved or turned off/on again.
Exact anchors to keep searchable
Current ValueDefault ValueenvironmentvariablevaluePower Platform PipelinesBuild Tools
Learn-grounded reminders
- Microsoft Learn says environment-variable values are derived from the variable and can change across imported environments.
- Microsoft Learn also says
Current Valueis optional, separate from the definition, and should be removed from the solution if you do not want to use it in the next environment. - Microsoft Learn says flows can keep using the previous environment-variable value until they are saved or turned off/on again.
3. Implement Power Apps Improvements (10-15%)
Know cold
| Need | Default answer |
|---|---|
| Inspect app runtime behavior | Monitor |
| Add your own debug/telemetry messages | Trace |
| Simplify complex formula readability | With |
| Let a reusable component read app-level collections or vars | Access app scope |
| Investigate model-driven client behavior | Monitor + browser dev tools + Fiddler |
Decision rules
- Treat this area as a cheap-points lane, not a deep-theory lane.
- If the stem is about observing request/response behavior or runtime diagnostics, start with
Monitor. - If the question wants the formula construct that improves readability and avoids repeated subexpressions, think
With. - If the question wants custom log output for Monitor, think
Trace.
Exact anchors to keep searchable
Application Insights connection stringMonitorTraceWithAccess app scope
Learn-grounded reminders
4. Extend The User Experience (10-15%)
Know cold
| Need | Answer |
|---|---|
| Filter a lookup before results show | addPreSearch |
| Show blocking wait state | Xrm.Utility.showProgressIndicator() |
| Show control-specific message | addNotification |
| Show form-level message | setFormNotification |
| Show command only when rows are selected | CountRows(Self.Selected.AllItems) > 0 |
| Share JS used by a command | add the web resource as a dependency |
PCF know-cold items
- Packaging flow:
text
npm run build
-> npm start
-> pac solution init
-> pac solution add-reference
-> msbuild /restore- Manifest class name must match the implementation class.
- Device features are not magic: declare them in the manifest.
feature-usagewrapsuses-feature.uses-featurerequires bothnameandrequired.
Decision rules
addPreSearchis about lookup filtering right before search, not a random page-load event.- Register the callback up front, then let the lookup invoke it when the user searches.
- Notification questions are usually about scope:
- control problem -> control notification
- whole form/status problem -> form notification
- PCF questions are often not about React or TypeScript logic. They are about manifest, capability declaration, or build/package order.
Exact anchors to keep searchable
addPreSearchfeature-usageuses-featureDevice.getCurrentPositionshowProgressIndicator
Learn-grounded reminders
- Microsoft Learn says
addPreSearchapplies changes to lookups just as the user is about to view results. - Microsoft Learn says
feature-usagewrapsuses-feature. - Microsoft Learn says
uses-featurerequiresnameandrequired. - Microsoft Learn documents
context.device.getCurrentPosition()as the PCF device geolocation API.
5. Extend The Platform (30-35%)
5A. Plug-ins and custom APIs
Know cold
| Pipeline stage | Rule |
|---|---|
PreValidation | reject/cancel early |
PreOperation | mutate incoming values |
MainOperation | internal only except custom API / custom virtual table providers |
PostOperation | react after core operation; async handoff starts here |
| Plug-in detail | Rule |
|---|---|
Change Target before write | PreOperation |
| Cancel safely | prefer PreValidation |
| Pass data between steps | SharedVariables |
| Compare old/new values | use images before extra retrieves |
| Read/write Dataverse rows in code | IOrganizationService |
| Trace/debug | ITracingService |
| Runtime context | IPluginExecutionContext |
Entity-image rules
- No
Pre ImageonCreate. - No
Post ImageonDelete. Post Imageexists only for steps inPostOperation.- Include only the columns you actually need.
Custom API rules to know cold
- If it must be callable from Power Automate, make it an Action, not a Function.
- That means
Is Function = false. Enabled for Workflowmust be true only when you need workflow/flow invocation.- The custom API's main business logic is attached via the custom API plug-in type, not a normal plug-in step registration pattern.
- A custom API can exist without a plug-in when you are using it as a business event shell.
Exact anchors to keep searchable
WorkflowSdkStepEnabledPluginTypeIdIsPrivateExecutePrivilegeNamePreEntityImagesPostEntityImages
Learn-grounded reminders
- Microsoft Learn says
PreValidationis before the transaction,PreOperationis where you change values, andPostOperationis after the main operation. - Microsoft Learn says
MainOperationis for internal use only except custom APIs and custom virtual table data providers. - Microsoft Learn says a Function must return data, cannot be used with
Enabled for Workflow, and Power Automate needs an Action. - Microsoft Learn says
IsPrivatehides the API from$metadatabut does not prevent use by callers who already know it exists. - Microsoft Learn says
ExecutePrivilegeNamemust use an existing privilege.
5B. Custom connectors
Know cold
- Build the backend first.
- Lock authentication second.
- Test/export definition third.
- Create/import the custom connector fourth.
- Add policy/template or code-extension details last.
Canonical build order
text
Stable backend
-> auth
-> test in Postman or confirm OpenAPI
-> import/create connector
-> add policy templates or custom code
-> consume in app/flowAzure Function to connector sequence
text
HTTP-triggered Azure Function
-> add API key or auth
-> test/export definition
-> import into custom connector
-> consume from Power Apps / Power AutomateExact anchors to know
ScriptBaseScriptExecuteAsyncSet Host URLx-ms-capabilitiesx-ms-dynamic-values
Decision rules
- A custom connector is an API wrapper, not the API itself.
- If the endpoint varies by environment, think
Set Host URL, not hardcoding. - If the requirement is chunk transfer support, think
x-ms-capabilities. - If the requirement is populate parameter values dynamically from another operation, think
x-ms-dynamic-values.
Learn-grounded reminders
- Microsoft Learn says the custom-code class name must be
Script, it must implementScriptBase, and it must implementExecuteAsync. - Microsoft Learn documents
x-ms-capabilitiesfor operation-level connector capabilities such as chunk transfer. - Microsoft Learn documents
x-ms-dynamic-valuesfor dynamic parameter-value lists.
5C. Dataverse Web API and Organization Service
Know cold
| Need | Default answer |
|---|---|
| REST operations against Dataverse | Web API |
| SDK/.NET service operations | Organization service |
| Return created row | Prefer: return=representation |
| Set lookup to existing row | @odata.bind |
| Optimistic concurrency | UpdateRequest + IfRowVersionMatches |
| FetchXML through Org Service | FetchExpression |
| SDK client that uses MSAL | ServiceClient |
Status-code anchors
| Situation | Code |
|---|---|
| Unauthorized | 401 |
| Forbidden / insufficient rights | 403 |
| Invalid method/operation | 405 |
| Payload too large | 413 |
| Service-protection throttling | 429 |
Decision rules
- Web API and Organization service are not interchangeable mental models.
- If the question is about
@odata.bind, status codes, or HTTP headers, it is a Web API question. - If the question is about
UpdateRequest,FetchExpression, entity bags, orIOrganizationService, it is an Organization service question. - If Dataverse throttles you, honor
Retry-After; do not invent your own retry timing. - Do not assume every attribute exists in an entity bag. Missing attribute access is a classic Org Service trap.
Exact anchors to keep searchable
@odata.bindPrefer: return=representationIfRowVersionMatchesFetchExpressionRetry-AfterServiceClient
Learn-grounded reminders
- Microsoft Learn says
ServiceClientuses MSAL whileCrmServiceClientuses ADAL. - Microsoft Learn says
ServiceClientandCrmServiceClientcan manage service-protection limit errors, and later versions automatically pause for theRetry-Afterduration. - Microsoft Learn shows
FetchExpressionas the FetchXML holder used withIOrganizationService.RetrieveMultiple.
5D. Azure Functions and cloud flows
Know cold
| Requirement | Default answer |
|---|---|
| Long-running or heavy external compute | Azure Function |
| Scheduled/server-side execution | timer-triggered function |
| Durable wait in Durable Functions | createTimer() |
| Sensitive flow output in history | Secure Outputs |
| Reusable flow logic | child flow |
| Critical flow ownership | service principal |
Decision rules
- Do not choose cloud flow for transaction-safe Dataverse business logic.
- For Durable Functions timer questions, keep
createTimer()in memory. - Azure Functions timer expressions use NCRONTAB, not a generic five-field cron assumption.
- For cloud flows, privacy questions usually want
Secure Outputs, not a vague masking story.
Exact anchors to keep searchable
createTimer()- NCRONTAB
{second} {minute} {hour} {day} {month} {day-of-week} Secure Outputs
Learn-grounded reminders
- Microsoft Learn says Azure Functions timer triggers use NCRONTAB and support five- and six-field forms, with the six-field format including seconds first.
- Microsoft Learn documents durable timers using
CreateTimer/createTimerin Durable Functions.
6. Develop Integrations (10-15%)
Know cold
| Scenario | Default answer |
|---|---|
| Immediate synchronous callout from Dataverse event | Webhook |
| Durable async handoff / queueing | Azure Service Bus |
| Event streaming / analytics-style sink | Azure Event Hub |
| In-transaction Dataverse logic only | Plug-in |
| Efficient external delta sync | Change tracking |
| No-code identity/deduplication | Alternate key |
| Create or update against alternate key | PATCH / upsert pattern |
Dataverse eventing rules
IServiceEndpointNotificationServiceis the exact service-endpoint publishing anchor.- Webhooks, Service Bus, and Event Hub are all service endpoints, but they are not interchangeable.
- Business events are asynchronous notification patterns.
- To expose a business event, you must catalog it.
- Custom business events only fire after the event completes successfully.
Change tracking rules
| API family | Anchor |
|---|---|
| Organization service | RetrieveEntityChangesRequest + version token / DataVersion |
| Web API | @odata.deltaLink |
- One
RetrieveEntityChangesrequest tracks one table at a time. - The first request returns all records as baseline.
- Old tokens expire; current docs say the default window is seven days unless changed.
Upsert and alternate-key rules
- Alternate keys are for identity and dedupe, not generic "sync magic."
- When using alternate keys in the URL for upsert, do not also include conflicting alternate-key data in the request body.
Exact anchors to keep searchable
IServiceEndpointNotificationServiceWebhookKeyCatalogAssignmentRetrieveEntityChangesRequestDataVersion@odata.deltaLinkUpsertRequestPATCH
Learn-grounded reminders
- Microsoft Learn says Dataverse business events expose automation through Power Automate, Service Bus, Event Hub, webhooks, and plug-ins, but custom business events only notify after completion.
- Microsoft Learn says custom events are created with custom APIs and must be cataloged to expose them.
- Microsoft Learn says
RetrieveEntityChangesreturns a version number you send back on the next request. - Microsoft Learn says Web API change tracking uses a delta link for subsequent changes.
- Microsoft Learn says WebHook registration can use
WebhookKey, which sends a query string usingcodeas the key. - Microsoft Learn says when using alternate keys in an upsert URL, do not include those same alternate-key values in the body.
Official Learn Anchors
- PL-400 study guide
- Custom APIs
- Event framework
- Register a plug-in
- Business events
- Register a WebHook
- Change tracking
- Upsert in Dataverse
- Write code in a custom connector
- OpenAPI extensions for custom connectors
- Environment variables in solutions
- Environment variables in solution cloud flows
- Environment-variable import/cache troubleshooting
- OAuth auth with Dataverse
- Service protection API limits
- FetchXML via Organization service
- addPreSearch
- feature-usage
- uses-feature
- Device.getCurrentPosition