PL-900 Practice Questions

Power BI dashboards are the correct solution for analyzing high-level KPIs. A dashboard is a single-page canvas in the Power BI service specifically designed to monitor business status at a glance. It aggregates the most important metrics (KPIs) from various reports into a unified, high-level view for decision-making.

Power BI reports are the correct solution for drilling down into details. Reports are multi-perspective views of a dataset that offer deep interactivity. The "Drill mode" (drill down, drill up, and drill through) is a specific feature of Power BI report visuals, allowing users to explore granular data hierarchies. While dashboard tiles generally link to reports, the actual action of drilling into visual details occurs within the report environment.

Microsoft. "Introduction to dashboards for Power BI designers." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/create-reports/service-dashboards

Relevance: Defines dashboards as a single canvas to "monitor your business and see all of your most important metrics at a glance."

Microsoft. "Dashboards vs. reports." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/consumer/end-user-dashboards#dashboards-vs-reports

Relevance: Explicitly compares features, noting that dashboards provide a "high-level" view while reports provide "more detail" and interactivity.

Microsoft. "Drill mode in the Power BI service." Microsoft Learn. Accessed November 28, 2025. https://learn.microsoft.com/en-us/power-bi/consumer/end-user-drill

Relevance: Confirm that drill actions (drill down/up) are operations performed on visuals within a report.

To implement the quality control check, the flow needs a decision point. After a request for confirmation is sent to the project lead, the flow must evaluate the response. A Condition control is the standard Power Automate component for this purpose. It creates two branches in the flow: an "If yes" branch and an "If no" branch. The flow will check the outcome of the confirmation (e.g., 'Approve' or 'Reject') and, based on that value, will execute the actions in the appropriate branch, such as sending the email to the project manager only if the task completion is approved.

A. a process argument: This is not a standard component used for creating conditional logic within a Power Automate cloud flow.

C. an expression: An expression is a formula used inside a condition or action to evaluate or transform data; it is not the control structure that creates the logical branch.

D. a trigger: A trigger is what initiates a flow. The requirement is to modify the logic after the flow has already started, not change how it starts.

E. an action: While sending an approval request is an action, the component that evaluates the result of that action and directs the flow's path is the condition control.

1. Microsoft Learn. "Add a condition to a flow." Power Automate Documentation. This document states

"Use a Condition card to have your cloud flow perform one or more tasks if a condition is true and to perform different tasks if the condition is false." This directly describes the required branching logic.

2. Microsoft Learn. "Create and test an approval workflow with Power Automate." Power Automate Documentation. Under the section "Add a condition

" the tutorial demonstrates the exact pattern required by the question: an approval action is followed by a Condition control that checks the outcome of the approval to decide the next step.

3. Microsoft Learn. "Build an approval flow with Power Automate." PL-900: Microsoft Power Platform Fundamentals Learning Path. This module explicitly details how to use the "Start and wait for an approval" action and then add a "Condition" to check the response

confirming this is the correct pattern for implementing approval-based logic.

Power Apps Portals use forms to show or edit a single Dataverse (formerly CDS) record. Lists surface multiple Dataverse records and support sorting, filtering, and pagination. SharePoint data is not native to portals, so a connector is required to bring SharePoint list data into the portal before it can be shown.

Microsoft Learn – Forms in Power Apps Portals

“Entity forms are used to display or edit a single Dataverse record.”

https://learn.microsoft.com/power-apps/maker/portals/configure/entity-forms

Microsoft Learn – Lists in Power Apps Portals

“Entity lists display multiple Dataverse records in a grid or list layout.”

https://learn.microsoft.com/power-apps/maker/portals/configure/entity-lists

Microsoft Learn – Using SharePoint Data with Portals

SharePoint requires connectors or integration to expose data to portals.

https://learn.microsoft.com/power-apps/maker/portals/admin/sharepoint-integration

1. KPIs (Key Performance Indicators): The KPI visual in Power BI is specifically engineered to communicate progress toward a measurable goal. It requires a base value (Quarterly sales total), a target value (Sales goal), and a trend axis. It is the correct choice for comparing current performance against a defined target.
2. Line chart: Line charts are the standard visualization for displaying continuous data over time. They are ideal for identifying trends, making them the correct choice for viewing sales trends by month.
3. Donut: Donut charts show the relationship of parts to a whole. When the requirement is to view data (Sales) broken down by category (Region) specifically as a percentage of the total, the Donut chart is the appropriate visualization type.

Microsoft Learn. (n.d.). Visualizations in Power BI reports:

KPIs: "A Key Performance Indicator (KPI) is a visual cue that communicates the amount of progress made toward a measurable goal."

Line charts: "Line charts emphasizes the overall shape of an entire series of values, usually over time."

Doughnut charts: "Doughnut charts are similar to pie charts. They show the relationship of parts to a whole."

Source: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-types-for-reports-and-q-and-a

Microsoft Learn. (n.d.). Create key performance indicator (KPI) visualizations:

"A KPI is designed for: Measuring progress (what am I ahead or behind on?). Measuring distance to a goal (how far ahead or behind am I?)."

Source: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-kpi

Dashboards can only be created in the Power BI Service, not in Power BI Desktop. Desktop builds reports and data models, but dashboards (collections of pinned visuals) exist exclusively in the Service. Likewise, sharing content with other users is a Power BI Service capability that supports permissions, sharing links, and app distribution. Therefore, both requirements rely entirely on the Power BI Service.

Microsoft Power BI Documentation – Dashboards

Microsoft Docs, “Dashboards in Power BI,” Section: You create dashboards in Power BI service.

https://learn.microsoft.com/power-bi/create-reports/service-dashboards

Microsoft Power BI Documentation – Sharing

Microsoft Docs, “Share dashboards and reports,” Section: Share from the Power BI service.

https://learn.microsoft.com/power-bi/collaboration/service-share-dashboards

The correct answer is 2 because the actor described is a "Customer." In Power Apps, only the App Owner or a user with Maker permissions can access the Versions tab and restore previous versions. A "Customer" (end-user) lacks these privileges, meaning the restore action cannot be performed. Consequently, no new version is created, and the list continues to display only the two existing versions (Version 1.0.0.0 and Version 2.0.0.0). If the user had Maker permissions, the count would be 3, but the options provided (max 2) force the strict application of the permission rule.

Microsoft Learn: Restore a canvas app to a previous version

"Only the app owner can restore a version of an app. To set a user as the owner of an app, use the Power Apps cmdlets for administrators."

Source: Restore a canvas app to a previous version - Power Apps | Microsoft Learn

Microsoft Learn: Save and publish a canvas app

"Each time you save a canvas app, you create a new version." (Confirming that creating/publishing V1 and V2 results in multiple version entries).

Source: Save and publish a canvas app - Power Apps | Microsoft Learn

The Microsoft Power Platform is a suite of low-code tools for business intelligence, application development, and process automation. Its core components include Power BI for data analysis and visualization, Power Apps for building custom applications, and Power Automate for creating automated workflows. Microsoft Flow was the original name for Power Automate and is still referenced in some contexts. These three products work together, often with Microsoft Dataverse as the underlying data service, to enable users to build comprehensive business solutions. Power Virtual Agents and Power Pages are also key components of the platform.

B. Azure Active Directory: This is Microsoft's cloud-based identity and access management service. While the Power Platform relies on it for authentication, it is a foundational Azure service, not a core Power Platform product.

D. Azure Machine Learning: This is a separate, advanced cloud service on Azure for building and deploying machine learning models. It can integrate with the Power Platform but is not a native component.

1. Microsoft Learn. (2023). What is Power Platform? Microsoft Docs. Retrieved from https://learn.microsoft.com/en-us/power-platform/admin/power-platform-overview.

Reference Point: The section "Power Platform overview" explicitly lists the key products: "The Power Platform is comprised of four key products: Power Apps

Power Automate

Power BI

and Power Virtual Agents."

2. Microsoft Learn. (2023). Get started with Power Automate. Microsoft Docs. Retrieved from https://learn.microsoft.com/en-us/power-automate/getting-started.

Reference Point: The first paragraph states

"In 2019

Microsoft Flow was officially renamed to Power Automate to better align with the Power Platform." This confirms that "Microsoft Flow" is synonymous with a core component.

3. Microsoft Learn. (2024). Study guide for Exam PL-900: Microsoft Power Platform Fundamentals. Microsoft Credentials. Retrieved from https://learn.microsoft.com/en-us/credentials/certifications/exams/pl-900/.

Reference Point: Under the "Skills measured" section

the objective "Describe the components of Power Platform" lists Power Apps

Power BI

and Power Automate as fundamental components.

To implement a prediction model using AI Builder, you must follow a specific lifecycle. First, the historical data required for the model to learn patterns must reside in Microsoft Dataverse (formerly Common Data Service); therefore, importing data is the prerequisite step. Once the data is available, you configure and train the model using that historical data. After the training process is complete and the model receives a performance grade, it must be published to make it accessible for consumption. Finally, the published model can be used within Power Apps or Power Automate (Microsoft Flow) to predict outcomes for new data.

Microsoft Learn. "Prediction model prerequisites". AI Builder Documentation. Available at: https://learn.microsoft.com/en-us/ai-builder/prediction-prereq. (States: "Your data must be in Microsoft Dataverse.")

Microsoft Learn. "Train and publish your prediction model". AI Builder Documentation. Available at: https://learn.microsoft.com/en-us/ai-builder/prediction-train-model. (Detailed steps on training and publishing).

Microsoft Learn. "Use your prediction model in Power Automate". AI Builder Documentation. Available at: https://learn.microsoft.com/en-us/ai-builder/prediction-pwr-automate.

Microsoft Learn. "Overview of the prediction model". AI Builder Documentation. Available at: https://learn.microsoft.com/en-us/ai-builder/prediction-overview.

For the first component, Connectors are the functional interfaces (wrappers around an API) that enable Power Automate to communicate with underlying services, including third-party cloud applications. Gateways are specifically for on-premises connectivity, not cloud-to-cloud interactions.

For the second component, Triggers are the events that initiate a flow. Specifically, a Polling Trigger is configured to periodically check an external service for new data or changes at defined intervals to determine if the workflow should execute. "Actions" refer to the steps executed after the flow has been triggered, and "DirectQuery" is a Power BI data retrieval method.

Microsoft. "Connectors overview." Microsoft Learn: Power Platform. Accessed November 28, 2025. https://learn.microsoft.com/en-us/connectors/connectors

Microsoft. "Use a polling trigger for Microsoft Power Automate." Microsoft Learn: Power Automate. Accessed November 28, 2025. https://learn.microsoft.com/en-us/connectors/custom-connectors/use-polling-trigger

Microsoft. "Custom connectors." Microsoft Learn: Power Automate. Accessed November 28, 2025. https://learn.microsoft.com/en-us/connectors/custom-connectors/

A business process flow is used when you need to guide users through a consistent sequence of steps, ensuring uniform task completion. An instant flow is appropriate when a user needs to trigger an action manually, such as sending an email after completing a task. A scheduled flow runs on a predefined interval, making it suitable for sending weekly summaries automatically.

Microsoft Learn – Types of Power Automate Flows

Defines automated, instant, scheduled, and business process flows and their use cases.

Microsoft Learn – Business Process Flows

Explains guided task-stage progression for consistent processes.

Microsoft Learn – Schedule Recurrence Trigger

Describes how scheduled flows run on a recurring timetable.