Exam PL-200 topic 3 question 20 discussion

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/apply-business-logic-with-code

To implement complex business logic that works across multiple Dataverse tables, returns a value after completion, and can be run from an existing Dataverse action, you should recommend: B. Custom API A Custom API allows you to define custom operations that can be invoked from Dataverse actions, providing the flexibility needed to implement complex business logic12. This method supports returning values and can be used across multiple tables.

Unbound action: This type of action is not tied to a specific table and can be invoked independently. While it can implement complex business logic and be called from various contexts, it doesn’t inherently return a value after execution, which is a requirement in your scenario. Custom API: This provides more flexibility and control. It allows you to define custom operations that can be invoked from Dataverse actions, work across multiple tables, and return values upon completion. This makes it a better fit for your needs, especially since you need the operation to return a value and be callable from an existing Dataverse action. So, a Custom API is recommended because it meets all your requirements: working across multiple tables, returning a value, and being callable from existing actions.

https://venkatasubbaraopolisetty.com/2022/03/25/power-automate-fundamentals-66-understand-unbound-action-in-power-automate/

unbound action C

i think its unbound action because it says in the text "The new business logic must work in multiple Dataverse tables".

B. Custom API. A bound action is a type of custom action that is associated with a specific table or entity. It cannot work in multiple Dataverse tables, and it cannot run from an existing Dataverse action. An unbound action is a type of custom action that is not associated with any table or entity. It can work in multiple Dataverse tables, but it cannot run from an existing Dataverse action. A scheduled workflow is a type of cloud flow that performs one or more tasks on a schedule. It cannot work in multiple Dataverse tables, return a value after it finishes, or run from an existing Dataverse action.

Bound Action or Unbound Action are extensions to out-of-the-box operation of data to Dataverse. This question mentions multi-tables, so it should be Unbound Action. Bound Action is for a single table.

On exam 5/23

ChatGPT says Custom API Explanation: Using a Bound or Unbound action may not meet your requirements as they are typically used to implement simple, reusable actions that operate on a single table or entity. Scheduled workflows may not meet your requirement for returning a value after they finish, as they are typically used to automate tasks that do not require user interaction or input.

https://learn.microsoft.com/en-us/power-automate/dataverse/bound-unbound https://www.youtube.com/watch?v=qU-ENcZyRoM

In addition, the operation must return a value after it finishes?

The question states two things: 1) Must work in multiple Dataverse tables 2) Must be able to run from an existing Dataverse action That is: there is already an ACTION that needs to be called. So it can only be Bound/Unboud Action. Also, it needs to be performed for several tables, so it can only be Unboud (not related to a specific table)

can someone please explain to me what an unbound actions is

i feel this should be custom API?

C seems to be the answer

Correct answer