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 Cold | Searchable If Needed |
|---|---|
| Official domain weights | Exact current Microsoft Learn page headings |
| Functional vs non-functional | Full Well-Architected wording |
| User story format | Formal agile terminology |
| Fit/gap and product boundaries | Exact AppSource/ISV product names |
| Surface selection by audience | Licensing fine print |
| Dataverse relationship cardinality | Edge-case cascade behavior names |
| Reference table vs choice | Admin UI paths |
| Append vs Append To | Privilege table details |
| Power Pages list/form/template/settings split | Portal Management app navigation |
| Integration guarantee map | Connector/version labels |
| ALM/migration/go-live playbook | CLI 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 Signal | Decision Rule |
|---|---|
As a role, I want capability, so that benefit | Valid user story |
| Lacks role, action, or benefit | Not a full user story |
| Performance, availability, retention, recoverability, residency, compliance | Non-functional |
| Create/update/view/submit/approve/track | Functional |
| Requirement has measurable verb/noun | Success criteria must anchor on that exact measure |
| Group ideation | Workshop |
| Individual remote feedback | Survey |
| Observe real work | Job shadowing |
| Existing event log | Process mining |
| Record user actions | Task mining |
| High value + low effort | Quick win |
| High value + high effort | Big investment |
| Low value + high effort | Defer/challenge |
Product And Fit/Gap Rules
| Need | First Answer |
|---|---|
| Case/inquiry/service process | Dynamics 365 Customer Service |
| Field work / on-site technicians | Dynamics 365 Field Service |
| Sales pipeline | Dynamics 365 Sales |
| Project delivery plus sales | Dynamics 365 Project Operations |
| Marketing journeys, delivery evidence, web contact capture | Customer Insights - Journeys |
| Chatbot | Copilot Studio |
| Chatbot to live agent | Copilot Studio plus Omnichannel |
| SMS or niche external capability | ISV/AppSource/custom connector gap |
| Digital signature in SharePoint/D365 process | ISV/AppSource likely |
| Geospatial routing/maps | Bing Maps/Azure Maps/industry accelerator |
| Existing external app that fits | Evaluate AppSource/ISV before building |
Searchable Learn Anchors
PL-600 study guide skills measured September 23 2024Power Platform fit gap analysis Dynamics 365 AppSourcePower Platform Process Advisor process mining task miningCustomer Insights Journeys Dynamics 365 Marketing
Fast Drills
- Classify 10 requirements as functional or non-functional in under two minutes.
- Read any user-story option and identify missing role/capability/benefit.
- For every product-selection question, name the D365 app by core workflow before reading the options.
- 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 / Requirement | Best Surface |
|---|---|
| Internal process users on Dataverse | Model-driven app |
| Internal custom mobile UX / device features / non-Dataverse sources | Canvas app |
| Internal D365 users on first-party process | D365 app or Power Apps mobile |
| External customers/partners/contractors with Dataverse-backed self-service | Power Pages |
| Customer chat | Copilot Studio |
| Customer chat plus live agent | Omnichannel for Customer Service |
| Invited Microsoft 365 collaboration around documents/cases | Teams plus SharePoint/Dataverse as indicated |
Repeat anchor: external contractors plus Dataverse plus no Power Apps licensing -> Power Pages.
Dataverse Data Model
| Requirement | Rule |
|---|---|
| One parent, many children; each child has one parent | 1:N |
| Both sides can have many and no association metadata | N:N |
| Association needs fields like date/status/role | Custom/intersect table |
| Shared reference values with metadata/search/reporting/localization | Reference table + lookup |
| Small fixed values local to one table | Choice/Choices |
| External ID prevents duplicates | Alternate key + Upsert |
| Show external data without copy | Virtual table when provider supports it |
| Import/transformed load into Dataverse | Dataflow |
| Dataverse to lake/warehouse analytics | Synapse Link |
Dataverse Security
| Requirement | Rule |
|---|---|
| Regional hierarchy | Business units plus role depth |
| Cross-sibling access | Owner team or sharing where target data lives |
| Per-record temporary access | Access team template |
| High turnover access | Entra group team / Dataverse team |
| Sensitive columns | Field security profile |
| External portal rows | Power Pages table permissions and web roles |
| Environment membership gating | Entra security group |
| B2B guest access | Guest user plus team/security-role assignment |
| Attach child row to parent | Append on child, Append To on parent |
Power Pages
| Need | Component |
|---|---|
| Record collection | List/View |
| Single-row edit/display | Basic form |
| Guided multi-page process | Multistep form |
| Reusable portal code | Web template |
| Reusable file asset | Web file |
| Reusable small content | Content snippet |
| Config value such as API URL | Site setting |
| Authorization grouping | Web role |
| Row/table operation permission | Table permission |
| Page visibility | Webpage access control |
Integration And Automation
| Requirement | Component |
|---|---|
| Third-party REST API wrapper | Custom connector |
| Dataverse event to external system | Plug-in, webhook, or cloud flow based on sync/async need |
| Lightweight HTTP call | Webhook |
| Durable queue, slow receiver, transactional buffering | Service Bus queue |
| Cloud-to-on-prem with response/retry | Azure Relay |
| Telemetry streaming | Event Hubs |
| Scheduled transform/import | Dataflow |
| Dataverse analytics replication | Synapse Link |
| On-prem source connectivity | Data gateway |
| No API, legacy UI | Desktop flow/RPA |
| API/event automation | Automated cloud flow |
| Human-triggered action | Instant cloud flow |
| Guided human stages | Business process flow |
| Reusable flow subprocess | Child flow in a solution with instant/manual trigger |
Canvas / Mobile Vocabulary
| Need | Rule |
|---|---|
| Embed a static map | Image control with map URL |
| Open external app or URL | Launch |
| Move between screens | Navigate |
| Device coordinates | Location |
| Reusable tabular local data | Collection |
| Reused scalar/flag across screens | Global variable |
| Add rows | Collect |
| Clear and replace rows | ClearCollect |
| Delete matching rows | RemoveIf |
| Offline local storage | SaveData and LoadData |
Searchable Learn Anchors
Dataverse relationship behavior lookup Append Append ToPower Pages list basic form multistep form web template site settingsDataverse alternate key upsertDataverse virtual tables dataflowsPower Platform Service Bus Azure Relay webhook Dataverse
Fast Drills
- Given any external-user prompt, answer surface plus identity plus row security.
- Given a relationship prompt, answer cardinality and why N:N is or is not allowed.
- Given an integration prompt, name the delivery guarantee before naming the component.
- 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
| Need | Rule |
|---|---|
| Dev work | Unmanaged solution |
| Test/UAT/prod promotion | Managed solution |
| Environment-specific config | Environment variables and connection references |
| Per-component source tracking | Solution Packager / pac solution unpack |
| Mixed assets including data/custom code/HTML/files | Package Deployer |
| Automated export/build/deploy | Power Platform Build Tools / pipelines |
| Secure pipeline identity | Service principal/application user |
| First ALM foundation | Project/repo -> Build Tools -> export pipeline -> run |
Migration
| Requirement / Failure | Rule |
|---|---|
| Preserve reference-data GUIDs | Configuration Migration Tool or import with GUID mapping |
| Lookup failures | Load parent tables first |
| External IDs / duplicates | Alternate key + Upsert |
| One-shot import failed rows | Import job details and error export |
| Ongoing transformed import | Dataflow refresh details and row errors |
| Side effects during load | Disable/adjust workflows, plug-ins, duplicate detection, auditing as appropriate |
| Missing users in assignment picker | Check environment security group/provisioning before role tuning |
| Large historical migration | Phased migration, schema mapping, trial loads |
Limits And Performance
| Symptom | First Move |
|---|---|
| High-volume API calls delayed/failing | Check service protection limits and optimize/filter/batch |
| Daily request entitlement exceeded | Capacity/add-on/licensing path |
| Portal save slow | Synchronous plug-in or real-time logic |
| Canvas startup slow | OnStart, data volume, sequential calls, missing Concurrent |
| One screen slow | Screen OnVisible and over-fetching |
| Background process slow | Cloud-flow filters, conditions, trigger scope |
Validation And Diagnostics
| Need | Evidence |
|---|---|
| Flow action-level failure | Flow run history |
| Plug-in failure detail | Plug-in trace log |
| Wrong plug-in trigger/filter | SDK message processing steps |
| Data-change evidence | Auditing |
| Platform aggregate usage/performance | Power Platform admin center analytics |
| API usage/limits | Dataverse analytics and service protection metrics |
| Deployment issue | Solution history / pipeline output |
| Import failure | Import job details / failed-row export |
Go-Live Readiness
| Signal | Rule |
|---|---|
| UAT prep | Prepare users, data, access, test cases, and acceptance flow |
| Deployment plan issue | Fix deployment sequencing before go-live |
| Migration issue | Isolate failed rows/dependencies before rerun |
| Performance issue | Prove whether it is client, server, integration, or data-volume driven |
| Automation conflict | Identify competing real-time/workflow/plug-in/cloud-flow logic |
| Integration conflict | Check auth, retries, throttling, message routing, endpoint availability |
Searchable Learn Anchors
Power Platform managed solutions ALM pipelinesSolution Packager Package Deployer Power PlatformDataverse Configuration Migration Tool preserve GUIDDataverse service protection limits Power Platform RequestPower Automate run history troubleshootDataverse plug-in trace log SDK message processing steps
Fast Drills
- Given a go-live symptom, name the evidence source before the fix.
- Given a migration error, name dependency order, duplicate/external-ID rule, and failed-row source.
- Given an ALM tool, say what it does and what it does not do.
- Given a performance symptom, classify it as client load, server transaction, flow logic, API limit, or data-volume issue.