Microsoft Power Platform Fundamentals PL-900 (PL-900) — Questions 226–300

An on-premises data gateway creates a secure outbound channel from your local network to Microsoft cloud services, letting a cloud flow reach the file share on the local drive. This directly satisfies the requirement to automate moving files from a local network drive into SharePoint Online.

The on-premises data gateway is installed on a machine inside the local network and creates an outbound, encrypted connection to Azure Service Bus. Power Automate then routes SQL requests through this gateway, allowing the cloud flow to reach the internal SQL Server without exposing it to the internet. It is the standard mechanism for this exact requirement.

Reviewing storage analytics in the Power Platform admin centre identifies which tables consume the most capacity, letting the administrator target oversized entities before deleting anything. This directly satisfies the stem's constraint of freeing storage without removing important data, since analytics reveals what can be archived or trimmed rather than blindly purged.

Power Automate is a native Power Platform service for building cloud flows and desktop flows that trigger on events such as a new loan application or an approval decision. It integrates with hundreds of connectors, enabling the firm to route documents, send notifications, and enforce approval steps automatically, which is exactly the kind of manual-work reduction the department is seeking.

Independent actions that do not rely on each other's outputs can run simultaneously rather than sequentially. Parallel branches cut total flow duration, directly improving performance, and reduce the chance that one slow action delays the rest of the run.

AI Builder provides prebuilt and custom AI models, including text classification, which can categorise incoming emails into Complaint, Request or Other. It integrates directly into Power Automate flows, satisfying the requirement to classify before ticket creation without bespoke model development.

Parse JSON validates incoming content against a defined schema. When the updated email template altered the body's structure, the payload no longer conformed to that schema, so the action rejected it with a BadRequest error rather than parsing the fields.

The Power Platform admin center provides a graphical interface for provisioning environments, satisfying the stem's requirement for a valid creation method. An administrator selects New environment, supplies name, region, type and Dataverse options, and the platform provisions it, so no code or scripting is needed.

Power Virtual Agents builds conversational chatbots that handle common IT support queries and can hand off to a human agent through configured escalation triggers. This directly satisfies the stem's requirement for a chatbot with human escalation, unlike flow or app components that lack native conversational interfaces.

Offline capability requires the app to store data on the device, since the stem's constraint is no internet in remote areas. Enabling offline use with local caching lets technicians load and submit records without connectivity, syncing to the data source once the device reconnects.

Creating apps requires the Environment Maker role, which is separate from licensing. A Power Apps licence alone grants usage rights, but without Environment Maker assigned in the default environment the user cannot create apps there.

SharePoint lists expose structured data through the SharePoint connector, which canvas apps consume natively via Power Fx formulas such as Filter and Patch. This satisfies the stem's requirement for a usable data source, letting makers read and write list items directly without custom code or an intermediate integration layer.

The 'Test bot' pane provides an immediate, integrated testing environment within Copilot Studio. The maker can type messages and see responses, including variable values and topic triggers, without publishing. This is the simplest and fastest way to test a new topic and ensure it behaves as expected.

The retry policy on an action controls how Power Automate handles transient failures. Setting a fixed interval with a count of 3 makes the action retry three times before the run is marked as failed. This directly addresses the requirement for automatic retries on temporary outages without additional flows or code.

Power Virtual Agents is the Power Platform service for building low-code chatbots. It can answer patient questions by drawing on knowledge sources and can be integrated with Power Automate to send appointment reminders. This aligns with the healthcare organization's need for a conversational interface that uses existing knowledge articles without custom coding.

'Configure Run After' defines how downstream actions respond when a preceding action fails, times out or is skipped, enabling graceful error handling and escalation. This prevents silent failures in production flows, satisfying the best-practice requirement for resilient design.

Business process flows give model-driven apps stage-based, guided navigation that enforces a consistent sequence of steps across the app. This directly satisfies the stem's requirement for a capability that guides users through defined stages, which canvas apps lack natively.

Native connectors let flows and apps consume Microsoft 365 data and Azure services without custom middleware, so existing investments extend into new solutions. This integration is a core business value, reducing duplication and accelerating delivery across the tenant.

A canvas app from a template provides pre-built screens and controls that the analyst can configure through drag-and-drop, satisfying the no-code requirement. Templates for request tracking already include forms and galleries, so the analyst customises rather than builds from scratch. This suits a simple vacation-request app without writing formulas or code.

The Conversation Start system topic runs automatically when a chat session begins. Using the User.DisplayName system variable retrieves the authenticated user's name from Microsoft Entra ID, and a menu can be added with question or message nodes. This directly fulfills the requirement without user input for the name.

The Details page setting binds each Entity List row to a target web page and passes the record ID as a parameter, enabling row-click navigation to a detail view. Without this configured, rows render but remain non-clickable, so it directly satisfies the stated navigation requirement.

Concurrency control on 'Apply to each' allows multiple iterations to run in parallel. Since the email action is independent per item, increasing the degree of parallelism reduces the total run time. This is the appropriate setting to speed up the loop without changing its logic or the data being processed.

The Power Platform admin center provides activity logs for environment-level events, including who created, modified, or deleted apps and flows. Enabling and reviewing these logs lets the administrator trace app changes back to the responsible user. This directly satisfies the requirement of recording and attributing changes made to apps in the production environment.

SharePoint's connector delegates only certain filter operations on indexed columns, so the query executes server-side and returns just matching rows rather than the full 10,000 items. This directly addresses the slow loading caused by pulling the entire list into the app.

Managed solutions are the deployment artefact for downstream environments: they are locked, support clean upgrades, and prevent unintended customisation in the test environment. Exporting managed from development and importing into test follows Microsoft's recommended application lifecycle management approach.

Publishing to Power BI service and scheduling a daily refresh lets the service re-read the Excel source automatically, so the dashboard shows current figures without manual republishing. Weekly source updates are comfortably covered by a daily refresh cadence.

Automation is needed to perform the reset.

Delegable queries push filtering to the data source rather than pulling entire tables to the client, so the canvas app retrieves only matching records. With over 50 data sources, this sharply cuts the volume transferred and processed locally, directly addressing the slow loading caused by non-delegable operations.

OAuth 2.0 is the only custom connector authentication type supporting the client credentials grant, where the app authenticates as itself using a client ID and secret rather than a signed-in user. This satisfies the API's machine-to-machine requirement.

Power Automate enforces a maximum file size for actions handling file content, so large video files exceed that limit while PDFs pass. The flow fails because the video's size breaches the platform's file size ceiling.

'Start an approval' is another valid action in Power Automate's Approvals connector. It initiates an approval request but does not wait for the outcome; the flow continues immediately. This is useful when you want to send an approval and handle the response asynchronously, perhaps via a separate trigger. It is distinct from 'Start and wait for an approval'.

The Power Platform admin center provides analytics and usage reports for Power Apps, Power Automate, and other services. Administrators can view metrics such as the number of apps and flows per environment, active users, and resource consumption. This centralized tool is designed for tenant-wide monitoring and is the appropriate choice for identifying high-resource environments.

Adding a knowledge source lets the copilot ground its answers in specified SharePoint documents, retrieving content at query time rather than relying on the model's pretrained knowledge. This satisfies the requirement to answer IT policy questions from existing SharePoint content.

Power Automate flows can be invoked as plugins from Copilot Studio, letting the copilot trigger multi-step actions. The flow performs the Dataverse record creation and approval email, satisfying both required outcomes within one orchestrated automation.

Model-driven apps are built on Dataverse and require at least one table to store and relate data. Tables define the schema, relationships, and business logic that the app's forms, views, and dashboards surface. Without Dataverse tables, a model-driven app cannot be created or run.

A Condition action evaluates whether the manager is on leave, branching the flow so the approval goes to the next-level manager when true. This satisfies the escalation requirement within a single flow, avoiding parallel branches or separate flows that would duplicate logic.

ARM deployments of Power Pages read the identityProviders property to set authentication; supplying an 'authentication' property instead leaves the default local provider in place. Correcting the property name and its Microsoft Entra ID configuration resolves the mismatch described in the stem.

Correct. SharePoint lists are easy to set up, require minimal administration, and are often included with Microsoft 365 subscriptions. Canvas apps are low-code and easy to maintain, making this combination ideal for the business's constraints.

ClearCollect pulls data into a local collection once, so subsequent control references read from memory rather than re-querying each connected source. This directly addresses the slow canvas load caused by repeated delegation and network round-trips across multiple data sources, cutting per-control fetch overhead during rendering.

Power Apps provides a no-code canvas app builder, letting technicians capture text and photos through mobile-optimised interfaces without writing code. It directly satisfies the stem's constraint of code-free mobile data submission, unlike flow-based or dashboard-only tools.

SharePoint triggers bind to a specific library path; if the trigger watches the root rather than the 'Pending' folder, uploads into that subfolder never fire it. Correcting the trigger's folder setting resolves the missing runs.

This action creates an approval request that can be delivered through the Approvals app in Microsoft Teams, and it blocks the flow until the approver responds. The action returns an outcome value such as Approve or Reject that subsequent actions can branch on, which is exactly the pause-and-decide behavior the finance team needs.

A trigger is the event that starts a flow; the SharePoint 'When a file is created (properties only)' trigger fires on new items in a document library, satisfying the automatic-notification requirement without polling or a scheduled recurrence.

Canvas apps render a fully customisable interface and, with offline capability enabled, cache data locally so technicians can view work orders and capture photos without connectivity, syncing once the network returns. This directly satisfies the stem's offline requirement, which model-driven apps cannot meet.

Power Automate triggers workflows from Dataverse record changes, so a new customer interaction can automatically send a follow-up email without code. This satisfies the no-custom-development constraint, whereas Power Apps would require building an app and Power BI only reports on data.

The Navigate function can pass context variables to the target screen. By specifying a record in the third argument, you create a variable (SelectedCustomer) that holds the selected item. The detail screen can then reference SelectedCustomer to display the record's fields. This is the standard way to pass data between screens in canvas apps.

Enabling authentication and selecting Microsoft Entra ID as the identity provider allows the copilot to authenticate users with their organizational credentials. This is required to access personalized data and ensure secure interactions. Without authentication, the copilot cannot reliably identify the user to retrieve their specific Dataverse records.

A scheduled cloud flow that silently stops running for a week is typically disabled. When a flow is turned off in the Power Automate portal, its schedule trigger no longer fires, so no runs appear. Re-enabling it restores the daily 8:00 AM executions.

The 'When an item is created' trigger fires when a new item is added to a SharePoint list. It returns the item's field values, including Title, which can then be passed to the Planner 'Create a task' action. This trigger directly matches the requirement of reacting to a new SupportRequests list item and using its Title as the task title.

Dataverse enforces relationships between tables, including one-to-many and many-to-many with cascading behaviour and lookup columns, which satisfies the stem's requirement for rich relationships as a benefit over flat sources such as SharePoint lists or Excel.

Sharing the app directly grants the volunteer run-only access to that single app, satisfying least privilege. It avoids assigning environment-level roles or maker permissions, so the volunteer cannot edit the app or reach other environment resources.

A daily scheduled refresh that fails leaves the dataset at its last successful load, so users see data two days old. Checking the refresh history in the semantic model settings confirms the failure and its error, distinguishing this from gateway or credential issues.

Microsoft Entra ID authenticates the canvas app user, and Dataverse is a first-party connector, so the app reaches it through the Power Platform service directly. No on-premises data gateway is required, satisfying the without-a-gateway constraint.

The flow runs successfully, so the trigger and actions work; placeholder text in the body means the employee name token was never bound to the actual field. Inserting the correct dynamic content token from the NewEmployees row resolves it.

Power BI is a core Power Platform component, providing business analytics and interactive reporting over datasets, and is listed by Microsoft among the platform's four components with Power Apps, Power Automate and Power Virtual Agents.

Capacity add-ons, including AI Builder credits, are consumed tenant-wide rather than per environment, so they are tracked under Resources > Capacity in the Power Platform admin center. This satisfies the requirement to view purchased add-ons for the whole tenant.

Row-level security applies DAX filter expressions to a role, restricting each store manager's dataset rows to their own store while sharing one semantic model. This satisfies the stem's constraint of per-store data visibility without duplicating reports.

The Dataverse connector exposes a 'Create a record' action, letting a cloud flow insert a new row into a chosen table. It is a native, first-party action available in the flow designer's connector list, satisfying the question's requirement for a valid flow action.

A Power Automate flow with the Dataverse 'when a row is added' trigger fires on submission and can send the support team email. This is the supported, no-code mechanism for reacting to new rows created through Power Pages forms.

Power Apps apps can be published to Microsoft Teams as tabs or personal apps, letting users run canvas apps directly within Teams channels and chats. This satisfies the embedding requirement without leaving the Teams interface.

Power Pages Studio exposes theme and logo settings through a visual interface, applying changes across all content pages at once. Editing each page or the theme file manually would be slower and risk inconsistency, so Studio is the efficient route.

Views are saved queries defining which records and columns appear in a model-driven app's grid, and they are core metadata components alongside tables, forms, charts and dashboards. They shape the app's list presentation, satisfying the component requirement in the stem.

Topics in Microsoft Copilot Studio provide a visual authoring canvas where makers define trigger phrases that start a topic and add question nodes that branch based on the customer's response. This lets a non-developer build structured conversational flows such as greeting customers and answering store-hour questions without writing code.

The Image column type stores image data natively in Dataverse and renders it in canvas and model-driven forms, satisfying the requirement to persist an uploaded image. File columns hold any binary content but do not display inline, and text columns cannot store the binary payload.

The System Administrator security role provides full permissions to manage all components in the environment, including creating and modifying entities, managing security roles, and administering users. It is the highest level of access within an environment and meets the requirement to manage other users' security roles and all components.

An automated cloud flow triggers on an event such as a SharePoint item being added, satisfying the stem's requirement. It then evaluates the amount with a condition and posts an approval, updating the item status on approval.

The action posts a message to a Microsoft Teams channel, satisfying the requirement to notify the Marketing team's General channel. It uses the Teams connector's "Post message in a chat or channel" action, which targets a specific team and channel rather than a personal chat, delivering the flow's output directly to that shared workspace.

The Power Platform admin center includes a Capacity page under Analytics that displays detailed information about Dataverse storage, Power Platform requests, and other capacity metrics for the tenant. This is the central location to monitor and manage capacity consumption, making it the correct choice.

A push dataset lets an external service, such as Azure Stream Analytics, push rows into the Power BI service via the REST API, so tiles refresh as events arrive. This satisfies the real-time streaming constraint that import or DirectQuery cannot meet.

DLP policies can block specific connectors in production environments.

Power Pages delivers anonymous and authenticated external access, with native Dataverse integration for storing tickets and support for custom workflows. This satisfies the public-facing, registration and Dataverse requirements, unlike Power Apps portals or canvas apps, which are not designed for external website publishing.

Views define the columns, filtering, and sorting applied to lists of records in a model-driven app. Configuring the Case table view determines which columns agents see in the case list, so it addresses the requirement to define the columns shown in the list. Views and forms are complementary configuration elements for model-driven apps.

GatewayTimeout errors occur when an operation exceeds the connector's allowed response window. A slow-running SQL query against the on-premises data gateway surpasses that limit, causing the flow to fail before results return, which matches the reported error precisely.