Skip to content

PL-600 study guide ​

PL-600 is less about "can this tool do it?" and more about "is this the best architecture recommendation?" Drill each table until every scenario signal points to one component without debate.


Know cold vs. look up later ​

Know ColdSearchable If Needed
Official domain weightsExact current Microsoft Learn page headings
Functional vs non-functionalFull Well-Architected wording
User story formatFormal agile terminology
Fit/gap and product boundariesExact AppSource/ISV product names
Surface selection by audienceLicensing fine print
Dataverse relationship cardinalityEdge-case cascade behavior names
Reference table vs choiceAdmin UI paths
Append vs Append ToPrivilege table details
Power Pages list/form/template/settings splitPortal Management app navigation
Integration guarantee mapConnector/version labels
ALM/migration/go-live playbookCLI syntax and pipeline task names

Memorize the reason the correct option is architecturally safer, not specific answers.


Perform solution envisioning and requirement analysis (45–50%) ​

Official weight: 45-50%.

Know-Cold Table ​

Scenario SignalDecision Rule
As a role, I want capability, so that benefitValid user story
Lacks role, action, or benefitNot a full user story
Performance, availability, retention, recoverability, residency, complianceNon-functional
Create/update/view/submit/approve/trackFunctional
Requirement has measurable verb/nounSuccess criteria must anchor on that exact measure
Group ideationWorkshop
Individual remote feedbackSurvey
Observe real workJob shadowing
Existing event logProcess mining
Record user actionsTask mining
High value + low effortQuick win
High value + high effortBig investment
Low value + high effortDefer/challenge

Product And Fit/Gap Rules ​

NeedFirst Answer
Case/inquiry/service processDynamics 365 Customer Service
Field work / on-site techniciansDynamics 365 Field Service
Sales pipelineDynamics 365 Sales
Project delivery plus salesDynamics 365 Project Operations
Marketing journeys, delivery evidence, web contact captureCustomer Insights - Journeys
ChatbotCopilot Studio
Chatbot to live agentCopilot Studio plus Omnichannel
SMS or niche external capabilityISV/AppSource/custom connector gap
Digital signature in SharePoint/D365 processISV/AppSource likely
Geospatial routing/mapsBing Maps/Azure Maps/industry accelerator
Existing external app that fitsEvaluate AppSource/ISV before building

Searchable Learn Anchors ​

  • PL-600 study guide skills measured September 23 2024
  • Power Platform fit gap analysis Dynamics 365 AppSource
  • Power Platform Process Advisor process mining task mining
  • Customer Insights Journeys Dynamics 365 Marketing

Fast Drills ​

  1. Classify 10 requirements as functional or non-functional in under two minutes.
  2. Read any user-story option and identify missing role/capability/benefit.
  3. For every product-selection question, name the D365 app by core workflow before reading the options.
  4. For every fit/gap question, ask: native, AppSource/ISV, low-code extension, or custom code?

Architect a solution (35–40%) ​

Official weight: 35-40%.

Surface Selection ​

Audience / RequirementBest Surface
Internal process users on DataverseModel-driven app
Internal custom mobile UX / device features / non-Dataverse sourcesCanvas app
Internal D365 users on first-party processD365 app or Power Apps mobile
External customers/partners/contractors with Dataverse-backed self-servicePower Pages
Customer chatCopilot Studio
Customer chat plus live agentOmnichannel for Customer Service
Invited Microsoft 365 collaboration around documents/casesTeams plus SharePoint/Dataverse as indicated

Repeat anchor: external contractors plus Dataverse plus no Power Apps licensing -> Power Pages.

Dataverse Data Model ​

RequirementRule
One parent, many children; each child has one parent1:N
Both sides can have many and no association metadataN:N
Association needs fields like date/status/roleCustom/intersect table
Shared reference values with metadata/search/reporting/localizationReference table + lookup
Small fixed values local to one tableChoice/Choices
External ID prevents duplicatesAlternate key + Upsert
Show external data without copyVirtual table when provider supports it
Import/transformed load into DataverseDataflow
Dataverse to lake/warehouse analyticsSynapse Link

Dataverse Security ​

RequirementRule
Regional hierarchyBusiness units plus role depth
Cross-sibling accessOwner team or sharing where target data lives
Per-record temporary accessAccess team template
High turnover accessEntra group team / Dataverse team
Sensitive columnsField security profile
External portal rowsPower Pages table permissions and web roles
Environment membership gatingEntra security group
B2B guest accessGuest user plus team/security-role assignment
Attach child row to parentAppend on child, Append To on parent

Power Pages ​

NeedComponent
Record collectionList/View
Single-row edit/displayBasic form
Guided multi-page processMultistep form
Reusable portal codeWeb template
Reusable file assetWeb file
Reusable small contentContent snippet
Config value such as API URLSite setting
Authorization groupingWeb role
Row/table operation permissionTable permission
Page visibilityWebpage access control

Integration And Automation ​

RequirementComponent
Third-party REST API wrapperCustom connector
Dataverse event to external systemPlug-in, webhook, or cloud flow based on sync/async need
Lightweight HTTP callWebhook
Durable queue, slow receiver, transactional bufferingService Bus queue
Cloud-to-on-prem with response/retryAzure Relay
Telemetry streamingEvent Hubs
Scheduled transform/importDataflow
Dataverse analytics replicationSynapse Link
On-prem source connectivityData gateway
No API, legacy UIDesktop flow/RPA
API/event automationAutomated cloud flow
Human-triggered actionInstant cloud flow
Guided human stagesBusiness process flow
Reusable flow subprocessChild flow in a solution with instant/manual trigger

Canvas / Mobile Vocabulary ​

NeedRule
Embed a static mapImage control with map URL
Open external app or URLLaunch
Move between screensNavigate
Device coordinatesLocation
Reusable tabular local dataCollection
Reused scalar/flag across screensGlobal variable
Add rowsCollect
Clear and replace rowsClearCollect
Delete matching rowsRemoveIf
Offline local storageSaveData and LoadData

Searchable Learn Anchors ​

  • Dataverse relationship behavior lookup Append Append To
  • Power Pages list basic form multistep form web template site settings
  • Dataverse alternate key upsert
  • Dataverse virtual tables dataflows
  • Power Platform Service Bus Azure Relay webhook Dataverse

Fast Drills ​

  1. Given any external-user prompt, answer surface plus identity plus row security.
  2. Given a relationship prompt, answer cardinality and why N:N is or is not allowed.
  3. Given an integration prompt, name the delivery guarantee before naming the component.
  4. Given a Power Pages prompt, classify it as list, form, multistep form, template, file, snippet, or setting.

Implement the solution (15–20%) ​

Official weight: 15-20%.

ALM And Deployment ​

NeedRule
Dev workUnmanaged solution
Test/UAT/prod promotionManaged solution
Environment-specific configEnvironment variables and connection references
Per-component source trackingSolution Packager / pac solution unpack
Mixed assets including data/custom code/HTML/filesPackage Deployer
Automated export/build/deployPower Platform Build Tools / pipelines
Secure pipeline identityService principal/application user
First ALM foundationProject/repo -> Build Tools -> export pipeline -> run

Migration ​

Requirement / FailureRule
Preserve reference-data GUIDsConfiguration Migration Tool or import with GUID mapping
Lookup failuresLoad parent tables first
External IDs / duplicatesAlternate key + Upsert
One-shot import failed rowsImport job details and error export
Ongoing transformed importDataflow refresh details and row errors
Side effects during loadDisable/adjust workflows, plug-ins, duplicate detection, auditing as appropriate
Missing users in assignment pickerCheck environment security group/provisioning before role tuning
Large historical migrationPhased migration, schema mapping, trial loads

Limits And Performance ​

SymptomFirst Move
High-volume API calls delayed/failingCheck service protection limits and optimize/filter/batch
Daily request entitlement exceededCapacity/add-on/licensing path
Portal save slowSynchronous plug-in or real-time logic
Canvas startup slowOnStart, data volume, sequential calls, missing Concurrent
One screen slowScreen OnVisible and over-fetching
Background process slowCloud-flow filters, conditions, trigger scope

Validation And Diagnostics ​

NeedEvidence
Flow action-level failureFlow run history
Plug-in failure detailPlug-in trace log
Wrong plug-in trigger/filterSDK message processing steps
Data-change evidenceAuditing
Platform aggregate usage/performancePower Platform admin center analytics
API usage/limitsDataverse analytics and service protection metrics
Deployment issueSolution history / pipeline output
Import failureImport job details / failed-row export

Go-Live Readiness ​

SignalRule
UAT prepPrepare users, data, access, test cases, and acceptance flow
Deployment plan issueFix deployment sequencing before go-live
Migration issueIsolate failed rows/dependencies before rerun
Performance issueProve whether it is client, server, integration, or data-volume driven
Automation conflictIdentify competing real-time/workflow/plug-in/cloud-flow logic
Integration conflictCheck auth, retries, throttling, message routing, endpoint availability

Searchable Learn Anchors ​

  • Power Platform managed solutions ALM pipelines
  • Solution Packager Package Deployer Power Platform
  • Dataverse Configuration Migration Tool preserve GUID
  • Dataverse service protection limits Power Platform Request
  • Power Automate run history troubleshoot
  • Dataverse plug-in trace log SDK message processing steps

Fast Drills ​

  1. Given a go-live symptom, name the evidence source before the fix.
  2. Given a migration error, name dependency order, duplicate/external-ID rule, and failed-row source.
  3. Given an ALM tool, say what it does and what it does not do.
  4. Given a performance symptom, classify it as client load, server transaction, flow logic, API limit, or data-volume issue.

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