Pass the Salesforce Accredited Professional Certification AP-222 Questions and answers with ExamsMirror

Salesforce directly documents Action Plans on Accounts as the mechanism for standardizing grantmaking due-diligence processes. An Action Plan Template acts as a reusable blueprint that defines the activities reviewers must complete consistently for each grantseeking organization.

Salesforce's Grants Management documentation explicitly states that organizations can use Action Plans on Accounts to define due diligence steps, related tasks, and documents to collect . Tasks can represent actions such as requesting tax documentation, verifying organizational eligibility, or completing financial reviews. Document Checklist Items identify supporting documents that must be obtained and reviewed.

This architecture directly addresses the problem in the scenario: reviewers currently follow different processes. A published Action Plan Template converts an informal procedure into a repeatable Salesforce-controlled workflow, improving consistency, traceability, accountability, and reviewer productivity.

A Screen Flow or OmniScript could technically guide a user through steps, but both would duplicate functionality already supplied by Action Plans. Merely supplying procedural documentation also provides no technical enforcement, assignment, due-date management, or document checklist tracking.

Therefore, Action Plans represent the product-native and lowest-customization implementation.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Due Diligence; Action Plans; Action Plan Templates; Tasks; Document Checklist Items.

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

The decisive requirement is pixel-perfect control over the digital experience . Salesforce specifically positions the Build Your Own (LWR) Experience Cloud template for organizations that need high-performance, highly customized experiences using Lightning Web Components. Salesforce states that the template enables developers to build pixel-perfect pages and create Lightning Web Components and themes that precisely match an organization's brand.

Lightning Web Runtime is optimized for performance because Lightning Web Components execute using browser-native standards, resulting in lightweight components and efficient rendering. LWR also includes performance capabilities such as HTTP caching and publish-time optimizations.

The Licenses and Permits template is excellent when the priority is rapid deployment and minimal customization. It provides preconfigured application, renewal, permit, complaint, inspection-history, and account-management pages. However, that was not the dominant requirement in this scenario. The sponsor has explicitly elevated pixel-perfect branded UX above minimizing implementation effort.

Help Center is designed primarily for public knowledge and support self-service. BYO Aura supports customization but does not provide the performance-oriented modern LWR architecture that Salesforce recommends for sophisticated custom digital experiences.

Therefore, BYO LWR with custom Lightning Web Components best satisfies the specified UX requirement.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud architecture; Build Your Own LWR; Lightning Web Components; branding and digital experience design.

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

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.

Action Plans are intended for exactly this type of repeatable licensing workflow. Salesforce identifies Business License Application as a supported target object for Action Plan Templates, allowing the agency to define standardized reviewer activities that are instantiated whenever the plan is applied to a specific application.

Salesforce also supports Document Checklist Items within action-plan-based document-processing workflows. Document checklist items identify the specific documents that applicants or staff must supply, such as a driver's license. When a document checklist item is included in a published Action Plan Template, it can be propagated to Action Plans created from that template, creating consistent document requirements.

Therefore, option A accurately combines the correct target record—Business License Application—with document tracking for the required identity-document image.

The other statements are overly restrictive. Salesforce supports Action Plan task dependencies in applicable Public Sector implementations, including prerequisite and successor task relationships, so dependent execution can be modeled declaratively. Action Plans also use ordinary task records, and Salesforce supports ad hoc task creation when configured, so staff can supplement standardized plans when case-specific work is necessary.

This gives the agency both governance and flexibility: required standard tasks come from the template, while exceptional application-specific work can still be accommodated.

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

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

This requirement calls for three cooperating layers: a guided application form to capture applicant information, a structured lookup model for eligibility criteria, and executable rule logic to evaluate and prioritize each application. Those capabilities are provided by OmniScript, Decision Matrix, and Expression Set .

Salesforce identifies Decision Matrices and Expression Sets as the two core elements of Business Rules Engine. A Decision Matrix stores policy criteria as structured input and output values, while an Expression Set executes calculations, invokes matrix lookups, and returns the resulting decision. Salesforce specifically states that BRE can determine whether applicants qualify for government programs, small-business loans, licenses, and other public-sector services.

The application front end should be created with OmniScript Designer . Salesforce documents the same architecture for eligibility-driven Public Sector workflows: an OmniScript captures applicant inputs, an Expression Set evaluates those values, and a Decision Matrix contains the eligibility thresholds or criteria.

Web-to-Lead creates Lead records and isn't a grant eligibility framework. Web-to-Case creates Cases and likewise doesn't provide structured application assessment or prioritization logic.

This combination gives the agency a maintainable, policy-driven system in which eligibility rules can change without rebuilding the constituent application.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScript Application Forms; Business Rules Engine; Decision Matrices; Expression Sets; automated eligibility and prioritization.

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

A DataRaptor , now called an OmniStudio Data Mapper , is specifically designed to read, transform, and write data to Salesforce objects. For the use case in this question, the external portal already exists; the primary requirement is therefore to take submitted application data and map it into the corresponding Public Sector Salesforce objects.

Salesforce states that a Data Mapper Load accepts JSON, XML, or supported custom input formats and writes the resulting data to Salesforce objects using configured object and field mappings. More importantly for this scenario, Salesforce exposes a Data Mapper REST API . An external application can POST a JSON payload to a Data Mapper Load, and the Data Mapper updates or creates Salesforce records according to its mappings.

That makes DataRaptor/Data Mapper an appropriate declarative bridge between the existing external portal and Public Sector's Grant application records.

An Integration Procedure is preferred when orchestration involves multiple data sources, several operations, conditional processing, REST integrations, error handling, or multiple Data Mappers. Salesforce recommends a single Data Mapper where the requirement is fundamentally a Salesforce-object write operation that can be handled through direct mappings.

FlexCards provide user-interface presentation. OmniOut runs OmniStudio UI components on third-party sites, but the question states that the agency will retain its existing portal and specifically needs to integrate submitted data .

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio DataRaptors/Data Mappers; Data Mapper Load; REST API; external application integration.

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

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.

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

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 secure Experience Cloud design follows a restrict-first, selectively-share model. Salesforce recommends setting external organization-wide defaults to Private wherever possible , ensuring authenticated external users receive no automatic access to records they do not own or that have not explicitly been shared with them. External OWD therefore establishes the least-privilege baseline required by the scenario.

After establishing that restrictive baseline, Sharing Sets provide authenticated Experience Cloud users access to records associated with their own Account or Contact. Salesforce states that Sharing Sets use access mappings between the external user's Account/Contact and the target record. For example, a user can receive access to Cases associated with the Account identified through their Contact. Sharing Sets support Accounts, Cases, Business License Applications, custom objects, and numerous Public Sector objects.

This mechanism is particularly important for high-volume Customer Community users because conventional role-based sharing isn't the appropriate scalability model. Salesforce specifically recommends Sharing Sets for Customer Community users when access should follow Account or Contact relationships.

Option C is invalid because Hidden isn't an external OWD access level. Option A is less appropriate than Sharing Sets for the account/contact-relative community access model described.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud Security; External OWD; Private access; Sharing Sets; least-privilege external record access.

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.

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