Free Practice Questions for the Salesforce Accredited Professional Certification AP-222 Exam (2026 Updated)

Grants Management is the appropriate product because it includes the grantseeker portal experience required for external applicants to discover funding opportunities, apply online, supply application information, and manage their applications.

Salesforce describes the Grants Management managed package as providing program management, financial commitments, relationship management, and a grantee portal . The portal is specifically intended to improve the applicant/grantee experience while allowing grantmakers to manage the complete funding lifecycle.

Salesforce's portal setup documentation explains that the Grantee Portal Experience Cloud template provides a location where people can review available Funding Programs, apply to programs, and manage their applications. Grants Management also supports enhanced application flows, organization self-registration, application mapping, collaboration, and other functions beyond the lightweight funding-management capabilities of Outbound Funds Module.

This matches Foodvania's requirement for a constituent-facing relief application experience with supporting documentation and ongoing application management.

Outbound Funds Module supplies the underlying funding data model and can manage Funding Programs, Funding Requests, reviews, and disbursements. However, Grants Management provides the richer preconfigured portal and application experience targeted by the scenario. Therefore, it is unnecessary to combine the products as option A suggests simply to obtain the applicant-facing capabilities described.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management; Grantee/Grants Portal; Funding Programs; Funding Requests; application management and constituent self-service.

Public Sector already includes a standard object specifically designed for this requirement: Business Regulatory Authorization Type Dependency . Salesforce states that many businesses require multiple licenses or permits and that dependency records establish the relationships and issuance sequence among those authorizations. A parent authorization must be obtained before its dependent child authorization where such a dependency is configured.

Salesforce additionally provides a standard Permits component for the Licenses and Permits Experience Cloud site. The component displays the permits required for a selected business type, including configured permit dependencies. Therefore, the agency does not need to develop a custom Permit Dependency object, custom FlexCard, or custom OmniScript merely to reproduce native functionality.

Option B consequently follows the standard Public Sector data model and minimizes custom technical debt while allowing administrators to maintain permit relationships declaratively.

The uploaded screenshot cuts off the final portion of option D. Its completed wording above was restored from a matching copy of the same item; the answer validation itself is based on Salesforce's official documentation .

Study Guide Reference: Public Sector Solution Product Configuration – Regulatory Authorization data model; Business Regulatory Authorization Type Dependency; parent and dependent permits; Permits Experience Cloud component.

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

The Work.com employee-service architecture represented by this question consists of Employee Workspace, Employee Concierge, and HR Service Center .

Employee Workspace provides the employee-facing digital hub. Salesforce describes it as a central location where employees can access resources, collaborate, and obtain the tools required to work effectively.

Employee Concierge extends Employee Workspace with a searchable knowledge base and employee ticketing capability. Salesforce specifically states that Employee Concierge requires Employee Workspace to be installed and configured before the Concierge package itself is installed.

HR Service Center extends the employee-service architecture further, adding HR ticket management and employee onboarding processes. Salesforce documents that HR Service Center can only be installed after both Employee Workspace and Employee Concierge are configured.

That dependency chain directly establishes A, E, and C as related Work.com managed-package features.

Workplace Strategy Planner and Workplace Command Center belong to workplace/facilities-oriented capabilities and are not the three employee-service packages identified by this Employee Experience implementation path.

Current Salesforce strategy has evolved: HR Service is now positioned as a redesign of Work.com, and Salesforce recommends migration for organizations using legacy Work.com features. The item, however, tests the Work.com-based Employee Experience architecture represented in its source curriculum.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Employee Experience for Public Sector; Employee Workspace; Employee Concierge; HR Service Center.

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

Two Decision Matrices provide the cleanest and appropriate Business Rules Engine design because the scenario contains two independent lookup domains . The first matrix represents the federal income-limit values applicable to household size or related criteria. The second maps the calculated percentage of Area Median Income to the appropriate prioritization pool.

Salesforce defines Decision Matrices as tables that match supplied input values against rows and return corresponding output values. Expression Sets can invoke these matrices and combine the results with calculations, variables, and constants.

The Expression Set would therefore obtain or calculate the applicable household AMI percentage by referencing the federal-income-limit criteria and then pass that calculated percentage into the prioritization matrix. Separating these rule sets is preferable to placing unrelated policy dimensions into one monolithic matrix. It improves maintainability because federal limits can change independently of an agency's prioritization thresholds.

Option D unnecessarily creates a third matrix for household data. Household income and household size are transactional inputs , not reference-policy values that inherently require their own Decision Matrix. Option A omits the Federal Income Limit lookup, while B improperly combines two independently maintained rule sets.

This modular design also supports policy changes without rebuilding the Expression Set itself.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Decision Matrices; policy lookup tables; AMI and prioritization calculations.

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

Intelligent Form Reader is the appropriate capability because it is specifically designed to extract structured information from uploaded documents through optical character recognition and then use that extracted information to create, update, or verify Salesforce record data. Salesforce documentation explicitly describes a validation scenario in which a person's birth date stored in Salesforce is compared against the birth date extracted from a scanned passport. This directly matches the requirement in the question.

For identity documents such as driver's licenses and passports, Intelligent Form Reader can use document types, extraction templates, field mappings, and Amazon Textract capabilities to identify values such as date of birth. The extracted field can then be mapped to the corresponding Salesforce field and used as part of an automated verification process.

Content, Attachments, and Files provide mechanisms for storing or associating documents, but none independently performs OCR-based extraction and validation of document data. They can participate in document storage, but they do not satisfy the stated automation requirement.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Intelligent Form Reader; document extraction, OCR, document types, field mappings, and identity-document verification.

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

A published Action Plan Template is intentionally immutable . Salesforce explicitly states that after an Action Plan Template is published, it cannot be edited or deleted; depending on the implementation, it can be deactivated or made obsolete, and a replacement template must be created when process changes are required.

This behavior preserves process integrity. Existing Action Plans can be traced back to the exact template definition from which they were created, which is important for standardized licensing, inspection, compliance, and due-diligence workflows. Allowing administrators to alter a published template could change the apparent definition of a process after users had already executed tasks generated from that template.

Salesforce's document-automation guidance states the remediation directly: because a published template can't be changed, create a new template and remove or retire the old one. In practice, an administrator can clone the existing template, modify the draft copy with the updated assessment tasks, document requirements, signatures, or inspection steps, then publish the replacement.

The absence of Edit is therefore not a page-layout problem or missing System Administrator permission. Salesforce Support isn't required to modify the existing record because the immutability is an intentional product lifecycle rule.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plan Templates; Draft and Published lifecycle; template versioning; inspection-process governance.

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

Expression Sets in Business Rules Engine (BRE) are designed for calculations and complex business-rule execution where administrators need to evaluate combinations of input data before deploying the logic into a production process. An Expression Set consists of ordered steps using variables, constants, calculations, conditions, lookups, decision matrices, and aggregations. It therefore provides an appropriate rule-processing layer for calculating application or licensing fees from multiple customer-provided parameters.

Critically, Salesforce provides a simulation capability for Expression Set versions. Before activation, a rule designer can open an Expression Set version, select Simulate , and provide different sample input values. Simplified Input Mode supports direct variable entry, while Advanced Input Mode accepts JSON input. The designer can repeatedly change inputs, compare outputs, modify the rule, and rerun the simulation before activation.

Integration Procedures orchestrate Salesforce and external operations but aren't the primary rule-simulation engine. DataRaptors/Data Mappers perform data retrieval and transformation. Flow can execute business processes, but the scenario specifically requires complex fee calculations and repeated pre-production sample validation, which BRE Expression Sets provide natively.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Expression Set Builder; Simulation; fee calculations.

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

Decision Matrices are the Business Rules Engine component used to map combinations of application inputs to defined outputs such as application fees. Salesforce describes a Decision Matrix as a lookup table containing input values and corresponding output values. When an Expression Set invokes the matrix, Business Rules Engine finds the row matching the supplied inputs and returns the output associated with that row.

Salesforce specifically documents Decision Matrices for Public Sector application-fee calculation . For example, a business licensing matrix can contain authorization category and authorization type as inputs and a base application fee as the output. Different application characteristics can therefore automatically resolve to different required fees without custom code.

This architecture is preferable to hard-coding fee mappings because administrators can update the Decision Matrix as legislation, agency policy, permit categories, or fee schedules change. Expression Sets can subsequently call the matrix and perform additional calculations when needed.

"Data matrices" isn't the Business Rules Engine component name used for this function. Workflow Field Updates and Process Builder are legacy Salesforce automation capabilities; neither provides the structured multidimensional policy lookup behavior required for configurable fee schedules.

Salesforce's current BRE portfolio also includes Decision Tables , which support advanced rule logic, but for the specific matrix-based fee-mapping architecture represented by this exam item, Decision Matrix is the required answer.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Decision Matrices; Expression Sets; automated application-fee calculations.

Scope, schedule, and cost constitute the classic project-management triple constraint and are the correct considerations for an Agentforce Public Sector implementation. Salesforce Trailhead explicitly identifies scope, schedule, and cost as the three interconnected project constraints. A modification to one dimension generally affects at least one of the others.

Scope defines what capabilities and requirements the implementation must deliver—for example, licensing, permitting, grants management, constituent portals, or integrations. Schedule defines when those deliverables must be completed, including statutory deadlines, procurement milestones, fiscal-year constraints, or mandated program launch dates. Cost represents the approved implementation budget, including Salesforce products, implementation resources, integration work, testing, migration, training, and operational readiness.

For a public-sector implementation, these constraints require particularly disciplined governance because agencies commonly operate under fixed budgets and formally approved scopes while also facing regulatory or legislative deadlines. Expanding scope without changing schedule usually requires additional cost or resources. Conversely, reducing the budget may require scope reduction or schedule extension.

Resources certainly affect project execution, but they are not part of the standard three-way constraint identified by Salesforce project-management guidance. Workshops and tools are implementation mechanisms rather than primary project constraints.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – implementation planning; project governance; scope management; schedule management; budget/cost management.

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

Public Sector Inspection Management provides the native framework for investigating regulatory complaints through Visits, inspections, and Action Plans . Salesforce explains that agencies perform inspections both for license and permit applications and when members of the public report compliance concerns. Visit records identify the location, account, inspector, purpose, and regulatory context of an inspection.

The Visit can be created from a license or permit application and linked through its context to the applicable application, thereby preserving the connection between the investigation and the underlying construction authorization. Salesforce's current documentation explicitly supports creating Visits from application records and associating them with inspection types.

Action Plans provide the repeatable task framework used by inspectors. They contain assessment tasks, signatures, checklists, and other required inspection work so that investigators follow a standardized process. Salesforce also documents Action Plan usage for Public Complaint investigations.

Business Rules Engine is unnecessary merely to determine whether a complaint is valid, and directly linking generic Case records is not the core LPI complaint-and-inspection architecture.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Public Complaints; Visits; Permit Applications; Action Plans; regulatory compliance investigations.

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

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.

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

The requirement is for a repeatable document requirement , not one-off checklist records created manually on each application. The correct architecture therefore uses an Action Plan Template , document checklist items contained in that template, and automation to associate the template with every applicable Business License Application.

Salesforce documents that Document Checklist Items can be added to Action Plan Templates to standardize document-processing workflows. When an Action Plan is created from the template, the defined checklist items are automatically carried into that plan. Salesforce further requires the completed template to be published before operational use.

Option B establishes the reusable application-oriented template. Option E defines the three required document types within that template and publishes it. Option D ensures every newly created Business License Application receives the standardized Action Plan automatically, removing reliance on staff remembering to add the checklist manually.

Option C would create the checklist directly against an individual Business License Application. Salesforce supports that capability, but it doesn't satisfy the requirement to impose the same three-document package consistently on every application. Option A uses Tasks rather than Document Checklist Items, so it doesn't provide the dedicated applicant document-upload and tracking semantics.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Document Automation; Document Checklist Items; Action Plans; Action Plan Templates; Business License Applications.

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

VS Code and Salesforce DX provide the supported development and deployment tooling for OmniStudio Lightning Web Components associated with DataPacks. Salesforce explicitly states that administrators and developers use Visual Studio Code with Salesforce DX and the Salesforce CLI to manage, develop, and deploy OmniStudio Lightning Web Components between development, sandbox, and production organizations.

This distinction matters because an OmniStudio DataPack can include configuration metadata as well as generated or supporting Lightning Web Component artifacts. When LWC deployment is required, a Salesforce DX project provides the metadata structure, authentication, source management, and deployment commands needed to transfer the components reliably between environments.

VS Code by itself is only the development environment; it does not constitute the complete Salesforce deployment mechanism. Salesforce DX provides the Salesforce-specific project model and deployment capabilities, making option B incomplete. Standard Change Sets aren't the recommended deployment mechanism for these OmniStudio LWC assets, while the ANT Migration Tool represents an older Metadata API deployment approach and isn't the prescribed toolchain for this requirement.

Therefore, the complete supported combination identified by Salesforce is Visual Studio Code together with Salesforce DX.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio deployment, DataPacks, Lightning Web Components, VS Code, Salesforce DX/SF CLI.

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

Volunteer Management provides capabilities for coordinating volunteer demand, registrations, assignments, projects, shifts, and volunteer activity. Salesforce's official Work.com documentation describes Volunteer Management as supporting volunteer projects at scale and explicitly states that volunteers can sign up for volunteer projects through a community experience and update the time spent on volunteer activities . This directly validates option C.

The package also maintains volunteer capacity and registration information associated with volunteer work. Volunteer-management records track shift requirements and registered resources so that changes in a shift—including cancellation—can be reflected in the volunteer counts. This supports option A's requirement to keep registered-volunteer and volunteer-demand figures synchronized.

Salesforce's volunteer data architecture similarly includes volunteer shifts, volunteer hours, volunteer counts, and "Volunteers Still Needed" information, demonstrating that capacity and participation tracking are integral functions of volunteer management.

Automatic reimbursement claiming is not a standard Volunteer Management capability described for this package. Likewise, a volunteer chatbot is not one of the core Volunteer Management features represented by the question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Volunteer Management; volunteer projects, shifts, registrations, capacity, and volunteer-hour reporting.

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

User Stories and a Functional Requirements Specification (FRS) are core implementation artifacts because both translate stakeholder needs into requirements that can guide Salesforce solution design, configuration, development, and testing.

Salesforce defines a user story as a concise description of functionality that a business system should provide from a user's perspective. The commonly used structure is: As a [user], I want [capability] , so that [business value]. User stories become development work items and allow requirements to be prioritized, implemented, and validated incrementally.

Salesforce describes the Functional Requirements Specification as documentation of business requirements from the end-user or business perspective, specifying the expected functional outcomes. It becomes a more comprehensive reference for how required capabilities should operate and supports scope control, solution design, QA, and user acceptance testing.

A Marketing Plan addresses promotion, audience positioning, and communication strategy rather than technical implementation requirements. A Budget Plan is an important project-governance artifact but isn't one of the two requirements-definition documents being tested.

In a Public Sector project, these artifacts are particularly important because requirements commonly involve statutory rules, eligibility criteria, licensing processes, data governance, integrations, and auditable approval workflows that must be defined precisely before implementation.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – discovery; requirements gathering; user stories; functional requirements specifications; implementation documentation.

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

Public Sector uses business accounts to represent businesses and Person Accounts to represent individual constituents . Salesforce explicitly states that Person Accounts should represent people applying for licenses, permits, programs, benefits, grants, and government services, while business accounts represent organizations or businesses.

Because the agency has explicitly selected a phased implementation—business constituents first and private constituents later—the appropriate implementation is to establish the Business Account and Contact model for the first release and introduce Person Accounts when the individual-constituent phase is implemented.

Salesforce supports enabling Person Accounts in an existing Public Sector organization. However, the decision requires appropriate planning because Salesforce warns that Person Accounts can't be turned off after they're enabled . Administrators should therefore evaluate and test the implications before activation.

Household Accounts aren't the standard constituent model for Public Sector license and permit applications. Person Accounts are specifically integrated with Individual Applications, Cases, public complaints, and Public Sector constituent experiences. Therefore, C and D use the wrong individual data model. Option A unnecessarily implements the second-phase architecture immediately despite the government's explicit phased rollout.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Public Sector data model; Business Accounts; Contacts; Person Accounts; phased implementation strategy.

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

The product-native, low-code solution is to use Salesforce's DocuSign integration together with the supplied generic DocuSign OmniScript rather than designing Apex-based envelope handling.

Salesforce currently documents the sample OmniScript under the exact technical name GenericDocuSign/sendEsignature . It sends one or more documents associated with standard objects such as Opportunity, Order, or Quote—and supported custom objects—to DocuSign for electronic signature. The user selects the recipients and documents, reviews the routing order, and sends the envelope directly through the guided OmniScript.

Salesforce also provides a Send for eSignature (Generic) action that launches this OmniScript, minimizing custom development and allowing the signed-document status to be tracked using Generic DocuSign Envelope functionality.

Therefore, option C represents the intended answer. The option's GenericDocuSign/sendSignature wording reflects older/abbreviated exam terminology; Salesforce's current documented component is GenericDocuSign/sendEsignature. Option A refers to an "ObtainSignature" process rather than the send-for-signature flow needed when agreements must be transmitted to external grantseekers. Options B and D introduce the separate managed-package/Flow architecture when the supplied OmniScript capability already solves the requirement with less custom implementation.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – DocuSign integration; electronic signatures; GenericDocuSign/sendEsignature; OmniStudio document workflow.

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

The lowest-customization Public Sector architecture is to reuse the prebuilt Emergency Service Request flow and deploy the constituent experience through the preconfigured Emergency Response Management digital-experience template .

Emergency Response Management is designed to accelerate deployment of emergency programs and constituent-service workflows. Its digital experience provides the public-facing channel through which citizens and businesses can obtain emergency information and submit requests for assistance or services. Using the purpose-built template prevents the agency from recreating emergency-specific navigation, pages, and constituent processes from a generic Experience Cloud template.

The Emergency Service Request flow provides the intake layer. It captures the basic information needed for an emergency request and creates the corresponding Salesforce records through the configured Emergency Response architecture. This provides a declarative alternative to developing a custom request workflow.

A Help Center template is primarily designed for knowledge and customer-support self-service and would require additional configuration to reproduce Emergency Response functionality. Creating a custom Case record type and relying on a generic Contact Support Form similarly duplicates functionality already supplied by the solution and introduces unnecessary technical debt.

The Set 3 source shows C and D as the selected combination for this item.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Emergency Response Management; Emergency Service Requests; Experience Cloud; preconfigured emergency-response digital experiences.

The verified configuration sequence is B, C, and E . Salesforce's Public Sector documentation explicitly instructs administrators to turn on document checklists , assign the required permissions to users who process documents, and configure Document Types for the information extracted from submitted documents.

Document Checklist must first be enabled through Document Checklist Settings. The intake officer then requires the appropriate permission-set licensing and object access so that only authorized personnel can work with Received Documents, Document Checklist Items, extracted information, and the relevant application records. Salesforce's Intelligent Document Automation user-setup guidance specifically requires assigning Document Checklist and Intelligent Document Workspace access to document-processing users.

Finally, a Document Type must be created to define the type of incoming document—in this case, a Business License Application. Salesforce lists creating a Document Type as a foundational IDA setup task.

Option D is incorrect because Document Types are configured through the dedicated Document Type functionality, not under Notes and Attachments.

Verified correction: the uploaded screenshot marks A, C, E , but Salesforce's documented configuration requirements support B, C, E . There is no equivalent generic "Enable Intelligent Document Automation" step that replaces enabling Document Checklist.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Document Automation; Document Checklist Settings; Document Types; user permissions; intake officer access.