PersonAccount -> Individual <- Employee. This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
The Core Concept Explained: The Public Sector data model builds on Salesforce's account, contact, person account, user, and industry objects. Choosing the correct anchor object prevents later sharing and reporting rework.
Step-by-Step Technical Analysis: Resolve the party and record model first because later configuration depends on it. Identify whether the scenario describes a person, business, employee, application, authorization, or funding record, then connect it to the standard or Public Sector object that owns relationships, sharing, reporting, and automation. Link Employee to Individual while the Individual is connected to the Person Account.

Keeping business rules in configurable metadata or other declarative configuration allows administrators to introduce new license types without changing automation logic. Flow simply evaluates the configuration and applies the correct process. Hard-coded logic and multiple Flows increase maintenance, while manual decisions reduce consistency.

This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
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.
Use a Decision Matrix to map those input combinations to the correct fee amount.

This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Experience Cloud design is driven by persona, authentication, scale, and sharing. The wrong template or license can create unnecessary cost, weak security, or excessive customization.
Step-by-Step Technical Analysis: Begin with the external persona, authentication requirement, and transaction volume. Select the Experience Cloud license or template that matches that access pattern, then configure sharing sets, external OWD, site visibility, and page access. Finish by testing the experience as anonymous, authenticated, and internal users. Use the sequence Plan, Engage, Apply, Review, Award, Manage, and Close Out. For exam preparation, validate the answer by tracing the record lifecycle, the user persona, and the automation owner from intake through reporting.

This selection keeps the implementation declarative and within the intended Public Sector operating model.
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.
Define the data type under Add Resource in the Expression Set.