What business rule application requirement would lead a Rule Developer to implement their own UrTraceDAO ,in order to create a custom DAO for storing execution traces?

Question

Options

• AThe business rule application must provide a full log of all the rules that were executed.
• BThe business rule application must provide evidence to auditors of how decisions were
• CThe business rule application must provide System Administrators with a way to roll
• DThe business rule application must provide the business users with data in the format

• A
  5% (2)
• B
  2% (1)
• C
  12% (5)
• D
  81% (34)

Explanation

Option D is correct because a custom UrTraceDAO is a Data Access Object - its purpose is to control how and where trace data is stored. When business users require execution trace data in a specific, non-default format (e.g., a particular database schema, XML structure, or proprietary system), the default DAO cannot satisfy that requirement, so the developer must implement their own.

Why the distractors are wrong:

• A (full log of all executed rules) is achievable using the standard trace facility without customizing the DAO - logging coverage is a what, not a how.
• B (audit evidence for auditors) similarly doesn't require a custom DAO; the default trace output can satisfy auditors without reformatting the underlying storage mechanism.
• C (rollback capability for System Administrators) is a transaction/state management concern, completely unrelated to trace storage - rolling back rule execution state is not a DAO responsibility.

Memory tip: Think of the DAO as the "pipe fitting" between the rules engine and your data store. You only need a custom fitting when the shape (format) of what you're storing must change to fit your business users' system - making D the only scenario that targets the storage format itself.

No community discussion yet for this question.