Salesforce defines Expression Sets and Decision Matrices as the key components of Business Rules Engine and explicitly establishes their relationship. Expression Sets perform a sequence of calculations using matrix lookups, user-defined variables, constants, conditional logic, and other BRE elements. During execution, an Expression Set can call a Decision Matrix , which stores business rules as a structured table of input and output values.
A Decision Matrix does not itself perform the sequence of calculations described in option A. Instead, it accepts input values, locates the table row that satisfies those values, and returns the corresponding output. That behavior makes option C reversed: matching inputs to rows is the responsibility of the Decision Matrix, not the Expression Set.
Option D is also technically incorrect. Salesforce documents that Expression Sets and Decision Matrices can receive JSON input from OmniScripts and return JSON output , not XML input.
This architecture is particularly effective for Public Sector licensing because frequently changing regulatory criteria, fee schedules, eligibility conditions, and authorization rules can be maintained declaratively in Decision Matrices while Expression Sets orchestrate the calculations and matrix lookups.
Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Decision Matrices; matrix lookups; JSON integration with OmniScripts.
================
