In the "Results" picklist field of the Inspection Assessment Indicator object, edit the "Fail" and "Issue" picklist values and.. This selection keeps the implementation declarative and within the intended Public Sector operating model.
The Core Concept Explained: Action Plans standardize repeatable work. They package tasks, dependencies, due dates, and document checklist requirements so staff do not rely on memory or one-off manual steps.
Step-by-Step Technical Analysis: Start by defining the target object that owns the operational work. Build or select the Action Plan Template, add the required tasks or Document Checklist Items, publish the template, and then automate or guide its association to the live record. Test that owners, due dates, dependencies, and applicant-facing upload prompts behave correctly. Configure the appropriate assessment question status/result picklist value to create a violation when selected.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

Plan, Engage, Apply, Review, Award, Manage and Close Out. 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.
Why the Incorrect Options Are Wrong: A uses the wrong packaged object or module boundary for this scenario. C uses the wrong packaged object or module boundary for this scenario. D uses the wrong packaged object or module boundary for this scenario.

Once published, an Action Plan template cannot be changed. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Action Plans standardize repeatable work. They package tasks, dependencies, due dates, and document checklist requirements so staff do not rely on memory or one-off manual steps.
Step-by-Step Technical Analysis: Start by defining the target object that owns the operational work. Build or select the Action Plan Template, add the required tasks or Document Checklist Items, publish the template, and then automate or guide its association to the live record. Test that owners, due dates, dependencies, and applicant-facing upload prompts behave correctly. Once a template is published, it cannot be edited directly.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. B may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

Integration Procedures. This maps the scenario to the Salesforce-native capability that owns the requirement.
The Core Concept Explained: Start by recognizing that the widget needs orchestration, not only display. OmniStudio separates guided interaction, data mapping, orchestration, and UI presentation. That separation is critical for high-volume public-sector intake because each asset can be tested and reused independently.
Step-by-Step Technical Analysis: Design the user journey first, then decide which OmniStudio asset owns each responsibility. OmniScript captures guided input, DataRaptors map Salesforce data, Integration Procedures orchestrate server-side work, and FlexCards expose summarized context. After assembly, validate data payloads, error handling, security, and performance with realistic application records. Use an Integration Procedure because it can declaratively orchestrate DataRaptor Extract actions, remote actions, calculations, conditional logic, and response shaping.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

Expression sets call decision matrices, which are tables that allow implementing of complex rules in a systematic, readable way. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
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. Build the Expression Set to call one or more Decision Matrices when the process needs complex, systematic, readable rules.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. B may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.