PL-200 Practice Questions

Box 1: To trigger a process based on a tile value, you must first configure the data alert definition (threshold and condition) directly within the Power BI service. Data alerts are set on specific dashboard tiles (such as cards, gauges, and KPIs). While Power Automate is used to define the actions (the process) that occur after the alert is fired, the alert itself—the trigger condition—must be configured on the dashboard tile in Power BI.

Box 2: Data alerts in Power BI are strictly personal and isolated to the user context. According to official documentation, only the person who created the alert can see or manage it. Even if a dashboard is shared with other users or published in an app, those users cannot view the alerts created by the owner; they must configure their own alerts on the shared dashboard if they wish to be notified.

Microsoft Learn. (2023). Set data alerts in the Power BI service. "Alerts are unique to you." Section: Who can set alerts. Retrieved from https://learn.microsoft.com/en-us/power-bi/create-reports/service-set-data-alerts

Quote: "Only you can see the alerts you set, even if you share your dashboard. Data alerts are fully synchronized across platforms..."

Microsoft Learn. (2023). Integrate Power BI data alerts with Power Automate. Section: Create a data alert. Retrieved from https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-flow-integration

Quote: "First, create a data alert in Power BI... Open the dashboard... Select the ellipsis (...) on the tile you want to alert on, and select Manage alerts."

To implement the logic in a "single evaluation statement" (an IF/ELSE IF structure):

1. 0-35: Use Check Condition to initiate the logic block (acting as the initial IF Rating <= 35).
2. 36-60: Use Conditional Branch to define the first alternative (acting as ELSE IF Rating <= 60).
3. 76+: Use Conditional Branch to explicitly target the final range (acting as ELSE IF Rating > 75). Note: You cannot use Default Action (ELSE) for the "76+" slot because the source table includes a "High" category (60-75) which is not in the answer area. Using "Default Action" would incorrectly process the 60-75 range as "76+" (Very High), creating a logic error.

Microsoft Learn - Configure workflow steps: Defines the logic components where "Check Condition" is a logical "if-then", "Conditional Branch" is a logical "else-if-then", and "Default Action" is a logical "else".

Source: Configure workflow stages and steps in Dataverse

Microsoft Learn - Process Logic: Describes how to use conditional branching to handle multiple outcomes in a business process or workflow without defaulting incorrect values.

Source: Enhance business process flows with branching

To construct a functional site map in Dynamics 365, you must follow the architectural hierarchy defined by the Site Map Designer. The process begins by defining the Area, which serves as the top-level container for the application's navigation (e.g., "Sales"). Next, you must Add a group within that area; groups act as headings to organize related navigation items. Finally, you Add a subarea within the group. The subarea is the actual actionable element that links to specific tables (entities), dashboards, web resources, or URLs. This cascading structure (Area > Group > Subarea) is mandatory for a valid site map.

Microsoft Learn - Power Apps Documentation

Article: "Create a site map for a model-driven app using the site map designer"

Section: "Add components to the site map"

Relevance: This documentation explicitly outlines the components of a site map. It defines the structure as: "Area: The top-level navigation...", "Group: A heading under an area...", and "Subarea: A link under a group...". It confirms that these are the three essential components required to build the navigation structure.

Source: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-site-map-app

Microsoft Learn - Power Apps Documentation

Article: "Understanding model-driven app components"

Section: "Navigation"

Relevance: Confirms that "Site maps define the navigation for your app" and that the hierarchy consists of Area, Group, and Subarea, distinct from data components like Views.

Source: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/model-driven-app-components

For the first action, the goal is to maintain referential integrity by blocking the deletion of a parent record (Contact) while it still has associated child records (Phone). In Microsoft Dataverse, the Restrict delete behavior prevents a record from being deleted if related records exist.

For the second action, the requirement is to synchronize ownership changes between the parent and child records. When a Contact (parent) is assigned to a new owner, the Assign action must propagate to the Phone records (child). The Cascade All behavior ensures that the same action (assignment/change of ownership) performed on the parent record is automatically applied to all related child records.

Microsoft Learn - Table relationships: See the section "Table relationship behavior" which defines the specific behaviors for cascading actions.

Quote: "Restrict: Prevents the Referenced table record from being deleted when it is related to Referencing table records."

Quote: "Cascade All: Perform the action on all referencing table records associated with the referenced table record."

URL: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships

Microsoft Learn - Configure cascading behavior: This documentation details how to configure 1:N relationships and the implications of "Assign" and "Delete" actions.

URL: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup#table-relationship-behavior

The Identify field should use the built-in Number entity (which already recognises ages such as “23”) so the bot receives an integer it can branch on (≤17, 18-25, etc.). The Date and time entity returns a full date/time value; Power Virtual Agents cannot directly calculate the customer’s age from that value without calling an external flow, so the required age-group logic would fail. Therefore the proposed solution does not meet the goal.

A. Yes – Choosing Date and time would capture a birth date, not an age; PVA lacks native date-difference calculation, so conditional branches cannot directly evaluate the five age ranges.

1. Microsoft Learn

“Use built-in entities in Power Virtual Agents” – section “number” (recognises ages). https://learn.microsoft.com/power-virtual-agents/advanced-entities

2. Microsoft Learn

“Add branching logic in a topic” – shows numeric comparisons using integer variables (no date-difference function). https://learn.microsoft.com/power-virtual-agents/branching

3. Microsoft Learn

“System entities: datetime” – returns date/time value without age calculation. https://learn.microsoft.com/power-virtual-agents/advanced-entities#datetime

To prevent general users from accessing the Sandbox instance while maintaining their access to Production, the administrator must use Security Groups. This is the standard architectural method for environment isolation.

1. Microsoft 365 admin center: You must create a Security Group (or use an existing one) and add only the authorized users (e.g., developers, testers) as members.
2. Dynamics 365 Sandbox instance: You must edit the instance settings to associate it with that specific Security Group. Once a security group is assigned to an environment, only users who are members of that group can access it. All other users (including those recording data in Production) will be denied access to the Sandbox entirely.

Microsoft Learn, "Control user access to environments: security groups and licenses", Section: Associate a security group with an environment. Available at: https://learn.microsoft.com/en-us/power-platform/admin/control-user-access

Microsoft Learn, "Create and manage environments in the Power Platform admin center", Section: Security group. Available at: https://learn.microsoft.com/en-us/power-platform/admin/create-environment#security-group

Microsoft Learn, "Manage user accounts, user licenses, and security roles", Section: Security groups. Available at: https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/admin-users-licenses-roles

The goal is to minimize Dataverse storage consumption. Enabling attachments for a table creates a relationship with the Notes (Annotation) table. Any files attached to these notes are stored within the Dataverse File storage capacity. While this is a valid way to store documents, it directly consumes Dataverse storage. A superior solution for minimizing Dataverse storage would be to integrate with SharePoint, which stores the documents in a SharePoint library, external to Dataverse. Therefore, the proposed solution does not meet the stated goal of minimization.

A. Yes: This is incorrect because enabling attachments consumes Dataverse File storage, which is contrary to the primary goal of minimizing its use.

1. Microsoft Learn. (2023). Manage storage and capacity in Microsoft Dataverse. In "Administer Microsoft Power Platform". "File capacity is used to store email attachments

notes

and files." This confirms that attachments consume Dataverse storage.

2. Microsoft Docs. (2023). Set up SharePoint integration. "With SharePoint document management you can... store documents on SharePoint in the context of a model-driven app record...". This demonstrates that SharePoint integration stores files externally

thus minimizing Dataverse storage consumption.

3. Microsoft Docs. (2023). Notes (annotation) table. "When you add a note to a record

you are creating an annotation record. The file attached with the note is stored in Azure Blob storage

and it is counted towards your file storage capacity." This explicitly states that attachments consume the Dataverse file storage capacity.

For the first requirement, the FAQbot was purchased from AppSource, meaning it is an existing solution installed in the environment. In Power Platform Solutions, to bundle this purchased component into your custom "communication solution," you must add (import) the existing app rather than creating a new one or importing a raw file definition ("Import bot").

For the second requirement, after the bot is added to the solution, you must enable and configure the Microsoft Teams channel within the bot's settings (Copilot Studio/PVA portal) to make it accessible to users in Teams. "Import a chatbot" into Teams would be a deployment step (sideloading), but "Configure" is the necessary setup action described.

Microsoft Learn: Add an existing chatbot to a solution - Explains the ALM process of adding existing bots (often treated as apps/components) to a solution file for distribution. [Reference: https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-export-import-bots]

Microsoft Learn: Configure Microsoft Teams channel - details the steps to "Configure" the Teams channel for a Power Virtual Agents bot. [Reference: https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-fundamentals-publish-channels?tabs=teams]

To automate a qualification verification process where data is stored in Microsoft Dataverse, the automation tool, likely a Power Automate cloud flow, must first connect to the data source. This is achieved by adding a Dataverse connector.

A robust business process requires a trackable item for the verification task. Creating a new record, such as a "Service Request" (or a Case/Task), formalizes the verification, allowing it to be assigned, monitored, and have its status updated through a defined lifecycle. This combination establishes the connection to the data and initiates the trackable process.

B. Add an Outlook connector.

While notifications via Outlook can be part of a process, creating a trackable record is more fundamental to managing the verification itself than sending an email.

C. Create an on-premises data gateway reference.

An on-premises data gateway is only required to connect to data sources located outside of the cloud, which is not indicated by the scenario.

D. Update the Qualification records to finished.

This action would occur at the end of the verification process, not at the beginning when the automation is initiated to start the verification.

1. Microsoft Learn. (2023). Overview of the Microsoft Dataverse connector. In "Use the Dataverse connector in Power Automate". This document explains that to "create flows that are triggered by create

update

and delete events on rows" in Dataverse

the Dataverse connector is required. This supports option A.

2. Microsoft Learn. (2023). Create rows in Microsoft Dataverse. In "Microsoft Dataverse connector reference". This section details the "Add a new row" action

which is used to create a new record in a specified table (such as a "Service Request" table) as part of a business process automation. This supports option E.

3. Microsoft Learn. (2023). What is an on-premises data gateway? This document clarifies that the gateway "acts as a bridge to provide quick and secure data transfer between on-premises data... and several Microsoft cloud services." This explains why option C is incorrect for a cloud-based Dataverse scenario.

Requirement 1 (Fallback topic): In Power Virtual Agents, the System Fallback topic is the specific component designed to handle unrecognized user input ("unknown questions"). When the natural language understanding (NLU) model cannot match a user's utterance to an existing topic with sufficient confidence, the bot triggers the Fallback topic to ask for clarification or offer generic assistance, rather than simply failing or escalating immediately.

Requirement 2 (Omnichannel for Dynamics 365 Customer Service): To redirect a conversation to a live staff member (agent), the bot uses a "Transfer to agent" node. This node requires a connected engagement hub to route the chat. Omnichannel for Dynamics 365 Customer Service is the officially supported customer service application that acts as the destination component, receiving the conversation context and routing it to the appropriate human agent queue.

Microsoft Learn. (n.d.). Configure the system fallback topic in Microsoft Copilot Studio. Retrieved from https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-system-topics-fallback

Quote: "The system fallback topic is triggered when the copilot can't find a matching topic for the user's input."

Microsoft Learn. (n.d.). Configure handover to Omnichannel for Dynamics 365 Customer Service. Retrieved from https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-hand-off-omnichannel

Quote: "You can configure your copilot to hand off conversations to a live agent... Power Virtual Agents supports ... Omnichannel for Dynamics 365 Customer Service."

Microsoft Learn. (n.d.). System topics in Microsoft Copilot Studio. Retrieved from https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-system-topics

Relevance: Defines the distinct roles of the "Escalate" topic (triggered by explicit requests for an agent) versus the "Fallback" topic (triggered by unknown input).