Microsoft Power Platform Fundamentals PL-900 (PL-900) — Questions 1–75

Environment Maker permits app creation within a given environment. Granting it only in Development means users can build there, while lacking the role in Production prevents them from creating apps in that environment, satisfying the restriction.

Connections are user-specific artifacts and are not carried inside a solution. After importing a managed solution that includes a custom connector, each user must create their own connection to that connector, and the app must reference a connection the running user owns. Because the maker holds Environment Maker but no connection existed yet, the app fails at runtime, matching the symptom precisely.

Run After settings define whether an action runs after the preceding action succeeds, fails, is skipped, or times out, letting the flow branch on failure. This satisfies the stem's requirement for implementing error handling within a Power Automate flow.

Power Apps model-driven apps suit this scenario because they build on Microsoft Dataverse tables, letting the sales manager track leads and opportunities using prebuilt entities and relationships — no custom development required. This directly satisfies the stem's constraint of avoiding code while delivering structured, data-driven sales tracking.

Power Automate provides event-driven cloud flows triggered by SharePoint list item modifications. A flow configured with the "When an item is modified" trigger and a condition checking Status equals 'Closed Won' then invokes the Outlook "Send an email" action, satisfying the automatic notification requirement without manual intervention.

Power Pages provides low-code, externally facing websites with built-in forms, authentication and Dataverse integration, so donations can be captured without writing code. It satisfies the public website requirement, unlike model-driven apps, which are internal, or canvas apps, which lack anonymous public hosting.

Copilot Studio deflects repetitive HR questions through conversational topics, so staff receive immediate answers while HR personnel redirect effort to strategic work. Automating routine inquiries is the primary business value, cutting ticket volume and response times.

The app-from-data wizard generates a working canvas app directly from a SharePoint list's schema, auto-creating browse, detail and edit screens without hand-written formulas. This satisfies the no-complex-formulas constraint, letting the analyst track team tasks immediately.

Power Automate provides built-in connectors and the Azure SQL Database connector, enabling automated invoice workflows to read and write ERP data without custom code. This satisfies the integration requirement by orchestrating triggers and actions between Power Platform and the Azure-hosted ERP.

Dataverse enforces role-based access at the environment and table level, so a user lacking a security role with read privilege on the relevant tables sees no records at all. This directly satisfies the stem's constraint: shared app access alone grants no data visibility, since app sharing and Dataverse security roles are independent permission layers.

SaveData writes a collection to local storage on the device, and LoadData restores it. In an intermittent-network warehouse, the app can capture scans into a collection, call SaveData, and later LoadData and submit when connectivity returns. This is the documented offline pattern for canvas apps and works without a network connection.

Form layout, field selection and control placement for model-driven apps are edited in the Power Apps maker portal, where the form designer exposes the table's fields. Editing records in the app itself changes data, not the form definition.

Downloading the report in the Power BI mobile app caches the report data locally on the device, satisfying the offline constraint in the stem. Once cached, the manager can open and interact with the report without network connectivity, which streaming or browser-based access cannot provide.

Power Automate's email trigger parses the notification, writes to Dataverse, sends the confirmation, and creates the To Do task in one flow, eliminating manual entry. It satisfies all three stated requirements without custom code or a new app.

FetchXML filters records using attribute conditions, so the statecode condition restricts results to active accounts while the createdon condition applies a rolling 30-day window. The attribute element limits returned columns to name, accountid and createdon, satisfying the stem's requirement to identify exactly which account data the query retrieves.

Copilot Studio provides a template gallery with prebuilt copilots for common scenarios, including customer support. These templates include sample topics and responses that can be customized. This allows non-programmers to quickly deploy a functional copilot. It is the fastest way to start.

Environments are the isolation boundary in Power Platform, and each is created in a specific geographic region where its data is stored. Creating environments in the required regions satisfies the stem's data residency constraint, since region selection at environment creation determines where data resides.

Power Apps includes an Excel connector that can connect to tables in Excel workbooks stored in OneDrive for Business or SharePoint. The app can read data and write back changes, such as adding or updating rows, as long as the data is formatted as a table. This allows business users to leverage existing Excel files as a lightweight data source.

AI Builder's custom document processing model learns your invoice layouts from labelled samples, so it extracts fields from non-standard PDFs that the built-in parser cannot handle, directly addressing the parsing accuracy failure in the flow.

Streaming datasets push data into Power BI as events arrive, bypassing the scheduled refresh cycle entirely. This satisfies the near-real-time requirement, whereas import-mode datasets refresh only at configured intervals and cannot deliver the low-latency insights business users need.

A canvas app suits this scenario because it gives pixel-level control over the mobile interface, letting employees capture receipt photos through the device camera and submit them directly. Power Apps canvas apps connect natively to Microsoft Dataverse or SharePoint for storing the images, satisfying the mobile capture and storage requirements.

Instant triggers run on demand, started manually by a user via a button or app. This is one of Power Automate's three trigger categories, satisfying the requirement for user-initiated flows rather than scheduled or event-driven ones.

Prebuilt templates let makers deploy a working bot for common scenarios without authoring dialogue from scratch, satisfying the requirement to identify genuine Power Virtual Agents capabilities. Templates ship with predefined topics and trigger phrases, so conversational logic is generated automatically rather than hand-built, which is a core authoring feature of the product.

The AI Builder 'Extract information from documents' action uses a prebuilt or custom document-processing model to return structured fields such as invoice total and vendor from a file. It is a no-code action that plugs directly into the flow, satisfying the requirement to avoid manual parsing expressions.

The Recurrence trigger allows you to schedule a flow to run at specific times and intervals, such as every weekday at 9:00 AM. This matches the requirement to periodically check for new orders and assign them. It provides control over the schedule and can be combined with actions to query Dataverse and update records.

Low-code drag-and-drop authoring with prebuilt connectors and templates removes much of the bespoke development effort, so business applications reach production far sooner than traditional coding projects. This directly satisfies the stem's requirement for a benefit that reduces application build time.

Canvas apps allow designers to drag and drop controls to create a custom user interface. They can easily integrate with SharePoint lists and use device capabilities like camera and microphone through controls such as Camera and Audio. This makes canvas apps ideal for building mobile inspection apps quickly without writing code. They are the recommended choice for this scenario.

A Switch control evaluates a single expression against multiple cases, branching the flow down exactly one matching path. This satisfies the stem's requirement for conditional logic by handling multi-outcome decisions, unlike loops or sequential actions, making it one of the two valid branching constructs in Power Automate.

Connectors assigned to the Blocked group in a data loss prevention policy are disabled for every app and flow in the environment where the policy applies. With Microsoft Teams and Twitter placed there, the default environment loses access to both connectors.

When a Dataverse column is marked as required, the corresponding action input must receive a value. If the analyst did not map dynamic content from the SharePoint output into that field, the action sends an empty value and Dataverse rejects it, producing exactly the missing-required-column error described in the scenario.

An on-premises data gateway brokers queries between Power BI cloud services and the internal SQL Server, enabling scheduled or near real-time refresh without exposing the database directly. It satisfies the real-time reporting constraint while keeping the data source on-premises.

DLP policies group connectors into Business, Non-Business, and Blocked. Connectors in the Business group can be used together. Twitter in the Blocked group cannot be used at all. This configuration allows SharePoint and Outlook in the same flow while blocking Twitter, exactly as required.

Microsoft Copilot Studio builds conversational copilots with generative answers and topic flows, and supports hand-off escalation to a live agent. This directly satisfies the requirement to answer common IT questions and escalate when needed, without custom code.

Actions define what the flow does after it starts. A flow with only a trigger would run and immediately end without accomplishing anything, so at least one action is required to summarize data and notify the team. Actions are the executable steps that carry out the business logic of the flow.

Dataverse provides a built-in data platform with standard tables, relationships and security, so makers bind controls to data without writing code. It satisfies the no-traditional-code constraint by removing the need to provision or query a separate database manually.

The Recurrence trigger is designed to run flows on a schedule. It allows specifying the frequency (e.g., Day, Week) and interval, and can be set to run only on weekdays by selecting specific days. This is the correct choice because it directly fulfills the requirement of running every weekday at a specific time. It is the standard trigger for scheduled flows.

Dataverse stores data in tables and enforces role-based security at environment, table and column level, satisfying the storage-with-security capability. This lets organisations centralise business data while controlling exactly which users can read or modify each record.

Power Automate provides low-code workflow automation through triggers and actions, letting employees build flows without programming. It directly satisfies the stem's no-code requirement, unlike Power Apps (app building) or Power BI (analytics). Its drag-and-drop designer and prebuilt connectors enable citizen developers to automate approvals, notifications and data movement.

Power BI connects directly to SQL databases, refreshes data on schedule or in real time, and publishes interactive dashboards shareable across the team. It satisfies the requirement for live sales reporting with collaborative distribution, unlike canvas apps or flow automation.

Microsoft Dataverse applies role-based security, assigning users security roles that grant privileges at table, record and column level, including owner-team and organisation scopes. This satisfies the requirement to control which users can read, create, update or delete specific data.

Canvas apps give the maker direct control over each control's properties, so conditional formatting such as highlighting overdue tasks uses formulas on the gallery's colour properties. Model-driven apps render forms from metadata and cannot express this per-record styling requirement.

The chart control in Power Apps can be bound to a data source such as a SharePoint list. It automatically updates when the underlying data changes, making it ideal for displaying a live monthly sales trend without additional components or refresh logic.

An automated cloud flow is triggered by an event rather than manual start, so the 'when a new email arrives' trigger fires on each incoming message. This satisfies the requirement for automatic execution, then a SharePoint action saves the attachment to the document library.

HTTPS encrypts browser-to-portal traffic by default, satisfying the security team's transmission requirement. Dataverse stores alumni profiles and interests, which Power Automate queries to trigger targeted emails. A custom connector lets low-code flows call the third-party payment gateway's REST API, meeting the donation integration need without bespoke code.

The trigger polls the specified SharePoint document library and fires when a new file with the .xlsx extension appears in the 'Incoming' folder, satisfying the scenario's file-creation condition. It uses the file extension filter to restrict firing to Excel workbooks only.

A gallery bound to the orders data source renders the list, and its OnSelect property can navigate to a detail screen passing the selected record's context. This single-screen-plus-detail pattern avoids duplicating controls per order, meeting the drill-down requirement efficiently.

Managed solutions are immutable in the target environment, so production changes cannot be edited directly. Pairing them with Azure DevOps pipelines enforces deployment gates, requiring review and approval before release. This satisfies the requirement that changes be approved prior to production deployment.

Each lookup field on a Power Pages form triggers a separate Dataverse query to populate its options, so load time scales with lookup count. Reducing lookup fields directly cuts those round trips, satisfying the stem's performance constraint. Filtered or dependent lookups, caching, and asynchronous loading do not eliminate the per-lookup query overhead that causes the slowness.

Security roles in Microsoft Dataverse define privileges at table and record level, including the Delete permission. Assigning a role without delete rights to the relevant users prevents case deletion while preserving read and update access.

The issue is that the Filter function on the Status column may not be delegable with the SharePoint connector, causing Power Apps to retrieve only the first 100 records. By using a delegable condition and confirming the connector supports delegation for that operation, the app can retrieve all matching items from the 8,000-item list.

Automating approval workflows is a core Power Automate use case, satisfying the requirement for multi-step, human-in-the-loop processes. Approval actions pause a flow, route requests to designated approvers via Microsoft 365 or Microsoft Entra ID identities, and resume based on the response, removing manual chasing and email-based sign-off.

Generative answers let a copilot retrieve content from configured knowledge sources and compose a natural language response grounded in that content. Adding a public website as a knowledge source means the copilot can search the site and answer volunteer policy questions without manually creating topic pairs. This directly matches the goal of reusing existing published content rather than authoring every answer by hand.

Power Apps provides a low-code canvas and model-driven builder for creating forms and apps without custom development, so the non-profit can rapidly digitise volunteer sign-up. Dataverse or SharePoint can store submissions, meeting the no-code and speed constraints.

The Offline capability lets canvas apps cache data locally on the device so technicians can record equipment issues without connectivity, then sync changes automatically once the network returns. This directly satisfies the stem's offline-and-sync requirement.

This trigger fires immediately when a new item is added to the specified SharePoint list, which is exactly the event the sales team wants to respond to. It provides the new item's properties as dynamic content so the subsequent email action can include order details. It is the standard, supported trigger for reacting to list item creation in SharePoint Online.

Power Pages provides a Copilot Studio chatbot component that can be placed on a page; configuring it with the bot's identifier and environment connects the portal to that published bot, satisfying the stem's integration requirement without custom code.

Sandbox environments are designed for development, testing, and training. They can include sample data and apps, and administrators can reset them to a clean state. This matches the requirement for a shared learning environment that can be reset.

Page permissions combined with anonymous and authenticated web roles let unauthenticated visitors submit tickets while restricting ticket detail views to signed-in users. This satisfies both the anonymous submission requirement and the authentication requirement for viewing ticket details.

Templates supply pre-built screens, controls and formulas, so the manager assembles and configures the app through the visual designer without authoring any code. This satisfies the no-code constraint, unlike pro-developer or blank approaches requiring manual formula or component construction.

A canvas app gives the field technicians a fully customised mobile interface, satisfying the requirement for a purpose-built logging experience. It connects directly to the existing SQL database through a native connector, so service calls are read and written without duplicating data or rebuilding the schema.

DLP policies in the Power Platform admin center classify connectors into Business, Non-Business and Blocked groups, then block combinations across those groups. This directly enforces the tenant-wide constraint that apps use only approved connectors and cannot reach unmanaged data sources.

The Filter function evaluates each record in array1 against the predicate Status = "Active", returning only matching rows. This satisfies the stem's requirement to identify the expression's behaviour: a row-level filter on the Status column, excluding records with any other status value.

Dataverse enforces business logic natively through calculated columns, rollup columns and business rules, so validation and derived values run consistently at the data layer regardless of which app accesses the table. This satisfies the requirement for centralised, reusable logic.

Managed solutions are locked, so changes are made only in a development environment and shipped as versioned artefacts. Exporting them to source control gives traceable history and enables rollback to a prior solution version, meeting the lifecycle management requirement.

Web roles in Power Pages define granular content-editing permissions per site section, satisfying the IT department's requirement that only authorised users modify content. Assigning departmental users to appropriate web roles restricts editing to authenticated individuals, unlike anonymous access. This directly enforces authorisation without relying on Microsoft Entra ID security group membership alone.

Power Apps enables non-developers to build a custom inventory-tracking app using pre-built connectors and a low-code canvas or model-driven interface, satisfying the constraint that the business lacks hired developers. Unlike Power Automate, which orchestrates workflows, or Power BI, which visualises data, Power Apps directly creates the interactive application needed for manual inventory data entry and lookup.

Enabling concurrency control lets the 'Apply to each' loop run multiple iterations in parallel rather than sequentially, directly addressing the slow runtime and timeout constraint. Power Automate processes iterations simultaneously up to the configured degree, cutting total duration for large datasets. This is the supported performance setting for loop-heavy flows.

The Outlook 'When a new email arrives' trigger fires on each incoming message, and the OneDrive 'Create file' action writes the attachment content to a folder. Together they satisfy the automatic copy requirement without manual intervention.

The Recurrence trigger is the built-in scheduling trigger in Power Automate. It lets you set an interval and frequency (for example, weekly) and then select specific days of the week, such as Monday through Friday, plus a start time of 8:00 AM. This directly implements the weekday morning schedule the scenario requires.

Canvas apps can be configured for offline use, which caches data locally on the device and synchronizes changes when the device reconnects. This allows the technician to record inspection results in areas without connectivity and have those records uploaded later. It directly addresses the need for continued operation without an active internet connection.

The Recurrence trigger allows specifying a weekly schedule with selected days. By choosing Week as the frequency and checking Monday through Friday, the flow will automatically run only on business days at the specified time. This eliminates the need for conditional logic to skip weekends and directly meets the requirement for weekday execution.

The Microsoft Forms connector provides the 'When a new response is submitted' trigger, which fires each time someone completes the specified form. This directly matches the requirement to react to new survey responses. After the trigger, you can add an action such as 'Get response details' to retrieve the respondent's email and then add them to the group.

Microsoft Copilot Studio supports multiple channels, including a demo website and Facebook. Publishing to these channels makes the copilot available on the company's website and on Facebook Messenger. This directly addresses the requirement for multi-channel availability and is a core capability of Copilot Studio, so this action is necessary to meet the scenario's accessibility goals.

The on-premises data gateway acts as a bridge between Power Apps and on-premises data sources like SQL Server. It allows secure data transfer without exposing the database to the internet. Installing and configuring the gateway is required for canvas apps to access on-premises SQL Server data.