Skip to content

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, ExecuteAsync
  • x-ms-capabilities, x-ms-dynamic-values
  • feature-usage, uses-feature, Device.getCurrentPosition
  • @odata.bind, Prefer: return=representation
  • ExecutePrivilegeName, IsPrivate, WorkflowSdkStepEnabled
  • Retry-After
  • WebhookKey

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 shapeDefault answer
Simplest native rule on forms/columnsBusiness rule
Immediate server-side validation/error in classic PL-400 framingReal-time workflow
In-transaction Dataverse logicPlug-in
Client/form/command behaviorJavaScript + Client API
Async orchestration or external-process automationCloud flow
Long-running or heavy external computeAzure Function
External API surfaced into app/flowCustom connector
External data stays outside DataverseVirtual table
High-scale Dataverse storage/workloadElastic 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 tables
  • virtual tables
  • data loss prevention (DLP) policies
  • Access Dynamics 365 as organization users

2. Build Power Platform Solutions (10-15%) ​

Know cold ​

SituationCorrect read
Build and edit componentsUnmanaged solution
Ship downstreamManaged solution
Managed behavior looks wrong in targetCheck active unmanaged layer
Dependency looks missingVerify it was published and included
Grant table/record accessSecurity role
Restrict one fieldColumn-level security
Hide/show different UI to different audiencesRole-based form

Decision rules ​

  • Unmanaged is for authoring. Managed is 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 Value wins if present.
    • Default Value is 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 Value
  • Default Value
  • environmentvariablevalue
  • Power Platform Pipelines
  • Build 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 Value is 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 ​

NeedDefault answer
Inspect app runtime behaviorMonitor
Add your own debug/telemetry messagesTrace
Simplify complex formula readabilityWith
Let a reusable component read app-level collections or varsAccess app scope
Investigate model-driven client behaviorMonitor + 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 string
  • Monitor
  • Trace
  • With
  • Access app scope

Learn-grounded reminders ​


4. Extend The User Experience (10-15%) ​

Know cold ​

NeedAnswer
Filter a lookup before results showaddPreSearch
Show blocking wait stateXrm.Utility.showProgressIndicator()
Show control-specific messageaddNotification
Show form-level messagesetFormNotification
Show command only when rows are selectedCountRows(Self.Selected.AllItems) > 0
Share JS used by a commandadd 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-usage wraps uses-feature.
  • uses-feature requires both name and required.

Decision rules ​

  • addPreSearch is 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 ​

  • addPreSearch
  • feature-usage
  • uses-feature
  • Device.getCurrentPosition
  • showProgressIndicator

Learn-grounded reminders ​

  • Microsoft Learn says addPreSearch applies changes to lookups just as the user is about to view results.
  • Microsoft Learn says feature-usage wraps uses-feature.
  • Microsoft Learn says uses-feature requires name and required.
  • 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 stageRule
PreValidationreject/cancel early
PreOperationmutate incoming values
MainOperationinternal only except custom API / custom virtual table providers
PostOperationreact after core operation; async handoff starts here
Plug-in detailRule
Change Target before writePreOperation
Cancel safelyprefer PreValidation
Pass data between stepsSharedVariables
Compare old/new valuesuse images before extra retrieves
Read/write Dataverse rows in codeIOrganizationService
Trace/debugITracingService
Runtime contextIPluginExecutionContext

Entity-image rules ​

  • No Pre Image on Create.
  • No Post Image on Delete.
  • Post Image exists only for steps in PostOperation.
  • 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 Workflow must 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 ​

  • WorkflowSdkStepEnabled
  • PluginTypeId
  • IsPrivate
  • ExecutePrivilegeName
  • PreEntityImages
  • PostEntityImages

Learn-grounded reminders ​

  • Microsoft Learn says PreValidation is before the transaction, PreOperation is where you change values, and PostOperation is after the main operation.
  • Microsoft Learn says MainOperation is 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 IsPrivate hides the API from $metadata but does not prevent use by callers who already know it exists.
  • Microsoft Learn says ExecutePrivilegeName must 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/flow

Azure 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 Automate

Exact anchors to know ​

  • ScriptBase
  • Script
  • ExecuteAsync
  • Set Host URL
  • x-ms-capabilities
  • x-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 implement ScriptBase, and it must implement ExecuteAsync.
  • Microsoft Learn documents x-ms-capabilities for operation-level connector capabilities such as chunk transfer.
  • Microsoft Learn documents x-ms-dynamic-values for dynamic parameter-value lists.

5C. Dataverse Web API and Organization Service ​

Know cold ​

NeedDefault answer
REST operations against DataverseWeb API
SDK/.NET service operationsOrganization service
Return created rowPrefer: return=representation
Set lookup to existing row@odata.bind
Optimistic concurrencyUpdateRequest + IfRowVersionMatches
FetchXML through Org ServiceFetchExpression
SDK client that uses MSALServiceClient

Status-code anchors ​

SituationCode
Unauthorized401
Forbidden / insufficient rights403
Invalid method/operation405
Payload too large413
Service-protection throttling429

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, or IOrganizationService, 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.bind
  • Prefer: return=representation
  • IfRowVersionMatches
  • FetchExpression
  • Retry-After
  • ServiceClient

Learn-grounded reminders ​

  • Microsoft Learn says ServiceClient uses MSAL while CrmServiceClient uses ADAL.
  • Microsoft Learn says ServiceClient and CrmServiceClient can manage service-protection limit errors, and later versions automatically pause for the Retry-After duration.
  • Microsoft Learn shows FetchExpression as the FetchXML holder used with IOrganizationService.RetrieveMultiple.

5D. Azure Functions and cloud flows ​

Know cold ​

RequirementDefault answer
Long-running or heavy external computeAzure Function
Scheduled/server-side executiontimer-triggered function
Durable wait in Durable FunctionscreateTimer()
Sensitive flow output in historySecure Outputs
Reusable flow logicchild flow
Critical flow ownershipservice 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 / createTimer in Durable Functions.

6. Develop Integrations (10-15%) ​

Know cold ​

ScenarioDefault answer
Immediate synchronous callout from Dataverse eventWebhook
Durable async handoff / queueingAzure Service Bus
Event streaming / analytics-style sinkAzure Event Hub
In-transaction Dataverse logic onlyPlug-in
Efficient external delta syncChange tracking
No-code identity/deduplicationAlternate key
Create or update against alternate keyPATCH / upsert pattern

Dataverse eventing rules ​

  • IServiceEndpointNotificationService is 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 familyAnchor
Organization serviceRetrieveEntityChangesRequest + version token / DataVersion
Web API@odata.deltaLink
  • One RetrieveEntityChanges request 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 ​

  • IServiceEndpointNotificationService
  • WebhookKey
  • CatalogAssignment
  • RetrieveEntityChangesRequest
  • DataVersion
  • @odata.deltaLink
  • UpsertRequest
  • PATCH

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 RetrieveEntityChanges returns 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 using code as 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 ​


Personal study notes written from official documentation. Not affiliated with Microsoft or GitHub. Contains no exam questions.