Salesforce AP-222 Exam Questions

For administrator-controlled registration, the Contact page layout should include the Enable Customer User action. This allows an authorized internal user to manually provision an Experience Cloud login from the constituent's Contact record rather than permitting visitors to create their own accounts.

Salesforce's documented manual-registration process instructs administrators to open Contact page-layout configuration and add Enable Customer User and, where appropriate, View Customer User. An administrator then opens the participant's Contact record, selects Enable Customer User, and specifies the username, profile, and other required user information. Current Salesforce guidance also confirms that Manage External Users functionality includes the Enable Customer User action and that these actions appear individually on Contact layouts in Lightning Experience. Self-registration would directly contradict the requirement because it allows external visitors to initiate account creation. There is no separate standard Contact action named Register User that replaces the established external-user provisioning mechanism described here. This configuration gives the PSO controlled onboarding of grantseekers while still allowing the resulting users to authenticate to the Grants Management Experience Cloud site after their accounts are provisioned.

Study Guide Reference: Grants Management; Experience Cloud User Administration; Manual Registration; Contact Page Layout; Enable Customer User.

Public Sector distinguishes between organizations and individual constituents through its account model. Salesforce explicitly recommends Business Accounts for businesses and Person Accounts for individual people. Person Accounts combine relevant Account and Contact information into a single constituent record and are intended for individuals applying for licenses, permits, programs, benefits, grants, and government services.

Because the agency is intentionally implementing its regulatory program in phases, it can first configure the business-oriented data model and processes for business constituents. Business Accounts and related Contacts support organizational applicants and associated representatives. When the agency is ready to extend services to individual private constituents, it can introduce the Person Account model and configure the corresponding individual application experiences. A Household Account is not the primary model for an individual constituent. Salesforce's relationship model uses Person Accounts to represent individual people and can optionally associate those people with business-account-based household structures when the business requirement calls for household modeling. Implementing both constituent models immediately would also contradict the agency's stated phased rollout objective and unnecessarily expand the first release scope.

Study Guide Reference: Public Sector Data Model; Business Accounts; Contacts; Person Accounts; Constituent Modeling; Phased LPI Implementation.

DataRaptor---called OmniStudio Data Mapper in current Salesforce terminology---provides the declarative data-mapping capability required to convert incoming application data into records on Salesforce objects.

A Data Mapper Load accepts JSON, XML, or custom-formatted input and creates or updates Salesforce records according to configured field mappings. Salesforce explicitly states that Data Mapper Load writes input data to Salesforce objects and can populate multiple mapped records without requiring custom Apex. This capability is particularly relevant when the source application runs outside Salesforce. Salesforce provides a Data Mapper REST API through which an external system can issue a POST request containing the application payload and invoke a Data Mapper Load to update the appropriate Salesforce objects. For the agency, grant application information collected in the existing external portal can therefore be transformed and mapped into Agentforce Public Sector records such as constituent, application, or funding-related objects. Integration Procedures provide broader server-side orchestration and can themselves invoke Data Mappers, but the specific requirement emphasized here is mapping submitted data into Salesforce objects. FlexCards are presentation components, while OmniOut is primarily used to run OmniStudio UI components outside Salesforce rather than serving as the direct object-mapping mechanism.

Study Guide Reference: OmniStudio DataRaptors/Data Mappers; Data Mapper Load; REST API; External Portal Integration; Public Sector Grant Application Data Mapping.

Decision Explainer is the Public Sector capability used to provide transparency into calculations performed by Business Rules Engine. Salesforce describes it as a collection of setup objects that helps users understand why a business rule produced a specific result. This is particularly important in government processes where eligibility, benefits, fees, or prioritization decisions must be explainable and auditable.

Salesforce specifically identifies individual and business application fees, unemployment benefits, and housing loan eligibility checks as Public Sector examples where Decision Explainer can provide insight into Business Rules Engine calculations. Decision Explainer works with Expression Sets and their execution data so authorized users can examine the variables and calculations contributing to a determination. This capability supports transparency in benefits administration because reviewers can trace a calculated result rather than treating automated policy decisions as a black box. The same architecture is applicable to fee calculations and eligibility checks because these processes commonly use Decision Matrices and Expression Sets to evaluate constituent information against government policy.

Study Guide Reference: Decision Explainer with Public Sector; Business Rules Engine; Expression Sets; Application Fee Calculations; Benefit and Eligibility Decisions.

A (Employee Experience Community Access); B (Employee Productivity Plus Access); E (Employee Experience for Public Sector). This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.

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. Assign Employee Experience Community Access, Employee Productivity Plus Access, and Employee Experience for Public Sector.

Why the Incorrect Options Are Wrong: 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.