Overview
Domain 2 carries 20–25% of PL-900 and has two functional groups. The first, Describe Microsoft Dataverse, covers how Dataverse differs from a traditional database, tables, columns and relationships, forms and views, business logic options including Power Fx, and using AI to create and edit tables, columns and relationships.
The second, Describe Microsoft Power Platform administration and governance, covers environments, the security model, support for data privacy and accessibility guidelines, monitoring and analytics, and application lifecycle management with Power Platform pipelines. The July 2026 update raised this domain's share and rated both groups as moderate changes, so material written before that date misses several current bullets.
How it's tested
Expect scenario items that name a data requirement or an administrative goal and ask which Dataverse component or governance feature applies. Some questions present statements about environments, security roles or relationships for you to judge as true or false. Precise terminology matters, because distractors often swap similar terms such as form and view.
-
Choose the Dataverse component
A requirement such as listing records, editing one record or linking two entities maps to a view, form or relationship.
-
Separate dev from production
A governance scenario asks for isolation between development, test and production, pointing to environments and pipelines.
-
Least privilege access
Users see too much or too little data, and the fix involves security roles, business units or environment security groups.
A company builds apps in one environment where makers also test changes, and a faulty edit recently broke the live app. Separate development, test and production environments isolate work, and Power Platform pipelines move a solution between them in a controlled way. Turning off Dataverse auditing or removing makers' licenses would not stop the problem, because the cause is the absence of staged deployment.
Functional groups 2
Official functional groups from the Microsoft outline, in outline order.
2.1 Describe Microsoft DataverseDataverse versus traditional databases, tables, columns, relationships, forms, views, business logic, Power Fx and AI-assisted table design.
- What it means
- This group covers how Dataverse stores and shapes business data. You need to describe how it differs from a traditional database, explain tables, columns and relationships, describe forms and views, outline business logic options including Power Fx, and describe using AI to create and edit tables, columns and relationships.
- What to understand
- Unlike a traditional database you design and administer yourself, Dataverse is a managed service with built-in security, auditing, rich data types such as file, image and currency, and a standard set of tables such as Account and Contact. Tables hold rows; columns define data types; relationships are one-to-many, many-to-one or many-to-many. Forms display and edit one row, while views list filtered, sorted rows. Business logic options include business rules, Power Fx formula columns, calculated and rollup columns, low-code plug-ins and flows. Copilot can propose tables and relationships from a description or file, which makers then review.
- How it shows up
- Expect a requirement such as listing open cases for each owner or validating a field, and pick view, form, relationship or business rule accordingly.
- Common confusion
- Mixing forms and views: a form is for one record, a view is a list of many records.
2.2 Describe Microsoft Power Platform administration and governanceEnvironments, the security model, privacy and accessibility support, monitoring and analytics, and ALM with pipelines.
- What it means
- This group covers how administrators control Power Platform. It includes describing environments, the security model, how the platform supports data privacy and accessibility guidelines, monitoring and analytics capabilities, and application lifecycle management by using Power Platform pipelines.
- What to understand
- An environment is a container for apps, flows, agents and data, with at most one Dataverse database, a region and a type such as production, sandbox, developer or default. The security model layers Microsoft Entra ID authentication, environment access through security groups, Dataverse security roles, business units and teams, and column-level security. Data policies classify connectors into business, non-business and blocked groups to prevent data leaks. Accessibility checker helps makers meet guidelines, and Microsoft compliance commitments cover privacy. The Power Platform admin center offers analytics and monitoring. Pipelines deploy solutions from development to test and production environments.
- How it shows up
- Expect questions on which feature isolates work, limits data access, stops a risky connector combination, or promotes a solution between environments.
- Common confusion
- Thinking a data policy controls who can see records; it governs connector use, while security roles control record access.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Environment
A container that holds apps, flows, agents, connections and optionally one Dataverse database.
- Remember
- Each tenant has a default environment; others are created for isolation by purpose or region.
- Tested as
- The answer to separating development, testing and production or different departments.
- Trap
- Assuming one environment can hold several Dataverse databases.
-
Table
The Dataverse structure that stores rows of one kind of business data.
- Remember
- Standard tables come built in; custom tables are created for your own data.
- Tested as
- Questions describe a new data need and ask what to create.
- Trap
- Calling a table an entity list or confusing it with a view.
-
Column
A field in a table with a defined data type.
- Remember
- Types include text, number, choice, lookup, file, image and formula.
- Tested as
- Picked when a scenario needs to store one more piece of information per record.
- Trap
- Choosing a new table when only an extra column is needed.
-
Relationship
A link between two tables, such as one-to-many or many-to-many.
- Remember
- A lookup column on the many side implements a one-to-many relationship.
- Tested as
- Appears when records of two kinds must be connected, such as accounts and contacts.
- Trap
- Treating a many-to-many need as a single lookup column.
-
Form
A Dataverse layout for viewing and editing a single row.
- Remember
- Types include main, quick create, quick view and card forms.
- Tested as
- Chosen when users must enter or update details for one record.
- Trap
- Using a form to show a filtered list of records.
-
View
A saved query that lists rows with chosen columns, filters and sort order.
- Remember
- Public views are shared; personal views are created by users.
- Tested as
- Chosen when users need to see many records matching criteria.
- Trap
- Confusing a view with a dashboard or a report.
-
Business rule
No-code logic on a table that sets values, shows errors or changes field visibility.
- Remember
- It runs in model-driven forms and, at table scope, on the server.
- Tested as
- The answer for simple validation without writing code.
- Trap
- Expecting a business rule to call external services; that needs a flow or plug-in.
-
Power Fx
The low-code formula language used across Power Platform.
- Remember
- In Dataverse it powers formula columns and low-code plug-ins.
- Tested as
- Questions on business logic options may name Power Fx as the formula-based choice.
- Trap
- Believing Power Fx is only for canvas apps.
-
Security role
A set of privileges on tables and access levels in Dataverse.
- Remember
- Roles are cumulative, and access levels range from user to organization.
- Tested as
- The fix when users see or edit records they should not.
- Trap
- Assuming a security role grants access to an environment without a Dataverse database.
-
Data policy (DLP)
An admin rule that groups connectors as business, non-business or blocked.
- Remember
- Connectors from different groups cannot be used together in one app or flow.
- Tested as
- The answer to stopping company data from flowing to personal services.
- Trap
- Treating a data policy as record-level security.
-
Power Platform pipelines
Built-in ALM that deploys solutions between environments.
- Remember
- Makers run deployments from development to test or production with admin-defined stages.
- Tested as
- The answer for controlled, repeatable promotion of solutions.
- Trap
- Thinking exporting and importing unmanaged solutions by hand is the governed approach.
-
Power Platform admin center
The portal for managing environments, policies, capacity and analytics.
- Remember
- Admins create environments, apply data policies and review usage there.
- Tested as
- Monitoring and governance questions point here.
- Trap
- Confusing it with the maker portal used to build apps.
-
Managed Environments
A set of premium governance features enabled on an environment.
- Remember
- Features include sharing limits, weekly digests and usage insights; pipelines target managed environments.
- Tested as
- May appear in governance scenarios that need more control at scale.
- Trap
- Assuming it is a separate environment type rather than a setting.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Forms, views and dashboards
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Form | Layout for one record. | Edits or displays a single row. | Picking it to list many rows. |
| View | Filtered, sorted list of rows. | Shows many records with chosen columns. | Assuming views allow editing all fields like a form. |
| Dashboard | Collection of charts, lists and views on one page. | Gives an overview across several sources. | Choosing it when users must edit a single record. |
Dataverse business logic options
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Business rule | No-code conditions and actions on a table. | Simple validation and field behavior. | Expecting it to call external APIs. |
| Formula column (Power Fx) | Column whose value is computed by a Power Fx formula. | Calculated at read time from other columns. | Thinking it stores a value users can type over. |
| Power Automate flow | Automation triggered by Dataverse events. | Can reach other services through connectors. | Using a flow for simple field validation that a business rule handles. |
| Plug-in | Code or low-code logic running in the Dataverse event pipeline. | Runs synchronously or asynchronously on the server. | Assuming plug-ins require a canvas app to run. |
Governance controls
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Security role | Privileges on Dataverse tables. | Controls what records users can read or change. | Using it to block connectors. |
| Data policy | Connector grouping rules. | Controls which connectors can be combined. | Using it to hide records from users. |
| Environment security group | Microsoft Entra group tied to an environment. | Controls who can access the environment at all. | Assuming it assigns table privileges. |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Default environment for everything
- What candidates pick
- Build production apps in the default environment
- Why it looks right
- Every user already has access there, so it seems convenient.
- Why it's wrong
- The default environment is shared by all licensed users; production solutions belong in dedicated environments with controlled access.
Clue to watch for Words like isolate, production or separate team.
-
DLP for record access
- What candidates pick
- A data policy to stop sales staff seeing finance records
- Why it looks right
- Both concern protecting data, so the terms blur.
- Why it's wrong
- Data policies control connector combinations; record visibility comes from security roles, business units and teams.
Clue to watch for The scenario is about which rows a user can see.
-
New table instead of a column
- What candidates pick
- Create a table to store a customer's preferred contact time
- Why it looks right
- Creating tables feels like the main Dataverse task.
- Why it's wrong
- One extra attribute of an existing record is a column on that table, not a new table.
Clue to watch for A single value per existing record.
-
Lookup for many-to-many
- What candidates pick
- Add one lookup column linking students to courses
- Why it looks right
- Lookups are the most familiar relationship tool.
- Why it's wrong
- A student takes many courses and a course has many students, so a many-to-many relationship is required.
Clue to watch for Both sides can have many related records.
-
Manual export as ALM
- What candidates pick
- Export and import unmanaged solutions by hand
- Why it looks right
- Many makers learned ALM that way.
- Why it's wrong
- Pipelines provide a governed, repeatable deployment with stages and approvals, which is what the outline names.
Clue to watch for Repeatable, controlled or approved deployment.
-
Traditional database equals Dataverse
- What candidates pick
- Dataverse requires a DBA to tune indexes and backups
- Why it looks right
- Relational concepts are shared with SQL databases.
- Why it's wrong
- Dataverse is a managed service where Microsoft handles infrastructure, backups and scaling, with built-in security and auditing.
Clue to watch for Comparisons between Dataverse and a self-managed database.
Answer framework
Use these steps to decide which Dataverse or governance feature a Domain 2 scenario is asking for.
- Decide whether the scenario is about data structure, record access, connector risk, environment isolation or deployment, because each points to a different feature family.
- For data structure, choose between a new table, a new column or a relationship, and check whether the relationship is one-to-many or many-to-many.
- For user interface inside Dataverse, pick a form for one record and a view for a list, and consider a business rule for simple validation.
- For access problems, check environment security groups first, then security roles, business units and column security for finer control.
- For risk and lifecycle questions, use data policies for connector control, admin center analytics for monitoring, and pipelines for moving solutions between environments.
Practice question
Want more like this? The PL-900 practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with Dataverse because it is concrete. In a free developer environment, create a custom table, add columns of several types, build a one-to-many and a many-to-many relationship, then customize a main form and a public view. Try asking Copilot to draft a table from a description and note what you would correct. Add a business rule and a formula column so you can compare logic options side by side.
Move on to governance in the Power Platform admin center. Look at the environment list, environment types and settings, then read how security groups, security roles and business units combine. Open the data policy editor and classify a few connectors to see how business and non-business groups behave. Review the analytics pages for apps and flows, and read the pipelines documentation, ideally running a simple deployment between two environments.
Close each session by explaining one feature aloud as if to a manager. Allow a week of short sessions, since this domain is among the heaviest.
FAQ
How much of PL-900 does Manage the Microsoft Power Platform environment cover?
Manage the Microsoft Power Platform environment is weighted at 20–25% of PL-900, an increase in the July 24, 2026 revision. Expect roughly ten questions.
Do I need to write Power Fx for this domain?
No. You need to describe Power Fx as a business logic option in Dataverse, for example in formula columns, rather than write formulas from memory.
What changed in this domain in 2026?
Both functional groups were rated moderate changes. New emphasis includes AI-assisted table design, data privacy and accessibility support, monitoring and analytics, and ALM with Power Platform pipelines.
Is Dataverse for Teams tested?
The current bullets focus on Dataverse in general. Know that Teams has a lighter Dataverse option, but study standard Dataverse tables, relationships and security first.
How deep should I go on security roles?
Understand that roles hold table privileges with access levels, that roles add together, and how business units and teams scope access. Configuring every privilege is beyond a fundamentals exam.
Are pipelines the same as Azure DevOps pipelines?
No. Power Platform pipelines are built into the platform and aimed at makers and admins, though professional teams may still use Azure DevOps or GitHub for advanced ALM.
What is a developer environment?
It is a free environment for an individual to build and test, with a Dataverse database and limited capacity, useful for hands-on practice for this exam.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 2 knowledge
Test whether you can choose the right Dataverse component, security control or environment strategy for a scenario before you move on.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PL-900 AI tutor Get any concept explained your way