PL-200 study plan

Build a Dataverse environment from scratch and create three custom tables with primary columns, custom columns of at least five different data types, and a lookup relationship

Configure one each of a one-to-many, many-to-one, and many-to-many relationship, then document which behavior (cascade vs. restrict) you selected and why

Create a business rule on a table that sets and clears a column based on another column's value, and verify it fires in a model-driven form

Define two security roles that differ at the table and column level, and assign a test user to confirm record visibility changes

Create calculated and rollup columns on a parent table that aggregate child records, and confirm the recalculated values against manually counted data

Enable and configure auditing on two tables and one column, then retrieve an audit history record showing a field change

Import at least 20 records from a CSV using the data import wizard, mapping columns explicitly and resolving one intentional import error

Publish all customizations and verify the solution installs cleanly into a second environment with no missing dependency warnings

Build a canvas app with three screens, a gallery bound to a Dataverse table, a detail form, and navigation between screens

Write formulas using Search, Filter, and delegation-friendly patterns, and identify at least two formulas in your app that would produce delegation warnings

Configure a form control with validation, submit behavior, and success/error feedback tied to a flow or patch call

Add a reusable component with an input property and use it on two different screens

Construct a model-driven app with a custom sitemap, two forms, three views, and a chart

Customize a main form with a business process flow control, a timeline, and a subgrid filtered to related records

Configure role-based form and view behavior so that two different security roles see different fields and default views

Test the app end to end as a non-admin user and log every permission error encountered and fixed

Build an automated cloud flow that triggers on a Dataverse row creation, applies a condition, sends a notification, and updates the source row

Implement a scheduled flow that uses at least three expressions (formatDateTime, addDays, coalesce) and writes results back to Dataverse

Add error handling to one flow using a Scope block with configure-run-after settings and a failure notification path

Create a business process flow with three stages, one conditional branch, and a stage-level requirement enforced by a column

Build an approval flow that routes to two approvers sequentially and branches on the approval outcome

Convert at least one flow and one business process flow into solution-aware components and add them to your existing solution

Create a second environment and configure data loss prevention policies that block a connector you have been using, then observe and record the resulting failure

Document the security model of the new environment: business units, teams, and which role grants app access

Deploy your managed solution through a pipeline or manual export/import from development to test environment and record every dependency issue resolved

Configure environment settings including auditing, email, and delegated admin options, and verify each setting's effect

Revisit Dataverse security by implementing a hierarchy security scenario (manager hierarchy) and confirming record access changes

Take a timed 30-question mixed practice set and tag every missed question to its exam domain

Rebuild from memory the three components you struggled with most, without consulting notes, then compare against your earlier work

Complete two full-length timed practice exams and score each attempt

Review every missed item from both exams and close gaps by re-reading only the affected feature documentation

Recite from memory the decision rules for choosing canvas vs. model-driven, cloud flow vs. business process flow vs. classic workflow, and business rule vs. validation