The requirements of a process being implemented are such that it is required to run multiple paths in parallel. What type of artifact should the integration developer use to implement the process?

Question

Options

• AMicroflow
• BLong running process
• CSelector with multiple selection criteria
• DMediation flow with fan-in/fan-out components

• A
  6% (2)
• B
  81% (25)
• C
  10% (3)
• D
  3% (1)

Explanation

Long running processes are specifically designed to orchestrate complex workflows that require spawning and managing multiple concurrent execution paths, making them the correct artifact for this requirement. They can fork into parallel branches, coordinate their execution, and wait for all paths to complete before proceeding - capabilities that are fundamental to parallel processing.

Why the distractors are wrong:

• (A) Microflow executes as a single, short-lived synchronous transaction - it runs one path sequentially and cannot branch into parallel execution.
• (C) Selector with multiple selection criteria is a routing artifact that directs flow to one path based on matching rules - it picks between paths, not runs them in parallel.
• (D) Mediation flow with fan-in/fan-out handles message distribution and aggregation for service mediation (routing/transformation), but is not designed for orchestrating parallel process paths with stateful coordination.

Memory tip: Think of it this way - "long" implies duration and complexity. Parallel paths take time and coordination across multiple transactions, which is exactly what a long running process is built to handle. Short = microflow (one shot), Long = orchestration with forks.

No community discussion yet for this question.