Free PL-900 practice test: 30 questions with answers

Dataverse security roles control access to records by business unit, owner or hierarchy, which limits what each user sees. System Administrator access is too broad, shared logins remove accountability, and public tables expose data.

Environments isolate apps, flows and data, and they can be created for different departments or stages such as development and production. Naming alone does not separate data, laptops do not provide tenant isolation, and turning off Dataverse removes its features.

DLP policies in Power Platform group connectors and can block combinations that are not allowed, which enforces data controls. Themes and backgrounds are visual settings, and reminder emails are not enforcement.

Sharing with the User permission lets a colleague run the app without editing it, while co-owners can change it. Environment administrator and emailed source files grant more access than needed.

Security roles and DLP policies restrict what data and connectors each user can reach, and granting environment access only to people who need it limits exposure. Shared administrator accounts remove accountability, turning off auditing hides misuse, and plain-text passwords in flows expose credentials.

Microsoft Power Platform combines Power Apps, Power Automate, Power BI and Power Virtual Agents or Copilot Studio for low-code solutions. Teams is a collaboration tool, Project manages plans, and Visio draws diagrams.

Power Platform uses visual, low-code tools so that business users and developers can build solutions faster. It is not a compiled language, a hardware appliance or a social network.

Dataverse is the managed data platform for Power Platform, with tables, relationships and security roles. Forms collects responses, Stream hosted video, and Whiteboard is a canvas for collaboration.

Power Automate uses triggers and connectors to automate workflows across services without code. Power BI visualizes data, Power Pages builds websites, and Power Apps Studio builds apps rather than running automations.

Power Platform products share connectors and data through Dataverse, and apps and flows can use the same connectors. Products do not need separate tenants, the platform is designed for business makers as well as developers, and it is available in browsers and on mobile devices.

Canvas apps let makers design the screen layout freely for mobile or desktop, and they can work with connectors and offline data. A report is for analysis, a flow has no user interface, and Forms is for surveys.

Model-driven apps are generated from the Dataverse data model and provide forms, views and dashboards based on the tables. Canvas apps focus on screen layout, dashboards are for analysis, and flows automate processes.

A custom connector describes an external API so that Power Apps and flows can call it securely. A theme changes visuals, list views display data, and channel tabs embed content in Teams.

Model-driven apps are built from the data model, which provides forms and views automatically, while canvas apps give makers freedom over the screen layout. Canvas apps connect to many data sources, not just Dataverse, and model-driven apps also run on mobile devices.

Component libraries let makers create components once and reuse them across canvas apps. Manual copies drift over time, a Power BI dataset holds data for reports, and business process flows guide stages.

An automated cloud flow starts when an event such as a file creation occurs, so it reacts without manual action. Instant flows need a user to start them, scheduled flows run on a timer, and desktop flows automate local applications.

An instant flow with a manual trigger is started by the user on demand, including from the mobile app. Automated and scheduled flows start from events or timers, and business process flows guide stages rather than run on demand.

Desktop flows automate user interface actions on Windows applications, which is robotic process automation. Business rules validate data in Dataverse, the data gateway connects on-premises sources, and Pages templates build websites.

Automated flows react to events, and desktop flows automate the user interface of Windows applications through robotic process automation. Instant flows are user-started, scheduled flows run on a timer, and flows rely on connectors to reach other services.

A condition action evaluates an expression and runs different branches depending on the result. A schedule does not branch on data, the desktop recorder automates screens, and bookmarks belong to Power BI reports.

Power BI creates interactive reports and dashboards that refresh from data sources and can be shared in the browser. Excel desktop without sharing, Access and Publisher are not designed for interactive shared business reporting.

Workspaces are containers where teams create and share reports, dashboards and datasets with defined roles. Flows, tables and app screens are part of other Power Platform products.

The on-premises data gateway securely connects the Power BI service to data sources inside the network for scheduled refresh. Public IPs weaken security, emailed copies are manual, and canvas screens are not data connectors.

Power BI Desktop is the Windows application for creating reports and data models before publishing. Pages, Teams and the mobile flow app are not used to build reports.

Scheduled refresh in the Power BI service updates the dataset automatically at chosen times. Manual desktop refreshes need someone to act, desktop recorders automate screens, and printed copies do not refresh data.

Power Pages builds secure external websites that can use Dataverse data and authenticate external users. Power BI Desktop builds reports, desktop flows automate local UI actions, and Forms only collects answers.

Copilot Studio lets makers build conversational agents that use knowledge sources and connect to actions. Visio draws diagrams, and Project and Planner manage tasks and plans.

AI Builder and built-in AI features let makers add AI capabilities such as summarization and prediction to apps and flows. Disabling connectors, backups and static images do not add AI functions.

Copilot Studio builds agents that answer questions from knowledge sources and can be published to websites and channels. Power BI Desktop builds reports, desktop flows automate local tasks, and Lists tracks items.

AI Builder provides prebuilt models, including document processing for invoices, which can be used in apps and flows. Slicers, themes and relationships do not extract information from documents.