Complete AP-222 Salesforce Materials

An OmniScript plus Decision Matrix provides the correct declarative architecture. OmniScript captures the constituent's answers through a guided, dynamic digital form, while the Decision Matrix stores the changeable business criteria used to determine which license type corresponds to those inputs.

Salesforce describes a Decision Matrix as a table containing input and output values. When invoked, the matrix identifies the row matching the supplied inputs and returns the corresponding output. Because thresholds and policy values are stored declaratively in matrix rows, administrators can update city/county conditions, revenue bands, building-size thresholds, and resulting license recommendations without rewriting Apex.

Salesforce also provides direct integration between OmniScripts and Decision Matrices. An OmniScript can pass selected input values to the matrix and capture the returned result in its JSON structure. This is analogous to Salesforce's documented Public Sector pattern in which constituent inputs from an OmniScript are evaluated against Business Rules Engine criteria to produce eligibility or fee results.

OmniChannel is a work-routing capability, not a public questionnaire framework. Einstein AI isn't appropriate for deterministic regulatory rules. LWC plus Apex could work but creates unnecessary code and maintenance.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScripts; Business Rules Engine; Decision Matrices; declarative eligibility and recommendation logic.

================

An Integration Procedure is the appropriate OmniStudio component when a solution must retrieve, combine, transform, and calculate data from multiple sources without custom Apex. Integration Procedures execute server-side and can orchestrate multiple data-access and transformation operations before returning a consolidated response to a FlexCard, OmniScript, Lightning component, or another consumer.

Salesforce defines OmniStudio Integration Procedures as components that can read and write data between Salesforce and external systems , while Data Mappers handle Salesforce data retrieval, transformation, and persistence. Integration Procedures can invoke multiple Data Mappers, conditional actions, calculations, HTTP actions, and other services within one declarative process.

That orchestration capability is particularly important when the records being aggregated aren't connected through one simple Salesforce relationship. The Integration Procedure can independently query each required data set, calculate or transform the results, merge the outputs into a JSON response, and provide the resulting data to the presentation widget.

SOQL is a query language, not a standalone declarative OmniStudio orchestration component. Apex could implement the requirement but introduces unnecessary custom code. MuleSoft is appropriate for enterprise integration scenarios but is excessive when the required aggregation can be handled natively through OmniStudio.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; Data Mappers/DataRaptors; server-side orchestration; data aggregation and transformation.

================

The appropriate relationship is PersonAccount → Individual ← Employee . Salesforce's Employee data model uses the Individual object as the common privacy and identity relationship point connecting employee information to other person-centric representations.

Salesforce documentation states that Employee records are related to Individual records and that an Individual connects employee data with privacy and consent information. The Work.com data-model documentation further explains that when another Salesforce solution represents a person through a Person Account, the Person Account can be linked to the Employee through the Individual record—specifically, PersonAccount > Individual < Employee .

This arrangement is particularly appropriate when Public Sector represents an individual constituent as a Person Account while the Employee data model separately maintains an Employee record. The Individual object provides the linking layer rather than requiring the Person Account to connect directly to User or Employee.

Option B is a valid pattern for solutions that represent people through Contacts, but it does not satisfy the scenario's explicit Person Account requirement. Option D incorrectly routes the relationship through User, while option A does not even use the standard Employee object.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Public Sector person data model; Employee data model; Person Accounts; Individual; Employee relationships.

================

The three controls address separate security layers: authentication, automated abuse protection, and record-level access .

Setting grant application pages to Requires Login restricts application workflows to authenticated Experience Cloud users. Salesforce documents the Page Access property for Experience Cloud pages and supports setting pages containing OmniScripts to Requires Login when workflows should only be available to authenticated users.

CAPTCHA or reCAPTCHA provides bot mitigation. Salesforce explicitly uses reCAPTCHA with Experience Cloud application-style forms to confirm that applications are submitted by humans rather than automated bots and recommends it for preventing misuse and spam.

Finally, external organization-wide defaults should be Private for sensitive grant application data. Salesforce's external-user security guidance recommends keeping external OWD settings Private wherever possible so authenticated external users don't automatically gain access to records belonging to other constituents. Additional sharing mechanisms can then selectively expose only the records each user is authorized to access.

A public application-reference search would create unnecessary information-disclosure risk. "Salesforce Spam Check" isn't the appropriate Experience Cloud control represented by this architecture.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud security; authentication; OmniScripts; CAPTCHA/reCAPTCHA; external OWD; privacy and record sharing.

================