AP-222 Exam Dumps - Salesforce Accredited Agentforce 360 for Public Sector Professional

The Employee Experience implementation represented by this question requires three complementary access layers: Employee Experience Community Access , Employee Productivity Plus Access , and Employee Experience for Public Sector .

Employee Experience for Public Sector grants access to Public Sector employee-specific objects and capabilities. Salesforce's release documentation states that employees need this permission set to access the Public Sector objects and features associated with Employee Experience.

Employee Productivity Plus Access supplies employee productivity functionality and UI-component access. Salesforce's HR Service Center permissions reference confirms that this permission set provides read access to onboarding tasks and user-interface components and requires the Employee Productivity Plus entitlement.

Employee Experience Community Access is the package-era permission used to provide the employee with access to the digital Employee Experience environment itself. Together, these three permissions establish community/site access, employee productivity capability, and Public Sector-specific employee functionality.

Employee Productivity Plus User Data Access provides a different data-access layer used in HR Service Center scenarios and isn't one of the three permission sets identified for accessing this prebuilt Public Sector Employee Experience application. Public Sector Solutions User Access is likewise broader and doesn't replace the Employee Experience-specific permission assignment.

Salesforce's employee-product naming has evolved in current releases toward Employee Service and unified employee licensing, but B, C, and D correspond to the architecture tested by this item.

Study Guide Reference: Public Sector Solution Product Configuration – Employee Experience for Public Sector; Employee Experience Community Access; Employee Productivity Plus; permission configuration.

Expression Sets use resources such as variables and constants to hold values used during calculations and rule execution. When an administrator creates or adds a resource in an Expression Set version, the resource is assigned an appropriate data type. Salesforce officially lists Currency as a supported Expression Set resource data type, together with Text, Number, Percent, Date, Date & Time, and Boolean.

Therefore, the administrator should configure the value through Add Resource in the Expression Set , making option C correct. A Currency resource supports numerical comparison operators including equals, not equals, less than, greater than, and their inclusive variants, making it suitable for licensing fee calculations.

Decision tables can also contain currency-compatible fields in supported Business Rules Engine scenarios, but the question asks specifically where the administrator establishes the data type for a resource within an Expression Set . That configuration occurs in the resource definition rather than through OmniScript options.

Salesforce explains that variables and constants are resources that hold dynamic or fixed values and are used as inputs, outputs, and intermediate values throughout expression-set execution.

Process Builder entry criteria are unrelated to Business Rules Engine resource typing.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Resource Manager; variables and constants; Currency data type; licensing fee calculations.

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

Grants Management and Outbound Funds Module provide the Salesforce-native funding architecture represented by this scenario. Salesforce states that Grants Management uses the Outbound Funds Module data model , which includes Funding Programs, Funding Requests, Reviews, Requirements, Disbursements, and related financial-tracking entities.

The grantseeker's submitted application is represented by a Funding Request . Review records capture the reviewers' status and feedback, while Disbursement records represent funds that have been made or are scheduled to be made to the recipient. Salesforce's Outbound Funds documentation specifically states that the module manages Funding Requests and outgoing funds and can create disbursements for expenditures.

For more detailed expenditure accounting, the Outbound Funds data model includes GAU Expenditure , which connects a Disbursement to a General Accounting Unit and identifies which allocation or accounting category funded the disbursement. This supports audit scenarios in which expenditures need to be distinguished among categories such as mortgage arrearage and utility assistance.

FinancialForce Accounting is an external accounting solution and is not required by this Public Sector design. Nonprofit Success Pack can extend certain GAU functionality, but selecting NPSP alone would not replace the Grants Management/Outbound Funds framework specified by the scenario.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management; Outbound Funds Module; Funding Requests; Disbursements; GAU Expenditures.

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

Salesforce's official Grants Management installation prerequisites directly support B, C, and E . Grants Management requires the appropriate Grants Management licensing together with Customer Community Plus Login licenses for the external grantseeker experience. Salesforce also requires Lightning Experience and Chatter to be enabled.

Therefore, because the agency's employees currently operate in Salesforce Classic, they must move to Lightning Experience to use the supported Grants Management experience. Chatter must also be enabled because the package depends on Salesforce collaboration functionality. For the external grant portal, Customer Community Plus provides the supported external-user licensing required by the managed-package implementation.

The distinction between options B and D is significant. Although Customer Community is appropriate for many high-volume constituent portals, the Grants Management managed-package prerequisites specifically identify Customer Community Plus Login licensing. This is therefore a product-specific requirement, not merely a generic Experience Cloud licensing choice.

Web-to-Lead concerns conversion of public web submissions into Lead records and has no role in installing or enabling Grants Management.

Salesforce additionally lists Digital Experiences and My Domain among the overall prerequisites, although those choices are not provided in this question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Grants Management installation; Experience Cloud; Customer Community Plus; Chatter; Lightning Experience.

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

Public Complaint and Case are the native Public Sector objects designed for this separation of external reporting from internal investigation. A Public Complaint records the concern submitted by a constituent, including health, safety, behavior, or well-being issues. Salesforce supports Public Complaint intake and subsequently allows staff to create a separate Case associated with the complaint when investigation or ongoing case management is required.

This architecture satisfies an important data-model requirement: the initial complaint and the internal investigative Case remain separate records but are related. Salesforce also provides the ComplaintCase junction object internally to associate complaints and Cases; this does not mean that "Complaint Case" is the principal constituent-facing object, making option D incorrect.

Using two Case record types would collapse two different Public Sector concepts into the generic Case object and discard purpose-built complaint functionality. Creating a custom complaint object would likewise duplicate capabilities already supplied by the Public Sector data model and increase maintenance.

The Public Complaint model also supports scenarios where a reporting party doesn't need to be treated as the subject of the investigative Case, which is particularly appropriate for anonymously submitted public concerns.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Public Complaints; ComplaintCase; Case Management; constituent complaint intake and investigations.

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

A high-volume grant window creates a capacity and transaction-load problem , so the implementation must reduce synchronous processing, optimize content delivery, and validate the architecture at anticipated peak volume.

First, computationally expensive operations should be moved away from the synchronous user transaction when possible. Salesforce's high-volume Experience Cloud architecture uses asynchronous processing and micro-batching to prevent heavy record creation and processing from blocking interactive requests during traffic spikes.

Second, Salesforce specifically identifies Content Delivery Network (CDN), caching, Lightning Web Runtime, Apex caching, and progressive rendering among its Experience Cloud performance and scale optimization tools. CDN and caching reduce repeated server processing and improve the delivery of static or reusable resources during high traffic.

Third, the agency must test the expected peak workload rather than assuming functional UAT proves scalability. Salesforce identifies Scale Testing as an optimization tool for heavy transaction loads and customizations.

UAT remains necessary for functional acceptance but does not establish capacity under concurrent traffic. IP restrictions would deliberately restrict legitimate applicants rather than scale the application to serve the expected demand.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud scale; asynchronous processing; CDN; caching; high-volume transactions; performance and load testing.

Salesforce explicitly states that the Person Account model uses the standard Account object to hold the details about a person . In Public Sector, Person Accounts represent individual constituents who apply for licenses, permits, programs, benefits, grants, and government services.

A Person Account combines selected Account and Contact behavior into a single person-oriented record. Salesforce's Public Sector data-model documentation explains that this record can contain personhood information such as birth date and tax identification information and can relate directly to Cases, Individual Applications, and Public Complaints.

Option B is incorrect because Person Accounts combine Account and Contact characteristics, not Opportunity and Contract fields. Option C is incorrect because the Person Account record type is fundamental to the implementation; Salesforce explicitly identifies Person Account as an Account record type.

Option D is particularly important from an implementation-governance perspective. Salesforce warns that after Person Accounts are enabled in an organization, they cannot be disabled . This is why enabling them requires deliberate architectural planning and testing before activation.

For Public Sector, business constituents should normally be represented by Business Accounts, while individual constituents can use Person Accounts. This separation supports Public Sector data relationships while maintaining a consistent CRM data model.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Person Accounts; Account data model; constituents; Person Account record type; implementation considerations.

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

The three foundational configuration records are Business Type, Regulatory Authorization Type, and Regulatory Authority . Salesforce's regulatory authorization model defines Regulatory Authority as the government agency or department responsible for issuing and enforcing licenses and permits. Regulatory Authorization Type represents the specific license or permit, while Business Type identifies the category of business and activities that require regulatory authorization.

After these components exist, Public Sector uses the Business Regulatory Authorization Type junction object to map a Business Type to the applicable Regulatory Authorization Type. This establishes which licenses or permits are required for a given business activity.

A Business Profile is used to capture information about the applicant's business or individual during application processing, but it is not one of the three foundational authorization-definition records asked for here. Inspection Type belongs to inspection configuration and therefore is not necessary simply to define the license authorization.

Salesforce's configuration sequence explicitly includes creation of Regulatory Authorities, Regulatory Authorization Types, and Business Types as core elements of regulatory authorization setup.

Study Guide Reference: Public Sector Solution Product Configuration – Regulatory Authorization Model; Regulatory Authority; Regulatory Authorization Type; Business Type; Business Regulatory Authorization Type.

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