• Home
• Microsoft Exams
• PL-200 - Microsoft Power Platform Functional Consultant

PL-200 Microsoft Practice Test Questions and Exam Dumps

Question No 1:

Your organization follows strict governance policies that do not allow custom code to be used in its business solutions. As part of your responsibility to improve data visibility in Power Apps, you are tasked with creating a view of data that should be accessible and visible to all users across the organization.

Given the no-code policy and the requirement for broad accessibility, where should you create this view to ensure that it adheres to organizational policies and is available to all users?

A. List view of the entity
B. Microsoft Visual Studio
C. Templates area
D. Maker portal

Correct Answer: A. List view of the entity

Explanation:

In Microsoft Power Platform and Dataverse, a "view" defines how data from an entity (also called a table) is presented to users, such as in a grid or list format. When you want to make a view visible to all users, you must create a system view (also known as a public or shared view), which is typically managed within the entity’s view settings in the Power Apps Maker portal.

Option A – List view of the entity is correct because:

• Views created here can be shared across the organization.

• No custom code is required.

• These views are accessible to any user who has access to the entity/table.

• It aligns with your organization's policy of avoiding custom development.

Option B – Microsoft Visual Studio is incorrect because this implies custom code development, which violates the organization's policy.

Option C – Templates area typically refers to Power Automate templates or document templates, not entity views, so it’s irrelevant in this context.

Option D – Maker portal is close, but not specific enough. While the Maker portal is where you access and manage entity views, the actual place to create the view is within the list views of the specific entity. Therefore, A is the most precise and correct answer.

Question No 2: 

Your organization uses a Power Apps Portal to offer online training courses. Students can register, create profiles, and purchase courses directly through the portal. You plan to add a collection of free courses that should be automatically accessible to all students after they sign in, without requiring manual assignment or individual permissions.

You need to configure the default permissions so that all authenticated users (students) gain access to free course data immediately upon login.

What is the best way to assign these permissions in alignment with the portal’s security model?

A. Create a Students web role and set the Authenticated Users Role option to true. Assign the web role to each registered user.
B. Create an entity for managing free courses. Create entity permission records to provide access to entity records for free courses and assign the entity permissions to users when they register on the portal for the first time.
C. Create an entity for managing free courses. Create a Students web role and set the Authenticated Users role option to true. Create appropriate entity permissions to access the free course entity records and assign the entity permissions to the web role.

Correct Answer:

C. Create an entity for managing free courses. Create a Students web role and set the Authenticated Users role option to true. Create appropriate entity permissions to access the free course entity records and assign the entity permissions to the web role.

Explanation:

In Power Apps Portals, entity permissions and web roles control access to Dataverse data. To automatically provide access to specific content (like free courses) to all signed-in users, you need a web role that is automatically applied to all authenticated users.

Here’s why Option C is correct:

• Creating an entity for free courses lets you manage course records within Dataverse.

• Defining entity permissions ensures that access is secure and granular—only users with assigned permissions can view or interact with course data.

• Creating a web role (e.g., Students) and setting the "Authenticated Users Role" to true means that any user who logs in to the portal is automatically assigned this role.

• Assigning the appropriate entity permissions to this web role allows every logged-in user to access the free courses without manual user-role mapping.

Option A is partly correct but lacks the step of creating entity permissions and assigning them to the web role, which is critical for access control.

Option B implies that permissions are assigned at registration time, which introduces complexity and does not scale automatically—you’d need a process to dynamically assign permissions, which is unnecessary if you configure the web role properly.

Summary:

• Question 2 Answer: A. List view of the entity

• Question 3 Answer: C. Create an entity for managing free courses... with web role and entity permissions

Question No 3:

A company uses Microsoft Dataverse to manage prospects, and to streamline this process, they have implemented a business process flow (BPF) named BPFA, which is currently associated with the Prospect entity. Recently, the company added a new field named Category to classify different types of prospects, and based on this field, they have developed multiple additional business process flows—each tailored to a specific category.

The goal is to ensure that users are able to switch between the newly created business process flows based on the Category, but they should no longer be able to use the original BPFA process for any Prospect records.

As the administrator, you need to configure the system so that users can freely work with the new business process flows but cannot select or use BPFA anymore.

What are two valid configuration options you can use to meet this requirement?

A. Remove all of the privileges for BPFA.
B. Use a business rule to prevent users from switching to BPFA.
C. Deactivate BPFA.
D. Change the display order of the business process flows to move BPFA to the bottom of the list.

Correct Answers:

A. Remove all of the privileges for BPFA
C. Deactivate BPFA

Explanation:

A Business Process Flow (BPF) in Microsoft Dataverse guides users through a series of stages and steps to ensure consistent data entry and adherence to business procedures. A BPF is tied to one or more entities (tables) and can be conditionally applied using logic based on fields (e.g., the Category field in this scenario).

In the given case, multiple business process flows have been created for different categories of prospects, but the original flow BPFA must no longer be used by users—while still allowing them to work with the new flows.

Let’s evaluate each option and see which ones are valid ways to achieve this.

This is a correct answer. Each business process flow in Dataverse is tied to a security object. You can control access to a BPF through security roles. By removing or revoking security privileges for BPFA in all user roles, you prevent users from seeing or selecting BPFA entirely. This method is effective when you want to disable access without deleting or deactivating the process (e.g., for auditing or future use).

This is another valid solution. Deactivating a BPF removes it from the list of selectable flows and prevents it from being applied to any records. It is a straightforward way to permanently retire a BPF that is no longer in use. Users will not see or be able to switch to BPFA once it's deactivated.

This option is not valid. Business rules in Dataverse are used to apply logic (e.g., hide fields, show error messages, set default values) at the form level. They cannot control or prevent which business process flow is selected for a record. You cannot use a business rule to restrict switching BPFs, as that is controlled by system-level settings and security, not business rules.

Changing the display order of BPFs only affects the default selection when multiple BPFs are available. It does not restrict users from manually selecting any available BPF—including BPFA. So while it might reduce visibility, it does not prevent its use, and therefore does not meet the requirement.

Summary:

To ensure users cannot use BPFA, but can still use other new business process flows:

• Use Option A to revoke permissions via security roles.

• Use Option C to deactivate the BPFA altogether.

Both methods effectively prevent users from accessing the old process flow.Would you like a visual guide or configuration steps for deactivating BPFs or editing security roles?

Question No 4:

You are tasked with implementing a new piece of business logic in a Microsoft Power Platform application. The application includes a Canvas App that contains a single screen named Screen1. You decide to use a business rule to enforce this logic. As part of the configuration, you must select the appropriate scope for the business rule so that it functions correctly within the Canvas App environment.

Considering that the business rule needs to run within a Canvas App and affect data at the entity level, which scope should be applied to the business rule to ensure proper functionality and reuse across multiple forms and applications?

A. Screen1
B. Entity
C. All Forms
D. Global

Correct Answer: B. Entity

Explanation:

Business rules in Microsoft Power Platform (specifically in Dataverse and model-driven apps) allow you to apply logic to data input and enforce validation without needing to write code. These rules can set field values, make fields required or visible, show error messages, and more—based on conditions.

When creating a business rule, you must define its scope, which determines where and how the rule is applied. The selection of scope is a critical decision—it controls how broadly the rule is enforced and whether it affects only forms or also server-side logic.This option is not valid in the context of configuring business rules in Dataverse.
Canvas Apps do not use “Screen” scope for business rules.
In Canvas Apps, logic is typically applied through formulas or Power Fx expressions.

When the scope is set to Entity, the business rule applies at the data level.It affects all forms, all apps, and even server-side processes.This means it runs both in model-driven apps and in any other context where the entity's data is involved, including Canvas Apps, Power Automate, and Dataverse APIs.
Entity scope ensures the logic is enforced universally, making it ideal for business-critical rules that should be applied consistently, no matter how the data is accessed or updated.
This scope limits the rule to client-side execution on model-driven app forms only.
It does not apply to Canvas Apps or server-side operations.While useful for UI-specific logic, it lacks the universal enforcement required for consistent data governance.
This is a misleading option. In the current Power Platform scope definitions, Global is not a valid or selectable scope in business rule settings.
Business rules are scoped at Form or Entity level in real-world use.Choosing Entity as the scope means the rule is evaluated whenever the data in that entity is created or updated, regardless of how or where that action takes place:

• Canvas Apps

• Model-Driven Apps

• Power Automate flows

• Custom integrations using the Dataverse Web API

This is essential for scenarios where data integrity must be enforced across all apps, not just UI forms.Unlike model-driven apps, Canvas Apps do not inherently support client-side business rules. Instead, they rely on the Dataverse entity rules to enforce logic. Therefore, any business rule meant to run in the background while a Canvas App user interacts with data must be defined at the entity level to work properly.

• Business rules must apply across multiple apps.

• You want data-level enforcement, regardless of how the data is modified.

• Your app includes Canvas Apps or Power Automate flows.

Summary:

To ensure that a business rule runs within a Canvas App, especially when working with Dataverse entities, the rule must be scoped at the Entity level. This ensures the logic is applied regardless of UI context, promoting data consistency and reusability across different apps and platforms within the Power Platform ecosystem.

Question No 5:

You are tasked with implementing a new feature for an app by creating a new entity. This entity must be linked to a business unit and its records need to have specified security roles that are associated with the business unit. Additionally, you need to configure the entity’s ownership model to ensure that proper access and security roles are maintained for each business unit.

Which type of entity ownership should you use for this scenario?

A. User or Team Owned
B. Organization Owned
C. None
D. Business Owned

Correct Answer:
D. Business Owned

Explanation:

When creating a new entity within an application, particularly in systems like Microsoft Dynamics 365 or other enterprise resource planning (ERP) tools, it is essential to configure the correct entity ownership type to ensure that security, data access, and business processes align with the organizational structure and business needs.

Entity ownership refers to who or what has control or authority over the records of the entity. In the context of enterprise applications, ownership is used to determine how security roles, permissions, and access are assigned to data records. It is also tied to user roles and business units to ensure that only authorized users or teams can access or modify the data. The four potential entity ownership options available are:

1. User or Team Owned

2. Organization Owned

3. None

4. Business Owned

Let’s break down the options and why Business Owned is the correct choice for this scenario:

1. User or Team Owned (Option A)

In a User or Team Owned model, records are associated with either a specific user or a team. This type of ownership means that the record’s access and security are controlled by the individual user or the team assigned to the record. For example, if a sales representative is assigned to a lead record, that record is owned by the sales rep or the team to which the lead is assigned.

This model is often used when there’s a need for individual responsibility over records. However, in this scenario, the requirement is to associate the entity records with a business unit, not an individual or a team. Therefore, User or Team Owned is not the ideal choice for configuring entity ownership because it does not provide a clear link to the business unit.

2. Organization Owned (Option B)

Organization Owned records are not associated with any specific user, team, or business unit. These records are accessible by all users within the organization, based on their security roles. This type of ownership can be useful in situations where data needs to be universally accessible across the entire organization, regardless of the user or business unit.

While this model might seem like a good option for ensuring broad access to records, it does not align with the specific requirement of associating records with a business unit. The security roles and access control in this case would be too generalized and would not support the need for business unit-specific configurations. As a result, Organization Owned is not the correct option here.

3. None (Option C)

The None ownership option is essentially a non-ownership model where no specific user, team, or business unit is assigned ownership of the records. This can be used in scenarios where you don’t need to define ownership, or in cases where ownership is determined by external processes or systems.

However, this is not suitable for this scenario because the entity records need to be associated with a business unit and specific security roles. Using None would leave the entity records without any defined ownership, which would make it difficult to enforce security roles or permissions at the business unit level.

4. Business Owned (Option D)

The Business Owned option is the most appropriate for this scenario. In this model, the entity records are owned by a business unit rather than by individual users or teams. This aligns perfectly with the requirement to associate records with a specific business unit.

With Business Owned records, the security roles and permissions for accessing and modifying the records are controlled by the business unit. This means that each business unit can have its own set of roles and permissions, which helps enforce security policies and ensure that only authorized users within the business unit can access or modify the entity records. This approach allows for better control and flexibility in managing security at the business unit level, while still ensuring that the entity records are tied to a specific organizational structure.

Conclusion

In this scenario, the best approach for configuring entity ownership is Business Owned (Option D). This ensures that the entity records are linked to a business unit, allowing for the assignment of security roles and access permissions that are specific to that business unit. By using this model, you maintain tight control over who can access and manage the data, aligning with both organizational needs and security requirements.