A company plans to create an order processing app. When orders are created, the app will perform complex business logic and integrate with several external systems.
Orders that have a large number of line items may take up to six minutes to complete. Processing for each order must be completed in one operation to avoid leaving records in an incomplete state.
You need to recommend a solution for the company.
What should you recommend?
Given the constraints of the problem, the solution must handle potentially long-running operations up to six minutes without leaving records in an incomplete state. Since processing must be completed in one operation, an asynchronous mechanism that can handle long-running transactions is necessary. An asynchronous workflow does not guarantee the operation will complete in one session. Similarly, real-time workflows and custom actions have a timeout that makes them unsuitable for operations exceeding two minutes. Webhooks connecting to an Azure Function are capable of handling longer durations and complex business logic and providing the necessary level of integration with external systems. Thus, a webhook that connects to an Azure Function is the best recommendation for this scenario.
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
I checked also in measure up website teh solution is C webhook and azure functions
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
C is the right answer. Both plugins and workflows have a 2 minute execution limit.
I agree - C is a better option - the plugin and the custom action will have a 2 minute limit. That said the webhook and azure function won't provide transactional rollback - unless it is coded to do so. This is a typical MS BS question.... overly elaborate question set up and then none of the answers are very good.
"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.
What will be the right answer? B or C
I too thought the answer was C. But... Yes, I agree workflows and Plugins have a 2 minute time out but real time workflow makes the user wait. Maybe the answer is really B because real time workflow is the only place where the operation will be rolled back. With Azure function, if something fails no roll back will take place.
everyone forgot on-prem? timeouts? what timeouts.. I know I know given the certification and exam context these days, so yeah could be that the given answer is indeed correct.
Due to the 2 min timeout, answer is C
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
ChatGPD said D. C is a possible solution, but not best
ChatGPD changed mind, should C since D may cause delays in processing if there are a large number of line items to process, which could result in incomplete records.
it can never be asynchronous because the requirement said it needs to be done in one operation. asynch means it can be done in many operations running at different times
it can never be asynchronous because the requirement said it needs to be done in one operation. asynch means it can be done in many operations running at different times
B will be correct as real-time workflow will rollback all changes in case of failures.
Answers will be a webhook that connects to an Azure Function.
Answer is C
My guess is C too.
C due to the 2min timeout.
Answer should be: A. an asynchronous workflow that uses a custom workflow activity Async workflow has no timeout and custom workflow activity runs in a transaction.
My guess: C
C looks overkill with azure function. this is power platform exam. not azure.
A webhook is registered using the plugin registration tool, what's the problem?
it is not correct in my opinion
2 min timeout for plugins, CWA etc... You can go with C by just excluding the other 3 options
C is the correct answer
C should be correct
Sandbox limitation is 2 minutes, and here said that execution could take up to 6 minutes. So it should be C.
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?
After reconsidering, due to the 2min timeout with plug-ins perhaps webhooks in conjunction with Azure Functions is a better approach.
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.
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.
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.