Scenario practice questions

A company wants to integrate Power Automate with Microsoft Teams so that when a new task is assigned in Planner, a message is posted in a Teams channel. Which connector should be used?

Trap 1: Outlook.com

Outlook.com handles personal mailbox mail, not Planner task events or Teams channel posts, so it cannot detect the assignment or deliver the message. It is tempting because it sends notifications, but Office 365 Outlook or the Planner and Teams connectors are needed here.

Trap 2: SharePoint

SharePoint connectors read and write lists, libraries and sites; they expose no Planner task triggers or Teams channel message actions. It is tempting as another Microsoft 365 workload connector, but the stem requires Planner events feeding Teams posts, which SharePoint cannot supply.

Trap 3: Office 365 Outlook

Office 365 Outlook sends and receives mail and calendar items; it cannot watch Planner assignments or post into a Teams channel. It is tempting because email notifications resemble channel messages, but the Planner and Teams connectors are required for this integration.

A
Outlook.com
Why it fails: Outlook.com handles personal mailbox mail, not Planner task events or Teams channel posts, so it cannot detect the assignment or deliver the message. It is tempting because it sends notifications, but Office 365 Outlook or the Planner and Teams connectors are needed here.
B
SharePoint
Why it fails: SharePoint connectors read and write lists, libraries and sites; they expose no Planner task triggers or Teams channel message actions. It is tempting as another Microsoft 365 workload connector, but the stem requires Planner events feeding Teams posts, which SharePoint cannot supply.
C
Office 365 Outlook
Why it fails: Office 365 Outlook sends and receives mail and calendar items; it cannot watch Planner assignments or post into a Teams channel. It is tempting because email notifications resemble channel messages, but the Planner and Teams connectors are required for this integration.
D
Microsoft Teams
The Microsoft Teams connector supplies the 'Post message in a chat or channel' action, which publishes to the target channel. Planner's own connector detects the task assignment, but Teams is the connector that performs the required channel post.

Question 2mediummultiple choice

An organization uses Power Automate flows that connect to Microsoft Dataverse. The flows need to run under a service account with specific permissions. What is the best practice to manage the connection?

Trap 1: Use the flow owner's credentials and share the flow with the…

Running under the flow owner's credentials means the service account's Dataverse permissions are never applied, and sharing grants only run-only access, not identity substitution. It tempts because sharing is how makers delegate flows, but that scenario involves personal delegation, not service-account execution.

Trap 2: Create a service account connection type in the Power Platform…

The Power Platform admin centre has no service account connection type; connections are created per user identity, so this cannot exist. It tempts administrators wanting centralised credential governance, which is instead achieved by creating the connection while signed in as the service account itself.

Trap 3: Hardcode the service account credentials in the flow

Embedding credentials in the flow definition exposes secrets in plain text to anyone with edit access and breaks when the password rotates. It tempts as a quick way to force a fixed identity, but the correct approach is creating the connection signed in as the service account, so no secret is stored.

A
Use the flow owner's credentials and share the flow with the service account
Why it fails: Running under the flow owner's credentials means the service account's Dataverse permissions are never applied, and sharing grants only run-only access, not identity substitution. It tempts because sharing is how makers delegate flows, but that scenario involves personal delegation, not service-account execution.
B
Create a connection reference that uses the service account's connection
A connection reference centralises the Dataverse connection so flows reference it rather than embedding credentials, letting the service account's connection be managed and updated in one place. This satisfies the requirement to run flows under a service account with specific permissions.
C
Create a service account connection type in the Power Platform admin center
Why it fails: The Power Platform admin centre has no service account connection type; connections are created per user identity, so this cannot exist. It tempts administrators wanting centralised credential governance, which is instead achieved by creating the connection while signed in as the service account itself.
D
Hardcode the service account credentials in the flow
Why it fails: Embedding credentials in the flow definition exposes secrets in plain text to anyone with edit access and breaks when the password rotates. It tempts as a quick way to force a fixed identity, but the correct approach is creating the connection signed in as the service account, so no secret is stored.

Question 3hardmulti select

Which THREE of the following are capabilities of AI Builder within Power Platform? (Select three.)

Trap 1: Replacing Azure Machine Learning

AI Builder supplements Power Platform with prebuilt and customisable models; it does not replace Azure Machine Learning, which remains Microsoft's platform for full model development, training and MLOps. It is tempting because both consume data and produce predictions, but they occupy different layers rather than substituting for one another.

Trap 2: Building custom machine learning models from scratch

AI Builder provides prebuilt and customisable models trained on your data through a guided interface, not from-scratch machine learning engineering. It is tempting because custom model training exists in the platform, but that belongs to Azure Machine Learning, which offers full algorithm and framework control.

A
Sentiment analysis
AI Builder provides prebuilt sentiment analysis, evaluating text and returning positive, negative, neutral, or mixed scores. This satisfies the question's requirement for a genuine AI Builder capability, unlike non-AI Power Platform features such as connectors or standard flow actions.
B
Replacing Azure Machine Learning
Why it fails: AI Builder supplements Power Platform with prebuilt and customisable models; it does not replace Azure Machine Learning, which remains Microsoft's platform for full model development, training and MLOps. It is tempting because both consume data and produce predictions, but they occupy different layers rather than substituting for one another.
C
Object detection in images
AI Builder's object detection model identifies and counts multiple object types within images, returning bounding boxes and confidence scores. This satisfies the requirement for a genuine AI Builder capability, distinguishing it from text-based models such as sentiment analysis or category classification.
D
Form processing
AI Builder form processing extracts structured field values from documents using trained document layouts, returning key-value pairs. This satisfies the requirement for a genuine AI Builder capability, distinguishing it from object detection, which locates items in images rather than reading document fields.
E
Building custom machine learning models from scratch
Why it fails: AI Builder provides prebuilt and customisable models trained on your data through a guided interface, not from-scratch machine learning engineering. It is tempting because custom model training exists in the platform, but that belongs to Azure Machine Learning, which offers full algorithm and framework control.

Question 4mediummultiple choice

A retail company wants to reduce the time store managers spend on manual inventory reporting. Currently, managers use paper forms and email to submit daily stock counts, which then need to be manually entered into a central system. This process is error-prone and delays replenishment. The company wants a solution that automates data entry, provides real-time dashboards, and allows managers to submit reports from their phones without installing any software on the phones. Which combination of Microsoft Power Platform tools should the company use?

Trap 1: Power Automate only

Power Automate moves and triggers data between services but offers no user interface for managers to submit counts and no dashboards, so the paper-to-system gap persists. It is tempting because automation of data entry is the stated pain point, and it would be correct if a capture app and reporting layer already existed.

Trap 2: Power Apps only

Power Apps delivers the mobile browser-based entry form, but it provides no automated flow to write submissions into the central system and no real-time dashboards for replenishment decisions. It is tempting because it satisfies the no-install phone requirement, and it would be the right sole tool if only data capture were needed.

Trap 3: Power BI only

Power BI renders dashboards and reports but cannot capture phone submissions or automate the entry of stock counts into the central system, leaving the paper-and-email process intact. It is tempting because real-time dashboards are an explicit requirement, and Power BI alone would suffice if the data were already flowing into a source it can query.

A
Power Automate only
Why it fails: Power Automate moves and triggers data between services but offers no user interface for managers to submit counts and no dashboards, so the paper-to-system gap persists. It is tempting because automation of data entry is the stated pain point, and it would be correct if a capture app and reporting layer already existed.
B
Power Apps only
Why it fails: Power Apps delivers the mobile browser-based entry form, but it provides no automated flow to write submissions into the central system and no real-time dashboards for replenishment decisions. It is tempting because it satisfies the no-install phone requirement, and it would be the right sole tool if only data capture were needed.
C
Power Apps, Power Automate, and Power BI
Power Apps delivers a phone browser-based canvas app requiring no installation, Power Automate replaces manual entry by writing counts into the central system, and Power BI supplies real-time dashboards. Together they satisfy automation, dashboards and no-install mobile submission.
D
Power BI only
Why it fails: Power BI renders dashboards and reports but cannot capture phone submissions or automate the entry of stock counts into the central system, leaving the paper-and-email process intact. It is tempting because real-time dashboards are an explicit requirement, and Power BI alone would suffice if the data were already flowing into a source it can query.

Question 5hardmulti select

Which THREE of the following are capabilities of Power Virtual Agents? (Choose three.)

Trap 1: Generate interactive reports from conversation data

Power Virtual Agents builds conversational bots; it surfaces analytics dashboards, not interactive reports generated from conversation data, which is Power BI's role. It is tempting because conversation analytics exist, but the capability named is reporting, so it fails this stem's requirement.

Trap 2: Automate complex workflows with conditions

Power Virtual Agents builds conversational bots; conditional branching exists within dialogue topics, but complex multi-step workflow automation with conditions is Power Automate's role. It is tempting because both integrate closely, yet the scenario describing workflow orchestration points to Power Automate, not the bot authoring capability.

A
Use prebuilt templates for common scenarios
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.
B
Escalate conversations to a live human agent
Escalating to a live human agent is a core Power Virtual Agents capability, satisfying the stem's requirement for genuine product features. The bot hands off an in-progress conversation to a configured engagement hub or Dynamics 365 omnichannel queue, preserving context and transcript so the human agent continues seamlessly rather than restarting the dialogue.
C
Create chatbots that can be published to websites and Microsoft Teams
Publishing chatbots to websites and Microsoft Teams is a core Power Virtual Agents capability, directly satisfying the stem's requirement for deployable conversational experiences. The same bot authored once can be surfaced across both external web channels and internal Teams collaboration, without rebuilding logic per channel. This multi-channel publishing distinguishes it from standalone bot frameworks.
D
Generate interactive reports from conversation data
Why it fails: Power Virtual Agents builds conversational bots; it surfaces analytics dashboards, not interactive reports generated from conversation data, which is Power BI's role. It is tempting because conversation analytics exist, but the capability named is reporting, so it fails this stem's requirement.
E
Automate complex workflows with conditions
Why it fails: Power Virtual Agents builds conversational bots; conditional branching exists within dialogue topics, but complex multi-step workflow automation with conditions is Power Automate's role. It is tempting because both integrate closely, yet the scenario describing workflow orchestration points to Power Automate, not the bot authoring capability.

Question 6easymultiple choice

A company wants to automate a business process that requires approval from a manager before an expense report is submitted. Which Microsoft Power Platform component should be used?

Trap 1: Power BI

Power BI visualises and reports on data; it has no workflow engine to trigger, route or track an approval. It is tempting because expense data is often analysed for trends, and would be correct for dashboards reporting approval volumes or spend.

Trap 2: Power Apps

Power Apps builds user interfaces and forms; it cannot itself orchestrate a multi-step approval workflow with routing and notifications. It is tempting because the expense report needs a data-entry screen, and would be correct for the front-end form feeding that process.

Trap 3: Power Virtual Agents

Power Virtual Agents creates conversational chatbots for handling user queries; it cannot enforce a manager approval gate before submission. It is tempting because employees could chat about expenses, and would be correct for answering policy questions rather than routing approvals.

A
Power BI
Why it fails: Power BI visualises and reports on data; it has no workflow engine to trigger, route or track an approval. It is tempting because expense data is often analysed for trends, and would be correct for dashboards reporting approval volumes or spend.
B
Power Apps
Why it fails: Power Apps builds user interfaces and forms; it cannot itself orchestrate a multi-step approval workflow with routing and notifications. It is tempting because the expense report needs a data-entry screen, and would be correct for the front-end form feeding that process.
C
Power Automate
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.
D
Power Virtual Agents
Why it fails: Power Virtual Agents creates conversational chatbots for handling user queries; it cannot enforce a manager approval gate before submission. It is tempting because employees could chat about expenses, and would be correct for answering policy questions rather than routing approvals.

Question 7mediummulti select

Which TWO are benefits of using Microsoft Power Platform for business process automation? (Select TWO)

Trap 1: It can be used offline without any connectivity.

Power Platform components such as Power Apps and Power Automate require connectivity to Microsoft Dataverse and connected services; offline use is not a benefit of the platform. It is tempting because mobile apps can cache data, and offline capability would be correct for field scenarios needing disconnected data capture, not process automation.

Trap 2: It requires no coding skills for any scenario.

Power Platform still requires formulas, expressions or code for complex logic, custom connectors and error handling, so a blanket no-code claim is false. It tempts because citizen developers build many flows without code, making no-code the correct description for simple departmental automation scenarios.

Trap 3: It only works with Microsoft data sources.

Power Platform connectors reach hundreds of non-Microsoft systems, including Salesforce, SAP and on-premises SQL, so restricting it to Microsoft sources contradicts the platform's core value. It tempts because native Microsoft 365 integration is seamless, and that tight coupling would suit an all-Microsoft estate.

A
It reduces development time compared to traditional coding.
Low-code development with Microsoft Power Platform lets makers assemble apps, flows and connectors visually, cutting build time against hand-written code. This directly satisfies the stem's automation benefit: faster delivery of business processes without a professional developer, since prebuilt connectors and templates remove most bespoke coding effort.
B
It can be used offline without any connectivity.
Why it fails: Power Platform components such as Power Apps and Power Automate require connectivity to Microsoft Dataverse and connected services; offline use is not a benefit of the platform. It is tempting because mobile apps can cache data, and offline capability would be correct for field scenarios needing disconnected data capture, not process automation.
C
It requires no coding skills for any scenario.
Why it fails: Power Platform still requires formulas, expressions or code for complex logic, custom connectors and error handling, so a blanket no-code claim is false. It tempts because citizen developers build many flows without code, making no-code the correct description for simple departmental automation scenarios.
D
It integrates easily with Microsoft 365 and Azure services.
Native connectors let flows and apps call Microsoft 365 data and Azure services without custom middleware, satisfying the requirement to automate processes across existing Microsoft investments. This tight integration removes bespoke glue code, cutting development effort and licensing overhead compared with standalone automation tools.
E
It only works with Microsoft data sources.
Why it fails: Power Platform connectors reach hundreds of non-Microsoft systems, including Salesforce, SAP and on-premises SQL, so restricting it to Microsoft sources contradicts the platform's core value. It tempts because native Microsoft 365 integration is seamless, and that tight coupling would suit an all-Microsoft estate.

Question 8easymultiple choice

A user wants to build an app that allows field technicians to view work orders and capture photos offline. Which type of Power App should be chosen?

Trap 1: Power Pages site with offline access.

Power Pages renders external-facing websites and cannot cache work orders or photos for offline capture; its Dataverse integration assumes live connectivity. It is tempting because Power Pages does support some authenticated portal scenarios, but offline field data capture requires a canvas app with the offline profile and Dataverse mobile offline sync.

Trap 2: AI Builder model embedded in a canvas app.

AI Builder adds prediction or extraction models; it does not provide offline data storage or sync for work orders and photos. It is tempting because AI Builder is used inside canvas apps for image processing, but the requirement is offline Dataverse access, which the canvas app's offline profile supplies independently of any AI model.

Trap 3: Model-driven app because it natively supports offline.

Model-driven apps do not natively support offline; offline capability comes from the mobile offline profile configured on the app, and model-driven forms are not designed for camera capture. It is tempting because model-driven apps suit Dataverse table-centric processes, but the stem's photo capture and offline field use point to a canvas app.

A
Power Pages site with offline access.
Why it fails: Power Pages renders external-facing websites and cannot cache work orders or photos for offline capture; its Dataverse integration assumes live connectivity. It is tempting because Power Pages does support some authenticated portal scenarios, but offline field data capture requires a canvas app with the offline profile and Dataverse mobile offline sync.
B
AI Builder model embedded in a canvas app.
Why it fails: AI Builder adds prediction or extraction models; it does not provide offline data storage or sync for work orders and photos. It is tempting because AI Builder is used inside canvas apps for image processing, but the requirement is offline Dataverse access, which the canvas app's offline profile supplies independently of any AI model.
C
Model-driven app because it natively supports offline.
Why it fails: Model-driven apps do not natively support offline; offline capability comes from the mobile offline profile configured on the app, and model-driven forms are not designed for camera capture. It is tempting because model-driven apps suit Dataverse table-centric processes, but the stem's photo capture and offline field use point to a canvas app.
D
Canvas app with offline capability enabled.
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.

Question 9mediummultiple choice

A company has a Power BI dashboard that displays real-time data from Azure Stream Analytics. Which connection type should they use?

Trap 1: Import

Import caches data on a scheduled refresh, so it cannot display real-time streaming output; latency equals the refresh interval. Streaming datasets pushed from Azure Stream Analytics deliver near-real-time updates. Import is correct for historical or slowly changing data, not live telemetry.

Trap 2: DirectQuery

DirectQuery issues queries against the source on each visual interaction, but Azure Stream Analytics output lands in a streaming dataset, which Power BI consumes through its push dataset API rather than a DirectQuery connection. DirectQuery suits large relational sources needing live reads without import.

Trap 3: Composite model

A composite model combines Import and DirectQuery tables within one dataset, adding latency and refresh complexity. Streaming data from Azure Stream Analytics arrives via push datasets, which bypass composite modelling entirely. Composite models suit mixing cached and live relational sources.

A
Import
Why it fails: Import caches data on a scheduled refresh, so it cannot display real-time streaming output; latency equals the refresh interval. Streaming datasets pushed from Azure Stream Analytics deliver near-real-time updates. Import is correct for historical or slowly changing data, not live telemetry.
B
DirectQuery
Why it fails: DirectQuery issues queries against the source on each visual interaction, but Azure Stream Analytics output lands in a streaming dataset, which Power BI consumes through its push dataset API rather than a DirectQuery connection. DirectQuery suits large relational sources needing live reads without import.
C
Composite model
Why it fails: A composite model combines Import and DirectQuery tables within one dataset, adding latency and refresh complexity. Streaming data from Azure Stream Analytics arrives via push datasets, which bypass composite modelling entirely. Composite models suit mixing cached and live relational sources.
D
Push dataset
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.

Question 10easymultiple choice

A sales team needs an app to track customer interactions. The app should display a list of accounts, and when an account is selected, show related opportunities and contacts. Which type of app is best suited?

Trap 1: Canvas app

A canvas app gives the developer a blank canvas with no automatic record-to-related-record navigation, so the account, opportunity and contact relationship must be built manually. It is tempting for its design freedom, and it would suit a highly customised interface rather than model-driven relationship views.

Trap 2: Power BI dashboard

A Power BI dashboard renders aggregated visuals for analysis, not interactive record navigation between accounts, opportunities and contacts. It is tempting because Power BI connects to Dataverse and displays account data, but it would be correct when the requirement is reporting and insight rather than transactional record browsing.

Trap 3: Chatbot in Power Virtual Agents

A Power Virtual Agents chatbot handles conversational question-and-answer flows, not a relational list-to-detail interface showing related records. It is tempting because chatbots surface Dataverse data conversationally, but it would be correct when users need to query information through natural-language dialogue rather than navigate linked tables.

A
Canvas app
Why it fails: A canvas app gives the developer a blank canvas with no automatic record-to-related-record navigation, so the account, opportunity and contact relationship must be built manually. It is tempting for its design freedom, and it would suit a highly customised interface rather than model-driven relationship views.
B
Power BI dashboard
Why it fails: A Power BI dashboard renders aggregated visuals for analysis, not interactive record navigation between accounts, opportunities and contacts. It is tempting because Power BI connects to Dataverse and displays account data, but it would be correct when the requirement is reporting and insight rather than transactional record browsing.
C
Chatbot in Power Virtual Agents
Why it fails: A Power Virtual Agents chatbot handles conversational question-and-answer flows, not a relational list-to-detail interface showing related records. It is tempting because chatbots surface Dataverse data conversationally, but it would be correct when users need to query information through natural-language dialogue rather than navigate linked tables.
D
Model-driven app
Model-driven apps generate UI directly from the Dataverse data model, so defining relationships between accounts, opportunities and contacts produces the list-and-related-records navigation automatically, with no manual screen wiring. This satisfies the requirement to show related opportunities and contacts when an account is selected.

Question 11mediummultiple choice

A financial services firm needs to create a compliance dashboard for regulators. The dashboard must display real-time data from multiple sources, including on-premises SQL Server and Dataverse. The firm requires interactive visualizations and the ability to drill down to transaction details. They also need to ensure that sensitive data is masked for certain users. Which Power Platform components should they use?

Trap 1: Power Automate, AI Builder, and Power BI

Power Automate is not needed for the dashboard itself.

Trap 2: Copilot Studio, Power BI, and Dataverse

Copilot Studio is not needed for compliance dashboards.

Trap 3: Power Apps, Dataverse, and Power Automate

Power Apps is not a dashboard tool.

A
Power Automate, AI Builder, and Power BI
Why it fails: Power Automate is not needed for the dashboard itself.
B
Power BI, on-premises data gateway, and Dataverse
Power BI provides dashboards with RLS, gateway connects to on-premises SQL, Dataverse is another data source.
C
Copilot Studio, Power BI, and Dataverse
Why it fails: Copilot Studio is not needed for compliance dashboards.
D
Power Apps, Dataverse, and Power Automate
Why it fails: Power Apps is not a dashboard tool.

Question 12mediummultiple choice

A retail company uses Power Apps to build a mobile app for store managers to approve discount requests. The app must work offline and sync when connected. Which type of app should the developer choose?

Trap 1: Portal

Portals publish external-facing websites backed by Dataverse; they run in a browser session and hold no local offline store, so approvals cannot be captured without connectivity. Portals suit anonymous or authenticated web access for customers and partners, not a store manager's disconnected mobile app.

Trap 2: Model-driven app

Model-driven apps render from Dataverse metadata and require a live connection, so they cannot queue approvals offline and sync later. They suit form-over-data processes with complex relationships, not disconnected field use; canvas apps provide the offline storage and sync this scenario demands.

Trap 3: Power Automate

Power Automate orchestrates flows between services; it builds no user interface for managers to approve requests, and its triggers depend on connectivity. It is the right tool for automating the approval notification or Dataverse write-back once a decision is made, not for the offline app itself.

A
Portal
Why it fails: Portals publish external-facing websites backed by Dataverse; they run in a browser session and hold no local offline store, so approvals cannot be captured without connectivity. Portals suit anonymous or authenticated web access for customers and partners, not a store manager's disconnected mobile app.
B
Model-driven app
Why it fails: Model-driven apps render from Dataverse metadata and require a live connection, so they cannot queue approvals offline and sync later. They suit form-over-data processes with complex relationships, not disconnected field use; canvas apps provide the offline storage and sync this scenario demands.
C
Canvas app
Canvas apps support offline capability through the SaveData and LoadData functions, storing data locally on the device and syncing when connectivity returns. This directly satisfies the requirement that store managers approve discount requests without network access.
D
Power Automate
Why it fails: Power Automate orchestrates flows between services; it builds no user interface for managers to approve requests, and its triggers depend on connectivity. It is the right tool for automating the approval notification or Dataverse write-back once a decision is made, not for the offline app itself.

Question 13mediummultiple choice

A non-profit organization wants to automate the process of sending thank-you emails to donors after a donation is recorded in a SharePoint list. Which Power Platform tool should they use?

Trap 1: Power Apps

Power Apps builds interactive user interfaces for data entry and viewing, not event-driven background automation triggered by a SharePoint list change. It would be the right choice when staff need a custom canvas or model-driven form to record donations, rather than sending emails automatically.

Trap 2: Power Virtual Agents

Power Virtual Agents builds conversational chatbots, so it cannot trigger an email when a SharePoint item is created. It would be the right choice when donors need to interact with a bot that answers questions or collects information, rather than for event-driven background automation.

Trap 3: Power BI

Power BI visualises and analyses data through reports and dashboards; it cannot detect a new SharePoint list item and send an email. It would be the right choice when the non-profit needs to analyse donation trends or build interactive reports for fundraising decisions.

A
Power Apps
Why it fails: Power Apps builds interactive user interfaces for data entry and viewing, not event-driven background automation triggered by a SharePoint list change. It would be the right choice when staff need a custom canvas or model-driven form to record donations, rather than sending emails automatically.
B
Power Virtual Agents
Why it fails: Power Virtual Agents builds conversational chatbots, so it cannot trigger an email when a SharePoint item is created. It would be the right choice when donors need to interact with a bot that answers questions or collects information, rather than for event-driven background automation.
C
Power Automate
Power Automate triggers on the SharePoint list item creation event and runs an automated cloud flow that sends the thank-you email via an Outlook connector. This delivers the event-driven automation the non-profit needs without manual intervention.
D
Power BI
Why it fails: Power BI visualises and analyses data through reports and dashboards; it cannot detect a new SharePoint list item and send an email. It would be the right choice when the non-profit needs to analyse donation trends or build interactive reports for fundraising decisions.

Question 14mediummulti select

A company wants to use Power Platform to streamline its expense reporting process. Which TWO components can be used together to create a complete solution that allows employees to submit expenses, managers to approve them, and finance to analyze trends?

Trap 1: Copilot Studio

Copilot Studio builds conversational agents and chatbots, which cannot capture structured expense submissions, route manager approvals, or store records. It is tempting because it delivers a friendly employee-facing interface, but that role here belongs to Power Apps, with Power Automate handling the approval workflow and Power BI the trend analysis.

Trap 2: Power BI

Power BI delivers dashboards and reports for the finance trend analysis, but provides no data-entry forms or approval routing, so employees cannot submit expenses or managers approve them. It is tempting because analytics is explicitly required, yet that requirement is only one of three; Power Apps and Power Automate cover submission and approval.

Trap 3: Power Pages

Power Pages builds external-facing websites for anonymous or portal users, offering no structured expense capture, approval workflow, or analytics. It is tempting when employees need a browser-based entry point, but internal submissions and manager approvals are handled by Power Apps and Power Automate, with Power BI for finance reporting.

A
Copilot Studio
Why it fails: Copilot Studio builds conversational agents and chatbots, which cannot capture structured expense submissions, route manager approvals, or store records. It is tempting because it delivers a friendly employee-facing interface, but that role here belongs to Power Apps, with Power Automate handling the approval workflow and Power BI the trend analysis.
B
Power BI
Why it fails: Power BI delivers dashboards and reports for the finance trend analysis, but provides no data-entry forms or approval routing, so employees cannot submit expenses or managers approve them. It is tempting because analytics is explicitly required, yet that requirement is only one of three; Power Apps and Power Automate cover submission and approval.
C
Power Apps
Power Apps provides the canvas or model-driven interface employees use to submit expenses and managers use to approve them, satisfying the submission and approval requirements. It integrates natively with Dataverse for storage and Power BI for finance trend analysis, forming the complete solution the stem demands.
D
Power Automate
Power Automate supplies the workflow engine that routes each submitted expense to the correct manager and triggers approval or rejection actions automatically. Combined with Power Apps for data entry and Power BI for trend analysis, it satisfies the stem's requirement for manager approval, enforcing the multi-step process without manual intervention.
E
Power Pages
Why it fails: Power Pages builds external-facing websites for anonymous or portal users, offering no structured expense capture, approval workflow, or analytics. It is tempting when employees need a browser-based entry point, but internal submissions and manager approvals are handled by Power Apps and Power Automate, with Power BI for finance reporting.

Question 15easymultiple choice

You need to create a flow that runs every hour and checks if any new files have been added to a SharePoint document library. Which trigger type should you use?

Trap 1: Compose

Compose constructs data within a flow; it cannot initiate execution, so no hourly run occurs. It is tempting because it appears in the action picker alongside triggers, but it would be the correct choice for shaping or transforming values mid-flow, not for scheduling.

Trap 2: When an item is created

'When an item is created' fires per new SharePoint item, giving event-driven execution rather than the required hourly recurrence. It is tempting because it detects new files, but it would be correct when immediate notification on creation is wanted, not a scheduled poll.

Trap 3: Power Apps button

A Power Apps button trigger starts a flow from a canvas app interaction, so it cannot run hourly. It is tempting because it is a genuine instant trigger type, but it would be correct when a user taps a control in Power Apps, not for time-based scheduling.

A
Compose
Why it fails: Compose constructs data within a flow; it cannot initiate execution, so no hourly run occurs. It is tempting because it appears in the action picker alongside triggers, but it would be the correct choice for shaping or transforming values mid-flow, not for scheduling.
B
When an item is created
Why it fails: 'When an item is created' fires per new SharePoint item, giving event-driven execution rather than the required hourly recurrence. It is tempting because it detects new files, but it would be correct when immediate notification on creation is wanted, not a scheduled poll.
C
Recurrence
The Recurrence trigger fires at fixed intervals, such as every hour, then the flow queries SharePoint for newly added files. This satisfies the hourly schedule requirement, since event-based triggers cannot guarantee a regular time interval.
D
Power Apps button
Why it fails: A Power Apps button trigger starts a flow from a canvas app interaction, so it cannot run hourly. It is tempting because it is a genuine instant trigger type, but it would be correct when a user taps a control in Power Apps, not for time-based scheduling.

Question 16mediummultiple choice

A company wants to enable its field service technicians to access customer records and update work orders from their mobile devices offline. Which Power Platform solution should they implement?

Trap 1: Power Pages website accessible from mobile browsers

Power Pages is for external-facing websites, not for offline mobile access.

Trap 2: Power BI dashboards embedded in a mobile app

Power BI is for reporting, not for transactional data entry.

Trap 3: Power Automate flows to sync data periodically

Power Automate does not provide a mobile app interface for technicians to interact with records.

A
Power Pages website accessible from mobile browsers
Why it fails: Power Pages is for external-facing websites, not for offline mobile access.
B
Power Apps (model-driven) configured for offline use
Model-driven Power Apps can be used offline, enabling technicians to view and edit data on their mobile devices.
C
Power BI dashboards embedded in a mobile app
Why it fails: Power BI is for reporting, not for transactional data entry.
D
Power Automate flows to sync data periodically
Why it fails: Power Automate does not provide a mobile app interface for technicians to interact with records.

Question 17hardmulti select

Which TWO of the following are required to set up a Power Pages site that allows external users to sign in using their social media accounts?

Trap 1: Deploy a model-driven app to manage user registrations.

A model-driven app manages internal staff working with Dataverse records; it plays no part in external social sign-in. It would be correct when employees need forms, views and dashboards over the same data. Social login instead requires configuring an identity provider and enabling external authentication on the site.

Trap 2: Configure Microsoft Entra ID as the identity provider.

Microsoft Entra ID authenticates internal organisational accounts, not consumer social identities such as Facebook or Google. It is the right provider when external partners already hold work accounts in your tenant. Social sign-in needs an OpenID Connect provider configured for each social network instead.

Trap 3: Create a local contact record for each external user.

Power Pages creates the contact record automatically when an external user registers through an identity provider; manual creation is unnecessary. Creating contacts manually suits importing known customers before they ever sign in. The required setup is the identity provider configuration plus the site's authentication settings.

A
Deploy a model-driven app to manage user registrations.
Why it fails: A model-driven app manages internal staff working with Dataverse records; it plays no part in external social sign-in. It would be correct when employees need forms, views and dashboards over the same data. Social login instead requires configuring an identity provider and enabling external authentication on the site.
B
Set up the social identity provider in the Power Pages admin center.
Registering the social provider in the Power Pages admin centre creates the site's identity provider configuration, enabling the external authentication handshake. Without this entry, Power Pages cannot redirect visitors to the social platform or trust its returned claims, so social sign-in fails regardless of credentials.
C
Configure Microsoft Entra ID as the identity provider.
Why it fails: Microsoft Entra ID authenticates internal organisational accounts, not consumer social identities such as Facebook or Google. It is the right provider when external partners already hold work accounts in your tenant. Social sign-in needs an OpenID Connect provider configured for each social network instead.
D
Obtain a client ID and client secret from the social media platform.
The client ID and client secret are issued by the social platform's developer portal and authenticate the Power Pages site during the OAuth exchange. Power Pages needs these credentials to request tokens on the user's behalf, satisfying the external identity provider requirement.
E
Create a local contact record for each external user.
Why it fails: Power Pages creates the contact record automatically when an external user registers through an identity provider; manual creation is unnecessary. Creating contacts manually suits importing known customers before they ever sign in. The required setup is the identity provider configuration plus the site's authentication settings.

Question 18mediummulti select

Which TWO of the following are capabilities of Power Apps that help organizations build custom business applications without writing traditional code?

Trap 1: Natural language processing to create conversational bots

Conversational bots are built with Power Virtual Agents, not Power Apps, so this capability sits outside the canvas and model-driven app builders. It is tempting because both products share the Power Platform and low-code ethos, and Power Virtual Agents would be the right choice when the requirement is a chatbot.

Trap 2: Automated workflows triggered by business events

Event-triggered automation belongs to Power Automate, which orchestrates flows across services; Power Apps itself provides app UI and data binding. It is tempting because apps often call flows, and Power Automate would be correct when the requirement is background processing rather than a custom application interface.

Trap 3: Real-time data dashboards with drill-down analytics

Real-time dashboards with drill-down analytics are a feature of Power BI, not Power Apps; Power Apps focuses on building custom application interfaces and logic through connectors and canvas or model-driven design, whereas Power BI specialises in data visualisation and business intelligence. This option tempts because both platforms integrate with Microsoft Entra ID and Dataverse, and a Power App can embed a Power BI dashboard, but the stem specifically asks for capabilities that build applications without code, not for analytics tools.

A
Integration with Common Data Service (Microsoft Dataverse)
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.
B
Pre-built templates for common business scenarios
Templates ship pre-wired screens, data schemas and logic for common scenarios, so makers start from a working app and adjust it visually. This directly satisfies the no-traditional-code constraint by eliminating the need to author app structure from scratch.
C
Natural language processing to create conversational bots
Why it fails: Conversational bots are built with Power Virtual Agents, not Power Apps, so this capability sits outside the canvas and model-driven app builders. It is tempting because both products share the Power Platform and low-code ethos, and Power Virtual Agents would be the right choice when the requirement is a chatbot.
D
Automated workflows triggered by business events
Why it fails: Event-triggered automation belongs to Power Automate, which orchestrates flows across services; Power Apps itself provides app UI and data binding. It is tempting because apps often call flows, and Power Automate would be correct when the requirement is background processing rather than a custom application interface.
E
Real-time data dashboards with drill-down analytics
Why it fails: Real-time dashboards with drill-down analytics are a feature of Power BI, not Power Apps; Power Apps focuses on building custom application interfaces and logic through connectors and canvas or model-driven design, whereas Power BI specialises in data visualisation and business intelligence. This option tempts because both platforms integrate with Microsoft Entra ID and Dataverse, and a Power App can embed a Power BI dashboard, but the stem specifically asks for capabilities that build applications without code, not for analytics tools.

Question 19mediummultiple choice

A company uses Power Apps to manage employee leave requests. They want to automate the approval process so that managers receive an email when a request is submitted. Which component should they add?

Trap 1: Power BI

Power BI renders dashboards and reports from data; it cannot trigger emails on a leave-request submission. It is tempting because it visualises the leave data stored by the app, which suits reporting on approval trends, but the requirement is event-driven notification, which Power Automate flows provide.

Trap 2: AI Builder

AI Builder provides prediction and form-processing models, not event-driven approval routing. It is tempting because AI Builder adds intelligence to apps, but it cannot send manager emails on submission. That trigger-and-action automation belongs to Power Automate, which fires when a leave request record is created and notifies the approver.

Trap 3: Power Virtual Agents

Power Virtual Agents builds conversational bots that respond to user chat; it cannot send a manager an email when a record is created. It is tempting because it automates interaction within Power Platform, and would be correct for a self-service leave-balance chatbot, but not for record-triggered email notification.

A
Power Automate
Power Automate supplies the event-driven workflow engine that Power Apps alone lacks. A flow triggers on the leave request's creation, then sends the manager an approval email, satisfying the requirement to notify managers automatically on submission without custom code.
B
Power BI
Why it fails: Power BI renders dashboards and reports from data; it cannot trigger emails on a leave-request submission. It is tempting because it visualises the leave data stored by the app, which suits reporting on approval trends, but the requirement is event-driven notification, which Power Automate flows provide.
C
AI Builder
Why it fails: AI Builder provides prediction and form-processing models, not event-driven approval routing. It is tempting because AI Builder adds intelligence to apps, but it cannot send manager emails on submission. That trigger-and-action automation belongs to Power Automate, which fires when a leave request record is created and notifies the approver.
D
Power Virtual Agents
Why it fails: Power Virtual Agents builds conversational bots that respond to user chat; it cannot send a manager an email when a record is created. It is tempting because it automates interaction within Power Platform, and would be correct for a self-service leave-balance chatbot, but not for record-triggered email notification.

Question 20easymultiple choice

You are creating a flow that should run only when a button is pressed in a mobile app. The flow will send an email to a manager with the current location of the user. Which type of flow should you create?

Trap 1: Scheduled cloud flow

A scheduled cloud flow relies on a recurring time-based trigger, such as every hour or daily at 9 AM, and cannot be initiated by a button press in a mobile app. It is tempting because scheduled flows are commonly used for automated, periodic tasks like sending daily summary emails to a manager, which might seem similar to the email-sending requirement here. However, the scenario demands an instant trigger from a user action, which only an instant cloud flow or button-triggered flow can provide.

Trap 2: Automated cloud flow

An automated cloud flow triggers on an event such as a new Dataverse row or incoming email, not on a manual button press. It would be correct for event-driven onboarding, but the scenario requires user-initiated execution, which is the instant cloud flow trigger.

Trap 3: Desktop flow

A desktop flow drives a Windows desktop through UI automation and requires a machine or gateway, so it cannot be triggered by a mobile button and cannot read the device's current location. Desktop flows suit legacy applications lacking APIs, not mobile-initiated cloud actions.

A
Instant cloud flow
An instant cloud flow is triggered manually by user action, such as tapping a button in the Power Automate mobile app. This satisfies the requirement that the flow runs only when a button is pressed, unlike automated or scheduled flows that trigger without direct user input.
B
Scheduled cloud flow
Why it fails: A scheduled cloud flow relies on a recurring time-based trigger, such as every hour or daily at 9 AM, and cannot be initiated by a button press in a mobile app. It is tempting because scheduled flows are commonly used for automated, periodic tasks like sending daily summary emails to a manager, which might seem similar to the email-sending requirement here. However, the scenario demands an instant trigger from a user action, which only an instant cloud flow or button-triggered flow can provide.
C
Automated cloud flow
Why it fails: An automated cloud flow triggers on an event such as a new Dataverse row or incoming email, not on a manual button press. It would be correct for event-driven onboarding, but the scenario requires user-initiated execution, which is the instant cloud flow trigger.
D
Desktop flow
Why it fails: A desktop flow drives a Windows desktop through UI automation and requires a machine or gateway, so it cannot be triggered by a mobile button and cannot read the device's current location. Desktop flows suit legacy applications lacking APIs, not mobile-initiated cloud actions.