Question 2
Consider a rule based pricing system that allows for different pricing strategies to be used based on different types of corporate policies:
Lowest possible nationally available price on all products for government customers
Price based on contract at highest hierarchical relationship
Lowest price for a particular category of products
Customers have types such as government, preferred, or new. Hierarchy means that a customer can have a contract with a vendor at levels such as global, regional or direct. Categories are properties of the product being priced such as safety, health, or clothing of which products may have more than one. The rules are organized into packages for each of the categories mentioned in this paragraph but are executed in different sequences based on the strategy that applies to the customer’s order. The vendor has about 1000 customers and 3000 products.
Consider a problem where a government customer does not receive the lowest national price for a product and an application developer is tasked with figuring out why they are not receiving the correct price.
Which set of actions leverages the list of capabilities for understanding the rule logic when the system is still in the pre-production testing phase?
1. Use the Business Console to examine decision trace.
2. Isolate the rules related to government pricing and execute them without a rule flow.
3. Add the rules back into the full rule flow and test that the rules work in the context of the other logic in the flow.
4. Use verbose Rule Execution Server logging and inspect the log files.
1. Isolate the rules related to government pricing and execute them without a rule flow.
2. Add the rules back into the full rule flow and test that the rules work in the context of the other logic in the flow.
3. Use the Decision Warehouse to examine decision trace.
4. Use verbose Rule Execution Server logging and inspect the log files.
1. Remove all of the conditions from the rules that are not firing and call the rules and test that the rules work in the context of the other logic without any conditions in the flow.
2. Add the conditions back into the rules and test that the rules work in the context of the other logic in the flow.
3. Use the Decision Warehouse to examine decision trace.
4. Use verbose Rule Execution Server logging and inspect the log files.
1. Remove all of the conditions from the rules that are not firing and call the rules and test that the rules work in the context of the other logic without any conditions in the flow.
2. Isolate the rules related to government pricing and execute them without a rule flow.
3. Use the Decision Warehouse to examine decision trace.
4. Run the Rule Designer Debugger and inspect working memory.
5. Use verbose Rule Execution Server logging and inspect the log files.
Correct answer: D