Microsoft Power Platform Fundamentals PL-900 (PL-900) — Questions 526–600

Conditional access applies only to interactive sign-ins, so a non-interactive service account cannot satisfy MFA prompts. Excluding it from the policy preserves the account's workload authentication while the remaining environments stay compliant with the security team's mandate.

A Power Automate cloud flow can call the REST API, manage the API key securely, and return the loyalty balance. The copilot topic then uses a Call an action node to invoke the flow and display the result. This is the supported no-code integration pattern for custom APIs in Copilot Studio topics, satisfying the lookup and response requirement.

Setting the retry policy on the Dataverse action to a fixed interval with a count of 3 ensures the action retries up to three times if it fails. Then, by adding a 'Configure run after' on a subsequent action (e.g., send error notification) to run only if the Dataverse action fails, the flow can send an error notification after retries are exhausted. This combination meets the requirement precisely.

Power Virtual Agents is a no-code chatbot development tool that uses natural language understanding to interact with users. It can be deployed on websites and other channels, and it supports escalation to human agents via integration with Power Automate or Dynamics 365. This directly meets the requirement for a customer-facing chatbot.

Solutions enable ALM with validation at each stage.

Row-level security filters data by the signed-in user's identity, so each store manager sees only rows matching their own store. This directly satisfies the requirement to restrict visibility per store without duplicating datasets or building separate reports.

Power BI connects to multiple data sources and refreshes visuals automatically, giving the sales team a single real-time dashboard for trend analysis. Its aggregation and visualisation engine satisfies the cross-source, live-data constraint that Power Apps or Power Automate cannot.

Power Apps delivers the canvas app that field technicians use to capture maintenance reports, with offline capability through the mobile player caching data locally and syncing to Dataverse once connectivity returns. This directly satisfies the stem's offline logging and later synchronisation requirement, unlike components lacking a mobile data-entry surface.

The Pen input control is designed for freehand drawing and signature capture on touch devices. It exposes the Image property, which returns the drawn strokes as an image that can be written to a Dataverse image column on the work order record. This directly satisfies the requirement of capturing and storing signatures.

Microsoft Copilot Studio supports knowledge sources, including SharePoint, that ground generative answers in an organization's content. Pointing the copilot at the policy site means answers are drawn from those documents and reflect edits as the source is reindexed, satisfying both the grounding and the automatic currency requirement without manual retraining.

Power BI connects to multiple data sources, models donations, and schedules refreshed reports distributed by email subscription to stakeholders. This satisfies the weekly, multi-source reporting requirement, whereas Power Apps and Power Automate do not deliver analytical reporting.

Business rules run server-side on the table, so the discount validation applies across every form, view and API write, not just one app. This enforces the 50% limit consistently at the data layer, satisfying the model-driven app's requirement.

Core component for chatbots.

Canvas apps give full control over the layout and formulas, so the analyst can add date pickers and a calculated label using DateDiff to derive the number of days between start and end dates, satisfying the automatic calculation requirement.

A Power Automate flow registered on the Dataverse lead-creation message runs automatically when a lead record is created, letting it create and assign a task to the sales team, which satisfies the required automated trigger.

Both topics share the trigger phrase 'refund policy', causing ambiguous matching that routes users to Shipping Information. Deleting that phrase from the newer topic leaves Refund Policy as the sole match, requiring no threshold or flow changes.

Canvas apps provide a drag-and-drop designer with Excel-like formulas, so volunteers' hour and expense logging needs minimal coding. This directly satisfies the stem's ease-of-build and low-code constraints, unlike model-driven apps, which require Dataverse data modelling and offer less layout freedom.

The Start with data wizard in Power Apps Studio automatically generates a three-screen canvas app (browse, detail, and edit/create) based on a selected data source such as a SharePoint list. It creates the necessary forms and galleries, allowing a non-developer to quickly produce a working app for submitting expense reports.

Canvas apps store data locally via the offline profile, letting the Camera and Signature controls capture images and signatures without connectivity. Dataverse queues these records and syncs them automatically once the device reconnects, satisfying the offline capture constraint for text, images, and signatures.

Model-driven apps are built on Microsoft Dataverse and automatically generate UI components such as forms, views, and dashboards from the underlying data model. They honor Dataverse security roles and business rules without custom code, which matches the requirement for field representatives to look up customers, view orders, and update accounts with minimal coding effort.

Even with a gateway installed, the flow needs a connection that specifies the gateway and the SQL Server credentials. The SQL Server connector's connection must be associated with the gateway so that Power Automate routes queries through it. Without this connection configuration, the flow cannot authenticate to the database, making this component necessary.

This Excel Online (Business) trigger monitors a table in a workbook stored in OneDrive for Business or SharePoint. It fires when a row in the specified table is added, modified, or deleted. Since the shipment status is updated in an existing row, this trigger detects the change and can pass the updated row values to subsequent actions, enabling the conditional email notification.

This trigger is specifically designed to fire when a new task is added to a Planner plan. It provides details about the task, such as its title and assignee, which can be used in the subsequent Teams action. It directly matches the event the user wants to monitor, making it the correct choice for this scenario.

Power Automate flows trigger on Dataverse events, such as a support ticket's status changing to Resolved, then execute actions automatically — here, creating a follow-up task record. This satisfies the stem's requirement to automate task creation without user intervention, unlike manual configuration or static business rules.

A radio control presents mutually exclusive options, letting managers select a single decision such as approve or reject. This satisfies the requirement to capture one definitive choice per request, preventing contradictory selections that checkboxes or text inputs would allow.

Setting the list component's Sort Column to the logical name 'cr5f3_total' with descending direction satisfies the stem's ordering constraint directly, since Power Pages lists sort server-side using the table's column logical name rather than display name. This returns orders highest total first without client-side scripting or custom views.

Idempotency is achieved by checking whether each expense's unique identifier was already processed before performing the side-effecting HTTP call. Recording processed IDs in a Dataverse table and skipping matches ensures retries from the trigger or loop do not produce duplicates, and missed items can be replayed safely.

Canvas apps render pixel-perfect interfaces that can be published as a Teams tab or personal app, satisfying the embedding requirement directly. Unlike model-driven apps, which depend on Dataverse and follow a fixed, form-based layout, canvas apps give the designer full control over the UI, making them the appropriate choice for a Teams-embedded Power Apps experience.

Copilot in Power Apps generates a working app from a natural-language description, scaffolding screens, controls and data connections. This satisfies the stem's capability question by naming a genuine Copilot feature rather than a manual authoring task.

Trigger phrases define the utterances that cause a topic to be invoked. By adding trigger phrases for maintenance requests, the copilot can recognize when a user wants that topic and route the conversation accordingly. This is the standard way to connect user intent to the correct topic in Copilot Studio without code.

Form Processing is the AI Builder model type trained to extract structured fields such as invoice number and total from PDFs. Pairing it with the Dataverse 'Create a new row' action persists those extracted values, meeting the requirement to store extracted text in Dataverse.

Building a custom form that writes to a Dataverse 'Deletion Requests' table, then triggering a Power Automate flow for admin notification and post-approval deletion, satisfies the manual review constraint. Dataverse integrates natively with Power Pages, so no custom authentication or external storage is needed, keeping effort minimal.

Power Automate cloud flows can be triggered by Dataverse events such as when a record is updated. You can configure the flow to check if the case was escalated, then send an email and update the priority. This requires no code and integrates directly with Dataverse, making it the correct solution for the scenario.

Copilot Studio advances a conversation only when it extracts a value for the expected entity. If the order number entity is not recognised, the slot remains unfilled, so the dialogue stalls despite the customer supplying the requested information.

Exponential backoff retry policies directly address HTTP 429 throttling by spacing repeated attempts progressively further apart, letting the service's request limit reset before the next call. This satisfies the intermittent daily-flow failure constraint, since transient rate limiting resolves without manual intervention or flow redesign.

The Item property on an Edit form or Display form control determines which record the form displays. By setting this property to the gallery's Selected property, the form dynamically updates to show the details of whichever project the user selects. This is the standard way to link a gallery and a form in a canvas app so that selection drives the form content.

Creating an item in SharePoint or Dataverse fires the same connector trigger Flow1 listens on, regardless of which flow performed the write. Flow2's first action therefore satisfies Flow1's trigger condition, so Flow1 runs and sends its email, then updates the item — the cascade the stem asks about.

Power Automate is built to automate repetitive tasks by connecting services with triggers and actions. It can trigger when a new web form response arrives, write the lead to Excel or another data store, and send a confirmation email automatically. This directly removes the manual copying and emailing steps described.

Power Automate builds event-driven cloud flows that trigger on purchase order creation, route an approval request by email, and branch on the manager's approve or reject response — satisfying the requirement for an emailed link plus automated decision handling without custom code.

An on-premises data gateway brokers the refresh connection between the Power BI service and the internal SQL Server, which is unreachable directly from the cloud; assigning it to the dataset lets the 2:00 AM refresh succeed.

Canvas apps let makers place controls such as the Camera control on a blank canvas, bind them to Dataverse as a data source, and use formulas to write the captured image and work order number. This supports fast drag-and-drop development with no server-side code, matching the technician's needs.

The 'Apply to each' action has a concurrency control setting that allows multiple iterations to run simultaneously. By turning it on and setting a degree of parallelism, the flow can process several line items at once instead of one at a time, which reduces total duration when iterations are independent. This is the intended feature for speeding up loops.

The Recurrence trigger emits only timestamp-based outputs such as start time, so no 'name' token exists at runtime. Referencing that dynamic content therefore resolves to empty on scheduled runs, while the manual trigger supplies it.

A tenant-level DLP policy in the Power Platform admin center classifies connectors into business, non-business and blocked groups, preventing flows from combining SharePoint and Dataverse data with external connectors, which directly enforces the no-data-leaving constraint.

Service principals authenticate as applications, so they need SharePoint application permissions such as Sites.FullControl.All granted with tenant admin consent. Missing permissions or absent consent produce intermittent 403 Forbidden responses when the flow calls the SharePoint API.

Dataverse enforces optimistic concurrency and record-level locking. If another process, such as a synchronous plugin or a concurrent flow run, holds a lock on the invoice record, the update step will fail with a lock error. This matches the symptom exactly. The resolution is to add retry logic or ensure the conflicting process releases the lock before the update.

Model-driven apps are built on Dataverse tables, and the maker must create the custom table for cases, then create a model-driven app that includes forms, views, and a dashboard. These components are defined within the app designer or solution explorer to provide the required user interface and data management.

Power Automate's SharePoint connector exposes the Create item action, which writes a new record to a specified list. This satisfies the stem directly: the flow performs the write through the connector's authenticated API call, with no code required.

Power Automate is the workflow engine that enforces the manager approval gate before submission. Its approval connector pauses the flow until the approver responds, satisfying the sequential authorisation constraint that a pure data store or dashboard cannot enforce.

Managed solutions package components with environment variables for environment-specific values, and Power Platform deployment pipelines promote them through development, test and production with configurable approval gates. This satisfies the requirement for staged promotion with approvals across multiple environments.

Microsoft 365 Outlook is a cloud service, so canvas apps connect to it through the built-in Office 365 Outlook connector using standard authentication. No on-premises data gateway is required because the data never resides behind a corporate network boundary.

Power Apps caches data to improve performance, leading to delays in seeing updates.

This is a core function of the Power Platform admin center.

Tenant-wide storage, database, file and add-on consumption across every environment is aggregated in the Power Platform admin center's Capacity page, which reports entitlement versus actual usage per environment. Individual environment settings and the maker portal show only scoped or per-app detail.

Cloud flows run server-side on triggers and schedules, so a SharePoint item event can initiate approval requests, route them to approvers, and record outcomes without any user's device being active. This satisfies the requirement for unattended, automated approval handling.

Power BI is the cloud-hosted analytics service that connects to multiple data sources, models the data, and publishes interactive dashboards with self-service authoring. This satisfies the cloud-based, minimal-IT-support constraints for analysing sales data and building dashboards.

Functions are built-in operations in Power Fx, the canvas app formula language, performing tasks such as text manipulation, date arithmetic and conditional logic. They satisfy the stem's requirement for a formula-language component, alongside operators and identifiers, by providing the callable expressions that formulas evaluate.

Separate development, test, and production environments isolate unmanaged customisations from live business data, satisfying the stem's large-enterprise constraint of controlled release governance. Changes are validated in test before promotion, preventing faulty solutions from disrupting production apps and flows, and aligning with Microsoft Entra ID-governed environment security boundaries.

Power Apps provides a low-code designer where makers build custom business apps by dragging controls and connecting data sources, requiring minimal traditional programming. This is a core platform capability, satisfying the question's requirement for a genuine Power Apps feature.

Canvas apps can be embedded as a tab in a Teams channel, allowing users to interact with the app directly within the channel. This is the recommended approach for embedding a custom app into a channel.

The 'Start and wait for an approval' action sends an approval request through Outlook or Teams and suspends the flow run until the approver responds. This is a standard, supported action in Power Automate cloud flows and directly fits the scenario, where processing should continue only after the expense report is approved or rejected.

Canvas apps give the maker full control over layout and behaviour through a drag-and-drop designer and Power Fx formulas, so a business user can assemble screens and logic without writing code. This satisfies the no-code requirement, unlike model-driven apps, which are generated from Dataverse metadata.

Microsoft Entra ID authentication with domain restrictions enforces tenant-based sign-in, so only users from the specified domains authenticate. This satisfies the requirement that external users be authenticated and limited to particular domains, which anonymous or local portal accounts cannot enforce.

Each field on a model-driven form triggers its own metadata retrieval and control rendering, so removing unused fields and columns reduces the payload Dataverse must assemble, directly improving case record load times without disabling business rules.

Checking run history exposes each execution's trigger inputs, action outputs and error codes, revealing whether the hourly recurrence fired but a downstream notification action failed. This directly satisfies the stem's diagnostic-first constraint, since it identifies the failing step before any rebuild or permission change is attempted.

The Omnichannel engagement hub must have a workstream and queue configured to accept and route incoming conversations. These components define the skills, capacity, and assignment rules that determine which human agent receives the escalated chat. Without a receiving queue, the handoff from Copilot Studio has nowhere to land, so the conversation cannot reach a live agent and the escalation fails.

Separate environments give each audience its own Dataverse instance, security roles and data boundaries, so external customers cannot access internal employee records. This isolation satisfies the requirement to keep customer data segregated from internal data.

The Parse JSON action validates incoming payloads against the schema's required fields, so a product object lacking 'quantity' fails validation. Removing 'quantity' from the required array makes the field optional, allowing the flow to process payloads where it is absent.

The Analytics area in the Power Platform admin center provides ready-made usage reports per environment, including which apps were opened, by how many users, and which users were inactive, with no paid add-on required. It directly answers the access and inactivity question for the production environment.

'For a selected file' is a manual, user-invoked trigger available in SharePoint and OneDrive, prompting the user to pick a file before the flow runs. It is a legitimate trigger type distinct from automated and scheduled triggers.

Row-level security in Dataverse filters records per user, so technicians see only their own and their region's rows, while role-based privileges grant create, read and update but withhold delete. Individual accounts replace the shared elevated service account, directly satisfying least privilege without breaking technician workflows.

Business rules in model-driven apps run client-side and server-side against Dataverse tables, enforcing field validation, required values, and conditional logic without custom code. This satisfies the stem's validation requirement directly, unlike canvas-only features. They apply consistently across forms and views, making them a core model-driven capability.

Configuring authentication restricts the chatbot to signed-in organisational users, since only internal identities can obtain valid credentials. This satisfies the requirement that the bot be unavailable to external customers, who cannot authenticate against the tenant.

Microsoft Purview retention policies govern audit records independently of their original source, so applying one to Power Platform audit logs keeps every captured event for the mandated seven years. Sentinel handles detection, not long-term retention, so it cannot satisfy the compliance requirement alone.

Notifying the on-call engineer in Microsoft Teams requires the Teams connector's messaging action, which can post an adaptive card or message to a channel or chat. Without this action the flow cannot deliver the notification, so it is one of the two required components for the described scenario.