Microsoft Power Platform Fundamentals PL-900 (PL-900) — Questions 376–450

Data Loss Prevention (DLP) policies in Power Platform define which connectors are Business, Non-Business, or Blocked, and prevent flows from combining connectors across groups — thereby stopping sensitive data from flowing to unauthorized external services. This is the purpose-built governance control for restricting connector usage across flows and apps.

Power BI datasets connected to SharePoint lists require a scheduled refresh to update the dashboard with the latest data from the list. If the refresh is not configured or fails, the dashboard will display stale data. The administrator should first check the scheduled refresh settings in the Power BI service to ensure it is enabled and running successfully.

The default backup frequency for Dataverse environments is every 24 hours, which ensures automatic system backups are created daily without requiring manual configuration. This policy applies to all environments, including trial and production, unless a custom backup schedule is explicitly set by an administrator.

The 'When an item is created - SharePoint' trigger is the correct choice because it initiates the flow automatically whenever a new item (in this case, a new employee record) is added to the specified SharePoint list. This event-driven trigger eliminates the need for manual intervention, making it ideal for automating the welcome email process immediately upon creation.

Power Automate is the correct choice because it is designed to create automated workflows that trigger on events in Dataverse, such as the creation of a new HR record. It can then perform actions like sending a welcome email via connectors (e.g., Office 365 Outlook) without manual intervention.

The flow is configured to run on a recurring schedule (e.g., every hour), not as an instant trigger on record creation. When a record is created at the exact boundary between two scheduled runs, it may not be captured by the previous run (which already completed) and may not yet exist when the next run begins, especially if the flow uses a filter query based on a timestamp. This is a classic limitation of scheduled polling compared to event-driven triggers like 'When a row is added, modified, or deleted' in Dataverse.

Power Pages (option A) is the correct solution because it enables external-facing websites that can be accessed by anonymous users without requiring a Microsoft account or license. Canvas apps and model-driven apps require authenticated users with appropriate licenses, and Power Automate is an automation service, not a portal for external submissions.

Automating a Teams message from a new Dataverse record requires an event-based Dataverse trigger. The 'When a row is added, modified or deleted' trigger with the Added change type listens to the CustomerOrders table and starts the flow the moment a record is inserted, after which a Teams 'Post message' action can publish to the channel without any code.

Azure AD B2C provides a 'Password reset' user flow that allows users to reset their own passwords. Options B, C, and D are incorrect: a custom identity provider may not support password reset natively and is unnecessary; Dataverse is a data storage layer and does not handle authentication; Microsoft Entra ID self-service password reset is intended for organizational accounts, not for external B2C users.

SharePoint is classified as 'Business' in the DLP policy because it is a Microsoft-owned enterprise service that supports data loss prevention (DLP) actions like blocking, monitoring, or restricting data flow. The exhibit shows SharePoint under the 'Business' data group, meaning it is allowed for business use without triggering policy violations. In contrast, Outlook, Twitter, and Facebook are placed in the 'Non-Business' group, which blocks their connectors from being used in apps and flows within this environment.

AI Builder's invoice processing model is a prebuilt AI capability in Power Platform specifically designed to extract structured data (vendor, total, line items) from invoices using OCR plus machine learning. It integrates directly with Power Apps and Power Automate and requires no custom model training. This is the purpose-built solution for the stated requirement.

Topic matching in Copilot Studio relies on trigger phrases that train the natural language model for each topic. When users phrase requests differently than the authored examples, recognition suffers, so adding realistic variations such as 'enroll in a class' and 'sign me up for a course' is the direct fix. Recreating topics, escalating everything, or changing locale does not improve matching.

Environment-level DLP policies allow administrators to apply connector restrictions to specific environments, such as blocking the 'Twitter' connector only in 'Production' while leaving it available in other environments. This granular control is essential for enforcing governance without affecting development or testing environments.

Dataverse is the only option that natively supports complex relationships, business rules, and security at the data level within the Power Platform. It is designed for scenarios requiring robust data modeling and governance, unlike SharePoint lists or Excel, which are better for simpler data storage.

Microsoft Copilot Studio's Topics canvas is the no-code authoring surface for conversation flow, using trigger phrases and nodes such as messages, questions, and conditions. Building a public-facing copilot that greets visitors and answers shipping questions is accomplished by creating topics, not by connectors, flows, or tables, which are supporting components rather than the dialog authoring mechanism.

Creating a custom connector with API key authentication is the recommended approach because it securely stores the API key in the connector's authentication configuration, and the connector can be reused across apps and flows. This avoids exposing the key in the app's formulas or client-side code.

Power BI is the correct choice because it is designed for data visualization and business intelligence, enabling real-time dashboards with drill-through capabilities. It can connect directly to an ERP system via connectors or DirectQuery to display live sales data, and managers can use the drill-down feature to navigate from summary metrics to individual transaction details.

Managed solutions allow you to package common components (entities, workflows) and deploy them to multiple environments, ensuring consistency while maintaining departmental isolation. Each department gets its own environment for independent chatbot management, and the shared components are installed via managed solutions that cannot be modified, preserving the common baseline.

Canvas apps in Power Apps are designed for rapid, low-code development with drag-and-drop UI and direct Dataverse connectivity, making them the fastest path to a mobile-friendly work order app. They can be published to Power Apps mobile and run on iOS and Android without native development.

Copilot Studio (formerly Power Virtual Agents) is the dedicated Power Platform component for creating and deploying chatbots using a no-code graphical interface. It allows you to design conversational topics, trigger flows, and publish the bot to channels like Microsoft Teams or websites without writing code. AI Builder provides AI models that can be integrated into a chatbot solution but cannot create or deploy a standalone chatbot.

Capturing user input and reusing it later requires a Question node configured to save the response into a variable. This is a core no-code authoring feature in Copilot Studio, allowing the copilot to remember the email address and use it in subsequent messages or conditions. Other features like redirects, system topics, or entity extraction do not provide the ask-and-store behavior needed here.

A DLP policy scoped to 'All environments' applies its connector classification across every Power Platform environment in the tenant. When connectors are placed in the 'Blocked' group, any app or flow using those connectors is prevented from running in any environment, including the default one. The scope setting directly determines where the policy's restrictions take effect.

Data Loss Prevention policies can be scoped to individual environments, allowing the administrator to block the custom connector in production while a separate policy permits it in the sandbox. This enforces the security team's review requirement without eliminating prototyping. A tenant-wide block, role removal, and tenant-level connector consent do not provide the environment-specific control needed, and some do not affect the already deployed app.

Power Automate provides the connectors and logic needed to trigger on a SharePoint item, branch by department, and send approval requests that approvers can act on directly from email. It is the Power Platform service purpose-built for workflow automation with minimal development. The other services handle app creation, reporting, or chat, none of which automate the approval routing described.

Canvas apps are the correct choice because they support offline capability by leveraging the Power Apps offline sync feature, which allows data to be cached locally on the device and synchronized with the data source (e.g., Dataverse or SharePoint) when connectivity is restored. This makes them ideal for mobile scenarios like store managers approving discount requests in areas with intermittent connectivity.

A daily Recurrence trigger with interval 1 fires once every day at the configured time. Setting the trigger's Time zone aligns that firing with local time, and a Condition action can filter out Saturday and Sunday. Together these settings deliver a weekday-only 7:00 AM run without external scheduling tools, which directly meets the stated requirement.

Power Apps is the low-code development platform in the Microsoft Power Platform, enabling users to create custom apps with a drag-and-drop interface. It supports mobile scenarios, camera controls, and integration with various data sources, making it ideal for field representatives to log visits and capture photos. The other components are not designed for building custom data entry apps.

AI Builder provides prebuilt models that can extract text and data from scanned invoices without requiring custom machine learning expertise. This capability integrates directly into Power Automate and Power Apps, enabling automated processing of invoice data within the Power Platform.

Large, unoptimized images increase the payload size that must be downloaded to the mobile device, directly impacting load times, especially over cellular networks. Power Apps loads all resources, including images, when the app starts, so oversized images cause significant delays. Optimizing images (e.g., compressing, resizing, using modern formats like WebP) reduces bandwidth usage and speeds up app loading.

The 'GatewayTimeout' error indicates that the flow successfully reached the on-premises data gateway but the gateway did not respond within the expected time frame. This typically occurs when the gateway service is not running, the machine hosting the gateway is offline, or network connectivity between the gateway and the SQL Server is broken. Incorrect credentials or missing tables would produce different errors (e.g., 'Login failed' or 'Invalid object name').

Power Automate is the correct tool because it is designed to create automated workflows that trigger actions based on events, such as a new item being added to a SharePoint list. In this scenario, a Power Automate flow can be configured to run automatically when a donation is recorded, then send a thank-you email via an email connector (e.g., Outlook or SMTP). This directly addresses the need for process automation without manual intervention.

Power Apps is the low-code application development service in the Microsoft Power Platform. It enables non-developers to assemble mobile and web apps with drag-and-drop controls, connect to data sources, and include features like signature capture and offline use. The other services focus on automation, analytics, or chatbots, none of which deliver an interactive driver-facing app.

A scheduled cloud flow is designed to run on a recurring schedule, such as every hour. It is triggered by a time-based recurrence, not by an event. This matches the requirement to check a SharePoint list hourly and send reminder emails.

When a flow does not trigger on file creation, the most common cause is a misconfigured trigger — the wrong site address, library name, or folder path selected in the 'When a file is created' trigger. Verifying the trigger configuration is the fastest first diagnostic step because it directly controls whether the flow fires. Other checks (licensing, environment state, target library) are valid but less likely to be the root cause of a non-firing trigger.

Managed solutions with application lifecycle management (ALM) ensure that all Power Platform solutions in production environments are tracked and changes are approved by enforcing version control, solution layering, and controlled deployment through environments. This approach uses solution components and environment segmentation to prevent unapproved modifications and maintain an audit trail.

Model-driven apps require first setting up Dataverse tables, then designing forms/views, then building the app with sitemap, and finally publishing with security roles.

It uses Power BI Row-Level Security (RLS) to restrict store managers to only their store's data while allowing regional managers to see aggregated data via a paginated report. The scheduled Power Automate flow automates the weekly email delivery, meeting both security and automation requirements without manual intervention.

To delegate environment creation and management without full admin rights, the administrator should assign the Environment Creator role at the tenant level and Environment Admin roles for the specific environments. This combination provides the necessary permissions while adhering to least privilege, as the user cannot manage unrelated environments or tenant-wide policies.

Dataverse mobile offline sync is the built-in Power Apps capability that lets canvas and model-driven apps download a filtered subset of Dataverse tables to the device, so field technicians can read and write data without connectivity. When the device reconnects, queued changes are synchronized back to Dataverse automatically, resolving conflicts server-side. This directly satisfies the offline-first requirement without custom code.

Business rules in Power Apps that target Dataverse tables are defined in the table's Business Rules settings within the Power Apps maker portal. These rules run server-side on Dataverse, apply across all apps (canvas, model-driven, Power Pages), and can set field values, show errors, or lock fields without requiring code. This is the correct location for a rule that automatically sets Priority to 'High' for VIP customers.

Microsoft Copilot Studio provides a no-code graphical authoring canvas where makers create topics, define trigger phrases, and add message nodes to build conversational experiences. For a public website copilot answering common questions, this is the fastest and most appropriate approach. The other options involve development work, background automation, or app interfaces that do not deliver a conversational copilot.

The 429 error indicates the API is rate-limiting requests. Configuring a retry policy with exponential backoff allows the flow to automatically retry after increasing delays, reducing server load and respecting the API's rate limits. This is the standard best practice for handling transient throttling errors in Power Automate.

Stale or incorrect generative answers often trace to the knowledge source not reflecting recent changes. Confirming the correct SharePoint site is connected and refreshing or reindexing the content is the appropriate first step. Switching to authored topics, changing authentication, or adding trigger phrases does not address outdated knowledge retrieval.

Power Pages integrates natively with Dataverse, and the 'List and Form' template provides prebuilt components for displaying records and capturing submissions without custom code. Creating a Dataverse table for appointments and using the template gives a low-code, integrated booking experience with data stored in the platform's native data store. This satisfies the no-custom-database and Microsoft 365 integration requirements.

Power Automate is the service within the Microsoft Power Platform specifically built for automating workflows across applications and services. It provides hundreds of connectors, including Outlook, SharePoint, and Dynamics 365, enabling the logistics company to digitize the expense approval process without writing code. The other components serve different purposes: Power Apps for app development, Power BI for analytics, and Power Virtual Agents for chatbots.

Power Automate is the Power Platform component specifically designed for workflow automation and approvals. It provides built-in approval actions and templates that allow you to define multi-step approval processes, send approval requests, and track responses. Power Apps is for building the user interface, Power BI for analytics, and Power Virtual Agents for chatbots, none of which natively handle approval workflows.

The Conversation Start topic is the system topic that fires at the beginning of every session, making it the correct place to present entry-point buttons. A Suggested Action added there renders clickable buttons tied to topic trigger phrases, so employees can either type 'book a meeting room' or click 'Room booking'. Trigger phrases, entities, and external flows do not produce an automatic button in the chat canvas.

Administrators can block specific connectors from being used in Power Automate flows as part of a DLP policy, preventing data from being shared with unauthorized services. Option C is correct because DLP policies can be scoped to a specific environment, allowing granular control over connector usage within that environment. This enables the administrator to enforce data protection rules tailored to different business contexts.

DLP policies in Microsoft Power Platform can be configured at the tenant level to apply across all environments. By creating a tenant-level DLP policy and blocking the specific third-party connector, the administrator ensures consistent enforcement without needing to manage individual environment policies. This approach centralizes control and prevents the connector from being used in any environment.

Power Apps builds custom apps, Power Automate automates workflows, Power BI analyzes data, and Power Virtual Agents creates chatbots. Common confusions include swapping these definitions.

The correct sequence for configuring a Power Virtual Agents chatbot is: first create the bot, then define topics to handle user intents, add nodes to each topic to define the conversation flow, test the bot in the test pane to verify behavior, and finally publish the bot to make it available to users. Publishing before testing risks deploying unresolved issues.

Power Apps is the appropriate component because it provides a low-code app designer for tablet-friendly interfaces and integrates with Dataverse, which supplies governed storage and role-based security. Supervisors can report issues through the app, and authorized staff can be granted access through security roles. Power BI, Power Pages, and Power Automate serve analytics, external websites, and automation respectively, not internal app creation.

Meeting the requirements needs two distinct capabilities: a handoff mechanism that routes the conversation to a live agent in Dynamics 365 Customer Service, and a question node that captures and stores the customer's email in a variable. Together they ensure unresolved chats reach an agent with the email already collected. Sentiment analysis, channel publishing, and FAQ knowledge sources do not provide escalation or email capture.

To restrict connector usage and prevent data sharing between certain connectors, the administrator must create a DLP policy that defines connector groups and blocks cross-group usage, and then apply that policy to the environment. These two actions together enforce the desired governance. Other actions, such as assigning roles or setting region, do not address connector-level restrictions or data flow control.

Power Pages charts built from Dataverse views are rendered dynamically at page load and reflect the current data in the underlying view — no caching layer or scheduled refresh is required. Because the chart queries Dataverse each time the page is rendered, changes to sales data appear automatically on the next page load without any additional configuration.

In Power Pages, web roles grant table permissions that are explicit and granular. The Partner role has only Read permission on the Proposal table, so a user with that role cannot create (Write) a new Proposal record. Power Pages enforces table-level CRUD permissions, and lacking Write on Proposal results in access denial for the create operation.