A customer needs to calculate sales taxes based on the state of origin for an online pricing solution. The customer identified 15 states in the US that have a different sales tax and also include…

Question

Options

• A
  • Organize tax rules in a common rule project to address taxes for the states sharing the
• B
  • Create a rule project for every state to include its own tax rules
• C
  • Create a rule project with only the rules of one state and use these rules as the only
• D
  • Create a rule project with a single decision table with all states listed and the tax logic

• A
  27% (16)
• B
  7% (4)
• C
  55% (33)
• D
  12% (7)

Explanation

Option C is correct because it leverages a single base rule project as the foundation, allowing state-specific rules to override only what differs - this means unchanged rules exist in one place and are not duplicated across deployments, directly satisfying the requirement to minimize redundancy and deployment impact.

Why the distractors are wrong:

• Option A (common rule project for shared states) partially addresses reuse but doesn't eliminate duplication for state-specific variations - states with unique logic would still require redundant copies of shared rules.
• Option B (separate rule project per state) is the worst option: it maximizes duplication since all 15 states would repeat identical logic, and monthly updates would require changes across every project.
• Option D (single decision table with all states) bundles everything into one artifact, meaning any monthly update to one state forces redeployment of the entire table - the opposite of isolated, minimal-impact changes.

Memory tip: Think "one base, override the rest." Just like class inheritance in OOP - a child class only defines what's different, not what it already inherits. Option C applies the same principle: one rule project as the canonical source, with state-specific exceptions layered on top.

No community discussion yet for this question.