Exam PL-400 topic 1 question 8 discussion

Definitely C. Custom actions have a 2 min timeout. This can be implemented using webhook and Azure function where the Azure function uses batch operations Web API which enables transactional operations and can run more than 2 mins https://docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/execute-batch-operations-using-web-api

C seems correct

synchronous plug-ins run in the background and support long-running operations (up to 2 minutes per execution cycle, but can chain/queue for more). Ideal for: Heavy business logic External system integration (e.g., via web services) Error handling and retries Since they execute outside the main transaction, they avoid blocking the UI and won’t timeout like synchronous plug-ins (which have a strict 2-minute timeout limit). You can use batching or queues to handle more complex or multi-stage orders safely.

Asynchronous plug-ins can still be designed to ensure complete processing — just not within the same transaction context as the user action. Asynchronous plug-ins: Run outside the main transaction, so the create operation completes first. Still execute the full logic in one operation and can be designed to ensure no partial writes (e.g., via scoped logic or retry mechanisms). Can handle long-running operations (like 6 mins), and are much better for external system integrations. So, what does "completed in one operation" really mean here? It means the business logic must be completed as a cohesive unit — it doesn’t necessarily mean it must be transactional or synchronous. The key is ensuring no partial data, not that the process must finish before the create completes.

B and C are less suitable because they both imply real-time processing, which might not be ideal for long-running operations and could potentially impact system performance and user experience. While D, an asynchronous plug-in, could be an alternative but might not provide the same level of flexibility and control over the processing flow as a custom workflow activity.

With plug-ins you can handle complex business logic, integrate with external systems, do synch processing, avoid delays and records are not left in incomplete state. They are native features of the Dynamics 365 and Dataverse, providing seamless integration and execution. Why would you introduce additional layer of complexity and potential points of failure by using webhooks?

Sandbox limitation is 2 minutes, and here said that execution could take up to 6 minutes. So it should be C.

what answer is the right answer ? most of websites saying its a realtime and you guys saying here webhook its really confusing and i dont know how i can pass if this website answering wrong or right

ChatGPD said D. C is a possible solution, but not best

C should be correct

I checked also in measure up website teh solution is C webhook and azure functions

"Processing for each order must be completed in one operation to avoid leaving records in an incomplete state" Real-time workflow action is the only option that will roll back if it fails and avoid leaving record in an incomplete state.

Check out this doc : https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-own-actions?view=op-9-1 Have a look on "Watch Out" section. It says no limit for Custom Action in real time workflow. But below that statement there is a tip "long running operations should be run outside of Crm 365". I would go for B but in real life I would push C as much as I can

C is the correct answer

2 min timeout for plugins, CWA etc... You can go with C by just excluding the other 3 options

Due to the 2 min timeout, answer is C

C looks overkill with azure function. this is power platform exam. not azure.