How can a developer design rule application to simplify the number of rules and the impact of multiple deployments so that unchanged rules are not duplicated?

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 2-3 additional types of taxes. Also, these 15 states have different regulations and need to update taxes on a monthly basis.

How can a developer design rule application to simplify the number of rules and the impact of multiple deployments so that unchanged rules are not duplicated?
A . Organize tax rules in a common rule project to address taxes for the states sharing the same logic. Create a separate rule project for every state where taxes calculations are unique. Override common rules with unique rules from this separate rule project.
B . Create a rule project for every state to include its own tax rules. Package all rule projects into a single RuleApp with multiple rulesets.
C . Create a rule project with only the rules of one state and use these rules as the only ruleset of a RuleApp.
D . Create a rule project with a single decision table with all states listed and the tax logic for every state in separate virtual methods from the BOM that can be used in the table. Use this rule project as the only ruleset in the RuleApp.

View Answer

Answer: B