A company uses Dynamics 365 finance and operations apps. The company must implement efficient business events to allow an external system to subscribe to events coming from Dynamics 365 finance and…

Question

Options

• AHTTP time-out
• BEndpoints allowed per event
• CProcessing threads
• DBundle size
• ERetry count

• A
  9% (4)
• B
  5% (2)
• C
  72% (31)
• E
  14% (6)

Explanation

Business events, Performance The business events framework has two primary settings that can affect performance: Processing threads and Bundle size. The application allocates dedicated batch threads to process business events in near-real time. Because threads are a shared resource for all batch processing, you must take care when you decide to change the thread allocation for business events. * Processing threads - The number of threads to use to process business events. With dedicated processing for business events, the thread count is the number per Batch Application Object Server (AOS) instance. The maximum value is 4. * Bundle size - The number of events to group together at a time for processing by a thread. By increasing the number, you produce fewer bundles and reduce the ability to distribute the events to parallel threads. By decreasing the number, you produce more bundles and increase the ability to distribute the events to parallel threads. However, if you make the number too small, you will cause unnecessary parallelization on small bundles. Note: Business events provide a mechanism that lets external systems receive notifications from finance and operations apps. In this way, business actions can be performed in response to the business events. Business events occur when a business process is run. During a business process, users who participate in it perform business actions to complete the tasks that make up the business A business action that a user performs can be either a workflow action or a non-workflow action. Approval of a purchase requisition is an example of a workflow action, whereas confirmation of a purchase order is an example of a non-workflow action. Both types of actions can generate business events that external systems can use in integration and notification scenarios. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/business-events/home-

No community discussion yet for this question.