The Process Abstraction pattern can help solve which of the following problems?

Question

Options

• AWhen business process logic is physically distributed across independent service
• BThe same business rules may exist within different business-centric services, leading to
• CGrouping non-agnostic business logic together with agnostic business logic hinders the
• DBundling both messaging and validation logic into the same service eventually results in the

• A
  12% (8)
• B
  5% (3)
• C
  77% (50)
• D
  6% (4)

Explanation

Option C is correct because the Process Abstraction pattern exists precisely to separate non-agnostic business process logic (workflow-specific steps, orchestration sequences) from agnostic logic (reusable capabilities like validation or entity management). When these are bundled together, agnostic services become polluted with process-specific concerns, destroying their reusability across the enterprise.

Why the distractors are wrong:

• A describes a distributed process logic problem - that's addressed by Process Centralization (consolidating logic into an orchestration layer), not Process Abstraction.
• B describes duplicated business rules across services - that's a Logic Centralization or canonical service problem, solved by entity/utility services.
• D describes coupling messaging and validation - that's a Service Granularity or decomposition concern, not specific to Process Abstraction.

Memory tip: Think of it as the "separation of concerns for services." The word Abstraction is the hint - you're abstracting the process away from reusable logic. If you see "non-agnostic mixed with agnostic," that's always the Process Abstraction pattern's territory, because its whole job is to give non-agnostic workflow logic its own home so agnostic services stay clean and reusable.

No community discussion yet for this question.