Power Apps Integration with Connectors and Flows
HOTSPOT A user is starting to learn about Power Apps. Which objects should you use? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area: [sampleXML/xmlfile-89_1.png]
Community Insight
The question tests the architectural components of Power Platform integration: Apps utilize Connectors for data access and trigger Flows for automation.
This PL-900 hotspot question tests the relationship between Power Apps, connectors, and flows. The page establishes that apps use connectors to access data and triggers flows for business logic.
Learners often incorrectly select 'Flow' for both slots, failing to distinguish that an App directly interacts with a Connector, which then invokes the Flow.
Community Discussion (70 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
In the Microsoft Power Platform architecture, a Power App is the user interface layer. To interact with external data sources (like SharePoint, SQL, or Dataverse), the app must use a Connector. Therefore, the first blank, 'An App calls a...', refers to the Connector. Once the connector is engaged, it can trigger a Flow (an automated workflow) to perform actions like sending emails or updating records. Thus, the second part describes the mechanism by which the app initiates a Flow.Why Other Candidate Answers Are Wrong
Selecting 'Flow' for the first slot is incorrect because Apps do not 'call' flows directly in the same way they call connectors; they call connectors, which may include the Power Automate Management connector to trigger flows. Selecting 'Connector' for the second slot is wrong because a connector itself does not have triggers and actions in the context of being called by an app; rather, the connector provides operations, and the Flow contains the specific triggers and actions that execute the logic.Community Comment Notes
Many users correctly identified the sequence as Connector then Flow. Some confusion existed where users argued that since the Flow is technically a connector inside the app, both should be Flow. However, the exam expects the high-level architectural distinction: App -> Connector -> Flow. Comments referencing official documentation confirm that connectors offer operations classified as actions and triggers.Official Reference
Exam Strategy
When analyzing Power Platform integrations, always identify the user-facing component (App) first, then the data/access layer (Connector), and finally the automation layer (Flow). Remember that Apps connect via Connectors.
Frequently Asked Questions
Does a Power App call a Flow directly?
Technically, an App calls a Connector. That Connector can then trigger a Flow. The exam distinguishes these layers.
What is the difference between a Connector and a Flow?
A Connector provides access to data sources and services. A Flow is an automated workflow that performs actions using those connectors.
Related Analysis
Practice All PL-900 Questions
Access 130 questions with complete answers and detailed explanations.
View Full PL-900 Practice Test →