The Bottom Line (Direct Answer): Answer: A, C, D — A (Create an Application Form using OmniScript Designer); C (Create an Expression Set using BRE); D (Create a Decision Matrix using BRE). This is the lowest-customization answer that still satisfies the business, security, and lifecycle requirements.
The Core Concept Explained: Business Rules Engine externalizes decision logic from custom code. Expression Sets orchestrate calculations and can call decision assets so policy thresholds remain maintainable by authorized business users.
Step-by-Step Technical Analysis: Identify the inputs that drive the decision, declare them as Expression Set resources, and use Decision Matrices or Decision Tables where business users must maintain rule thresholds. Execute representative samples before activation, then confirm the output and Decision Explainer history match the expected eligibility, fee, or prioritization result. Create the application form with OmniScript, build an Expression Set in Business Rules Engine, and create a Decision Matrix for the eligibility or scoring rules.
Why the Incorrect Options Are Wrong: B shifts the process onto Case even though the scenario is centered on application, license, permit, grant, or inspection records. E may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.
