CCNA Describe complementary Microsoft Power Platform solutions Questions

MCQmedium

A company uses Microsoft Power Platform to automate invoice processing. They want to integrate with their existing ERP system hosted on Azure SQL Database. Which Power Platform component is best suited for this integration?

A.Dataverse

B.Power BI

C.Power Automate

D.Power Apps

AnswerC

Power Automate creates automated workflows and can connect to Azure SQL Database via connectors.

Why this answer

Power Automate is the correct choice because it provides built-in connectors for Azure SQL Database, enabling seamless integration with the existing ERP system without custom code. It can trigger automated workflows based on invoice events, such as when a new record is created in the SQL database, and orchestrate data processing across multiple systems.

Exam trap

The trap here is that candidates often confuse Power Automate with Power Apps, thinking that building an app is necessary for integration, but Power Automate is specifically designed for workflow automation and system-to-system integration without a user interface.

How to eliminate wrong answers

Option A is wrong because Dataverse is a data storage and management platform, not an integration tool; it would require additional components to connect to Azure SQL Database. Option B is wrong because Power BI is a data visualization and analytics tool, not designed for system integration or workflow automation. Option D is wrong because Power Apps is a low-code application development platform; while it can connect to Azure SQL Database, it is meant for building user interfaces, not for automating backend integration processes.

Practice this question →

MCQeasy

A manufacturing company uses Microsoft Power Platform to manage its inventory. They have a Power Apps app that allows warehouse staff to scan items and update quantities in a SharePoint list. Recently, the app has been slow to load and occasionally times out when scanning multiple items in quick succession. The IT team suspects the issue is related to the data source connection. They want to improve performance without changing the user interface. The company has a Microsoft 365 E3 subscription and all data resides in SharePoint Online. What should the IT team do first?

A.Implement a timer control to delay scanning between items.

B.Migrate the SharePoint list to an on-premises SQL Server database.

C.Optimize the Power Apps by enabling delegation for the SharePoint connector.

D.Replace SharePoint with Microsoft Dataverse for better performance.

AnswerC

Delegation allows queries to be processed server-side, reducing data transfer.

Why this answer

Option C is correct because enabling delegation for the SharePoint connector allows Power Apps to offload filtering and sorting operations to SharePoint Online, rather than retrieving all rows to the client. This reduces the amount of data transferred over the network, which directly addresses the slow load and timeout issues when scanning multiple items in quick succession, without changing the user interface.

Exam trap

The trap here is that candidates often confuse 'optimizing performance' with 'changing the data source' (Option B or D) or 'adding client-side delays' (Option A), rather than recognizing that the most immediate and non-disruptive fix is to enable delegation on the existing SharePoint connector.

How to eliminate wrong answers

Option A is wrong because adding a timer control to delay scanning would degrade user experience and does not address the root cause of slow data source performance; it merely masks the symptom. Option B is wrong because migrating to an on-premises SQL Server would introduce latency and administrative overhead, contradicting the requirement to improve performance without changing the UI and ignoring the existing cloud-based SharePoint Online environment. Option D is wrong because replacing SharePoint with Microsoft Dataverse would require significant changes to the app and data structure, violating the constraint of not changing the user interface, and Dataverse is not inherently faster for all scenarios without proper delegation and indexing.

Practice this question →

Matchingmedium

Match each connector type in Power Automate to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Common connectors like Office 365, SharePoint

Connectors requiring additional licensing

Connectors built by developers for specific APIs

Connects to on-premises data via gateway

Connector that wraps multiple APIs

Why these pairings

Connectors enable integration with various services.

Practice this question →

MCQmedium

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?

A.Power Automate

B.Power BI

C.AI Builder

D.Power Virtual Agents

AnswerA

Power Automate can be triggered by Power Apps to send approval emails.

Why this answer

Power Automate is the correct component because it is designed to create automated workflows that trigger actions based on events. In this scenario, when a leave request is submitted in Power Apps, a Power Automate flow can be configured to send an email notification to the manager, automating the approval process without manual intervention.

Exam trap

The trap here is that candidates may confuse Power Automate with Power BI, thinking that reporting tools can also send notifications, but Power BI lacks workflow automation capabilities.

How to eliminate wrong answers

Option B is wrong because Power BI is a business analytics tool used for data visualization and reporting, not for automating workflows or sending emails. Option C is wrong because AI Builder adds artificial intelligence capabilities (e.g., form processing, object detection) to Power Platform solutions, but it does not handle event-driven email notifications. Option D is wrong because Power Virtual Agents is used to build conversational chatbots, not to automate backend processes like sending approval emails.

Practice this question →

Multi-Selecthard

Which TWO Microsoft Power Platform solutions are designed to be used together to build a complete customer feedback analysis system that collects feedback from multiple channels, processes sentiment, and provides actionable insights?

Select 2 answers

A.Dataverse

B.Power Apps

C.Power BI

D.AI Builder

E.Power Automate

AnswersD, E

Can process sentiment analysis from text feedback.

Why this answer

AI Builder (D) is correct because it provides pre-built AI models for sentiment analysis, which can process feedback text from multiple channels to determine positive, negative, or neutral sentiment. Power Automate (E) is correct because it orchestrates the collection of feedback from various sources (e.g., email, forms, social media) and triggers actions based on sentiment results, enabling a complete automated feedback analysis pipeline.

Exam trap

The trap here is that candidates often confuse the role of Power BI (visualization) with the need for actual sentiment processing and automation, leading them to select Power BI instead of AI Builder or Power Automate, when the question specifically requires solutions that collect, process, and provide insights—not just display them.

Practice this question →

MCQhard

A team is building a customer service solution using Power Apps and Dataverse. They need to ensure that customer data is synchronized with Dynamics 365 Customer Service. Which approach should they use?

A.Use Dataverse as the data store and connect both Power Apps and Dynamics 365 to it

B.Build a custom connector to transfer data between Power Apps and Dynamics 365

C.Implement a third-party middleware solution

D.Export data from Dynamics 365 and import it into Power Apps periodically

AnswerA

Dataverse is the underlying data platform for Dynamics 365 and Power Apps, providing native synchronization.

Why this answer

Using Dataverse as the common data store and connecting both Power Apps and Dynamics 365 to it ensures real-time synchronization. Direct integration via custom APIs is possible but not best practice. Power Automate flows can also sync, but Dataverse is the recommended approach for Dynamics 365.

Practice this question →

MCQeasy

A company wants to create a dashboard that shows real-time sales data from their ERP system and allows managers to drill down into individual transactions. Which Power Platform component should they use?

A.Power BI

B.Power Apps

C.Power Automate

D.AI Builder

AnswerA

Power BI provides interactive dashboards with drill-down features.

Why this answer

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.

Exam trap

Microsoft often tests the misconception that Power Apps can build dashboards because it includes canvas apps with charts, but Power Apps lacks native drill-through and real-time data aggregation capabilities required for enterprise dashboards.

How to eliminate wrong answers

Option B (Power Apps) is wrong because Power Apps is a low-code platform for building custom applications, not for creating dashboards with real-time data visualization and drill-down analytics. Option C (Power Automate) is wrong because Power Automate focuses on workflow automation and process orchestration, not on interactive data visualization or dashboard creation. Option D (AI Builder) is wrong because AI Builder provides prebuilt AI models for tasks like form processing or prediction, not for building dashboards or drilling into transactional data.

Practice this question →

Multi-Selectmedium

A company uses Microsoft Power Platform to automate business processes. They want to extend their solution by integrating with other Microsoft services. Which TWO services can be used together with Power Automate to trigger flows based on events from external systems?

Select 2 answers

A.Azure Logic Apps

B.Azure Event Grid

C.Power Virtual Agents

D.Azure DevOps

E.Azure SQL Database

AnswersA, B

Azure Logic Apps can trigger Power Automate flows via connectors.

Why this answer

Azure Logic Apps is a cloud service that provides pre-built connectors and enterprise integration capabilities, allowing Power Automate to trigger flows based on events from external systems via HTTP requests, webhooks, or service bus messages. Azure Event Grid is a fully managed event routing service that uses a publish-subscribe model, enabling Power Automate to react to events from Azure services or custom sources in near real-time. Both services extend Power Automate's event-driven triggers beyond its native connectors.

Exam trap

The trap here is that candidates may confuse Azure Logic Apps as a standalone alternative to Power Automate rather than recognizing it as a complementary service that provides advanced event triggers, or they may incorrectly assume Azure SQL Database can natively trigger flows without an intermediary event service.

Practice this question →

MCQhard

An organization is configuring a custom connector in Power Automate to connect to Salesforce. The exhibit shows a snippet of the connector definition. However, when attempting to test the connection, the authentication fails. What is the most likely cause?

A.The OAuth flow type is incorrectly set to 'accessCode' instead of 'authorizationCode'.

B.The scopes array is missing the 'id' scope.

C.The apiVersion is not supported by Power Automate.

D.The serviceUrl should point to the Salesforce instance, not login.salesforce.com.

AnswerA

The correct OAuth flow for authorization code is 'authorizationCode'.

Why this answer

Option A is correct because the OAuth 2.0 flow type 'accessCode' is not a valid OAuth 2.0 grant type. The correct value for the authorization code grant type is 'authorizationCode'. Power Automate custom connectors require this exact string to properly initiate the OAuth 2.0 authorization code flow with Salesforce.

Using 'accessCode' causes the authentication handshake to fail because the connector cannot map the flow to a supported OAuth grant.

Exam trap

The trap here is that candidates may assume 'accessCode' is a valid OAuth flow type because it appears in some third-party documentation or older samples, but the PL-900 exam expects the exact OAuth 2.0 standard term 'authorizationCode' as used in Power Automate custom connector definitions.

How to eliminate wrong answers

Option B is wrong because the 'scopes' array does not require an 'id' scope; Salesforce OAuth scopes are defined by the connected app and typically include 'api', 'refresh_token', and 'offline_access' but not 'id' unless specifically needed for OpenID Connect. Option C is wrong because Power Automate supports multiple Salesforce API versions (e.g., v58.0, v59.0) and an unsupported version would cause a different error (e.g., 404 or version mismatch), not an authentication failure. Option D is wrong because 'login.salesforce.com' is the correct OAuth token endpoint for Salesforce production instances; pointing to a specific instance URL would break the token exchange because the OAuth endpoint must be the global login URL for token issuance.

Practice this question →

Drag & Dropmedium

Drag and drop the steps to create a Power Automate flow that sends an email when a new item is added to SharePoint in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

The flow starts with an automated trigger, then adds an email action, and is saved after configuration.

Practice this question →

MCQhard

You are a Power Platform administrator for a large multinational company that uses Microsoft Power Platform to manage its sales operations. The company has a Power App for sales representatives to log customer meetings and a Power Automate flow that sends a summary email to the sales manager after each meeting is logged. Recently, sales representatives have reported that the app is slow to load and sometimes times out. The IT team has checked network connectivity and server performance and found no issues. The app uses Dataverse as its data source and includes several lookup fields to related tables. The Power Automate flow runs immediately after a meeting is created and queries additional data from the Dataverse. You suspect the issue is related to the flow's trigger and subsequent queries. What course of action should you take to improve performance?

A.Modify the flow to run on a schedule instead of immediately upon record creation

B.Disable the Power Automate flow and manually send summary emails

C.Implement caching in the Power App to store lookup data locally

D.Increase the timeout duration of the Power Automate flow to allow more time for queries

AnswerA

Running on a schedule reduces the immediate load on the Dataverse and improves app responsiveness.

Why this answer

Option A is correct because the performance issue is likely caused by the Power Automate flow's trigger running synchronously or near-synchronously upon record creation, which can block the app's response or cause timeouts if the flow queries additional Dataverse data. By modifying the flow to run on a schedule (e.g., every 5 minutes), you decouple the heavy query operations from the real-time app interaction, reducing the load on the app's session and preventing timeouts.

Exam trap

The trap here is that candidates often confuse client-side app performance issues (like lookup caching) with server-side flow execution delays, and they incorrectly assume that increasing timeouts or disabling automation will solve the problem, rather than recognizing that decoupling the flow from the real-time trigger is the proper architectural fix.

How to eliminate wrong answers

Option B is wrong because disabling the flow entirely removes automation and forces manual work, which is not a scalable or efficient solution and does not address the root cause of performance degradation. Option C is wrong because implementing caching in the Power App stores lookup data locally on the client side, which does not affect the server-side Dataverse queries triggered by the Power Automate flow; the slowdown is caused by the flow's queries, not the app's lookup fields. Option D is wrong because increasing the timeout duration of the flow only allows the flow to wait longer for queries to complete, but it does not reduce the load on the Dataverse or prevent the app from timing out while the flow is still executing.

Practice this question →