Microsoft PL-200 Exam
Microsoft Power Platform Functional Consultant (Page 3 )

Updated On: 1-Feb-2026

You attempt to deactivate several currencies in a Microsoft Dataverse environment.
You are not able to deactivate one of the currencies.
You need to determine why you cannot deactivate the currency.
What is the reason?

  1. You are not the currency record owner.
  2. The currency is used by an active business process.
  3. The currency is the base currency.
  4. The currency is used by another record.

Answer(s): C

Explanation:

The base currency cannot be deactivated.
Incorrect:
Not D: You can't delete currencies that are in use by other records, but you can deactivate them. Deactivating currency records doesn't remove the currency information stored in existing records, such as opportunities or orders. However, you won't be able to select the deactivated currency for new transactions.


Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/org-service/web-service-error-codes https://docs.microsoft.com/en-us/power-platform/admin/manage-transactions-with-multiple-currencies



A user has access to an existing Microsoft Dataverse database.
You need to ensure that the user can create canvas apps that consume data from Dataverse. You must not grant permissions that are not required.
Which out-of-the-box security role should you assign to the user?

  1. Environment Admin
  2. Basic User
  3. Environment Maker
  4. System Customizer

Answer(s): C

Explanation:

The Environment Maker can create new resources associated with an environment, including apps, connections, custom APIs, gateways, and flows using
Microsoft Power Automate. However, this role doesn't have any privileges to access data within an environment (but this user has this already according to the question).
Incorrect:
Not Environment Admin: The “Environment Admin” role can perform all administrative actions on an environment.
Not System Customizer: Has full permission to customize the environment. However, users with this role can only view records for environment entities that they create.
Not Basic User: Can run an app within the environment and perform common tasks for the records that they own. Note that this only applies to non-custom entities.


Reference:

https://docs.microsoft.com/en-us/power-platform/admin/database-security



DRAG DROP (Drag and Drop is not supported)
You are configuring Microsoft Dataverse security. You plan to assign users to teams.
Record ownership and permissions will differ based on business requirements.
You need to determine which team types meet the requirements.
Which team type should you use? To answer, drag the appropriate team types to the correct requirements. Each team type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Microsoft Teams team
Dataverse supports two types of record ownership. Organization owned, and User or Team owned. This is a choice that happens at the time the table is created and can't be changed. For security purposes, records that are organization owned, the only access level choices is either the user can do the operation or can't.
For user and team owned records, the access level choices for most privileges are tiered Organization, Business Unit, Business Unit and Child Business Unit or only the user's own records. That means for read privilege on contact, I could set user owned, and the user would only see their own records.

Box 2: Access team -
An access team doesn't own records and doesn't have security roles assigned to the team. The team members have privileges defined by their individual security roles and by roles from the teams in which they are members. The records are shared with an access team and the team is granted access rights on the records, such as Read, Write or Append.


Reference:

https://docs.microsoft.com/en-us/power-platform/admin/wp-security-cds https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-access-teams-owner-teams-collaborate-share-information



A company has locations in the United States, Brazil, India, and Japan. The company conducts financial transactions in all of these regions.
Financial transactions in Brazil are going to stop, but the office will remain open.
Users must no longer be able to create records associated with the Brazilian currency. Historical records must remain intact.
You need to configure Microsoft Dataverse to meet the requirement
What should you do?

  1. Disable the Brazilian language pack.
  2. Rename the Brazilian currency.
  3. Delete the Brazilian currency record.
  4. Deactivate the Brazilian currency record.

Answer(s): D

Explanation:

You can't delete currencies that are in use by other records; you can only deactivate them. Deactivating currency records doesn't remove the currency information stored in existing records, such as opportunities or orders. However, you won't be able to select the deactivated currency for new transactions.


Reference:

https://docs.microsoft.com/en-us/power-platform/admin/manage-transactions-with-multiple-currencies



HOTSPOT (Drag and Drop is not supported)
You are setting up Power Apps security for a company. The company has a CEO, two vice presidents, and 10 managers. Five support representatives report to each manager.
You set up Manager Hierarchy so managers are able to view data only for the representatives who report to them. The CEO must be able to view all data for everyone. All support representatives must be able to view customer information in each other's data across all managers.
You need to resolve issues that arise during testing.

What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Move the manager and reports to a separate business unit.
Keep the Manager hierarchy, and put the reports to the appropriate business unit.
Note: Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy. With the Manager hierarchy, a manager must be within the same business unit as the report, or in the parent business unit of the report's business unit, to have access to the report's data. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers' accessing data outside of their business units. However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.

Box 2: Add the CEO to the representative user record as a manager.
Set up Manager and Position hierarchies
The Manager hierarchy is easily created by using the manager relationship on the system user record. You use the Manager (ParentsystemuserID) lookup field to specify the manager of the user.
Incorrect:

Not Change the Manager Hierarchy depth to 3: Depth of 3 not required. Depth 2 is ok.
Note: Depth is used to limit how many levels deep a manager has Read-only access to the data of their reports. For example, if the depth is set to 2, the CEO can see the data of the VP of Sales, VP of Service and Sales and Service Managers. However, the CEO doesn't see the Sales data or the Support data.

Box 3: Add users to field security
Power Platform's field-level security lets you set which fields users can see or edit.


Reference:

https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security https://docs.microsoft.com/en-us/power-platform/admin/field-level-security



Viewing page 3 of 45
Viewing questions 11 - 15 out of 318 questions



Post your Comments and Discuss Microsoft PL-200 exam prep with other Community members:

Join the PL-200 Discussion