A large enterprise has multiple decision services from different business units using Decision Center as the source of truth to maintain their rules. Some of these projects have customized Decision…

Question

Options

• ATo test customizations
• BTo test product updates and ifixes
• CTo test the behavior of large decision tables
• DTo develop and encourage POCs away from production
• ETo simulate new complex rule ideas away from production

• A
  79% (33)
• C
  2% (1)
• D
  7% (3)
• E
  12% (5)

Explanation

Options A and B are correct because they address the two primary system-stability risks specific to this customer's situation: customized Decision Center environments can break unexpectedly when product updates or ifixes are applied, and untested customizations can corrupt or destabilize the platform entirely. Testing both in non-production first directly prevents the scenario where a live production Decision Center becomes inaccessible to all business units simultaneously.

Why C is wrong: Testing large decision tables is a content/performance concern, not a platform-stability concern - it does not risk taking Decision Center offline or interrupting access for other users.

Why D and E are wrong: POCs and experimenting with new rule ideas are general authoring best practices but do not pose a risk of system-level interruption to Decision Center itself; they belong in non-production for governance reasons, not availability reasons.

Memory tip: Anchor on the phrase "minimize interruption to access" - only changes to the platform itself (customizations + software updates/ifixes) can take the whole system down. Anything that's just authoring content (tables, rules, POCs) is lower risk. If the reason involves changing how Decision Center behaves or runs, it belongs in non-prod first.

No community discussion yet for this question.