Drag and Drop Question A company uses Power Apps to create maintenance requests. The maintenance manager emails the manager of the department noted in the request. The maintenance manager wants to…

Question

Answer Area

Explanation

This question tests knowledge of Power Automate cloud flow structure and the ability to distinguish cloud flow components from Business Process Flow components. The correct sequence reflects how an automated cloud flow must be constructed: a trigger to start it, an action to retrieve data, and a condition to route logic before sending the email.

Approach. A Power Automate cloud flow always begins with a Trigger - in this case, 'When an item is created' (e.g., in SharePoint or Dataverse where Power Apps stores the maintenance request). Next, an Action is added to look up the department manager's email address, such as using the 'Get manager (V2)' action from the Office 365 Users connector based on the department in the request. Finally, a Condition checks whether the lookup succeeded or validates the data (e.g., 'Is email not empty?'), branching into Yes/No paths so the email is only sent when valid data exists. This Trigger → Action → Condition sequence is the standard pattern for data-enrichment flows with conditional logic.

Concept tested. Understanding the structural components of a Power Automate cloud flow (Trigger, Action, Condition) versus Business Process Flow components (Stage, Data Step). Stage and Data Step belong exclusively to Business Process Flows, which guide users through structured phases - they have no place in an automated cloud flow that sends emails.

Reference. Microsoft Learn: 'Create a cloud flow in Power Automate' and 'Business process flows overview' - docs.microsoft.com/power-automate

No community discussion yet for this question.