PL-600 study plan
PL-600 · Give each week a clear focus.
8 weeks · About 7 hours per week
Perform solution envisioning and requirement analysis
Map the envisioning workshop stages to the artifacts each one must produce in a Power Platform engagement
Extract business goals, pain points, success metrics, and constraints from a stakeholder interview you write yourself
Compare three candidate approaches (out-of-the-box, configure, custom build) and document cost, benefit, and risk for each
Draft the executive summary and scope statement of a solution blueprint
Your checkpoint
A 3-5 page envisioning document for a self-invented scenario containing stakeholders, goals, risks, and a first-pass options comparison table
Perform solution envisioning and requirement analysis
Classify requirements into functional, non-functional, data, and reporting categories and write testable acceptance criteria for each
Perform a fit-gap analysis against standard Power Platform capabilities and record a resolution for every gap
Specify data requirements including entity scope, volume, retention, and data sensitivity classification
Prioritize the requirement set with MoSCoW and assign items to delivery phases
Your checkpoint
A fit-gap matrix covering at least 15 requirements, each with category, priority, gap status, and proposed resolution
Perform solution envisioning and requirement analysis & Architect a solution
Design the data model: tables, relationships, keys, business rules, and migration source mapping
Select the app type for each requirement (model-driven, canvas, Power Pages) and justify the choice in writing
Draft the security model using business units, security roles, column security profiles, and manager hierarchy
Translate the design into licensing and capacity implications
Your checkpoint
Two blueprint sections - a written data model specification with relationship list, and an app selection rationale table with one justification line per requirement
Architect a solution
Choose an integration pattern for each gap (native connector, custom connector, Azure service, virtual table, Dataverse event) and state the tradeoffs
Define the environment strategy: number of environments, purpose of each, and promotion path
Identify single points of failure and performance risks in the proposed architecture
Assemble the full solution blueprint from the pieces produced in weeks 1-3
Your checkpoint
A consolidated solution blueprint document reviewed against a self-written 20-point completeness checklist scoring 18 or higher
Architect a solution
Design the ALM approach: publisher and solution segmentation, source control, and pipeline stages
Define data loss prevention policies and compliance controls covering connectors, data residency, auditing, and access
Evaluate the design against reliability, security, operational excellence, performance, and experience considerations, documenting at least two tradeoffs
Specify the backup, disaster recovery, and support model
Your checkpoint
An ALM and governance plan document that names every environment, the solution segmentation scheme, and the pipeline stage gates
Architect a solution & Implement the solution
Build a work breakdown structure that sequences configuration, integration, data migration, testing, and cutover
Create a Dataverse solution containing tables, a model-driven app, and at least one automation, then export it as managed
Configure a deployment pipeline and promote the solution from development to a second environment
Record and resolve the errors encountered during import
Your checkpoint
A working solution exported as managed and successfully imported into a test environment, plus a deployment log listing each error and its fix
Implement the solution
Write a test plan covering unit, system integration, user acceptance, and performance testing with entry and exit criteria
Validate the security model using at least two test users with different role assignments
Run a go-live readiness review covering data migration, training, support handover, and rollback
Deploy a corrective change through the pipeline and confirm it reaches the test environment
Your checkpoint
A test results summary with pass/fail per test case and a signed-off go-live checklist
Perform solution envisioning and requirement analysis & Architect a solution & Implement the solution
Complete two timed full-length practice assessments under exam conditions
Tag every missed item by domain and root cause (knowledge gap, misread, or guess)
Re-study the two weakest sub-areas until you can explain them without notes
Condense architecture decision patterns into a one-page reference sheet you can recite
Your checkpoint
A timed assessment score of 80 percent or higher plus a written remediation list with zero unresolved items
Milestones
Week 2: Produce a complete fit-gap matrix from a fresh scenario in under 45 minutes without notes
Week 4: Solution blueprint scores 18 or higher on the 20-point completeness checklist and covers all five architecture considerations
Week 6: Managed solution deployed end-to-end through a pipeline to a second environment with zero blocking errors
Week 8: Two timed practice assessments completed with an average score of 80 percent or higher