Free AP-222 Practice Test Questions and Answers (2026)

The Public Sector Solutions data model uses a junction object to create a many-to-many relationship between Regulatory Codes and Assessment Indicators. This is necessary because a single regulatory code can be associated with multiple assessment indicators, and one indicator can apply to several codes. The standard junction object provided for this purpose is named "Regulatory Code Assessment Indicator" (RegulatoryCodeAssessmentIndicator). This object links a specific regulatory code to a specific assessment indicator, allowing the PSO to maintain a clear and referential map between the inspection criteria and the underlying regulations.

B. "Assessment Indicator Regulatory Code" is an incorrect naming convention for the standard junction object that links these two records in the data model.

C. While this describes the function of a junction object, "Regulatory Code Map" is not the standard API or label name for the object in Public Sector Solutions.

D. A master-detail relationship creates a one-to-many link, which is insufficient. It would incorrectly restrict an assessment indicator to only one regulatory code.

1. Salesforce Architects. (2023). Public Sector Solutions Data Model. Salesforce. The official Entity Relationship Diagram (ERD) for Public Sector Solutions shows the RegulatoryCode object and the AssessmentIndicatorDefinition object are linked via the RegulatoryCodeAssessmentIndicator junction object.

2. Salesforce Help. (2023). Public Sector Solutions Object Fields. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.pscobjectfields.htm&type=5. The object reference documentation lists RegulatoryCodeAssessmentIndicator as a standard object with lookups to both RegulatoryCode and AssessmentIndicatorDefinition.

To manage a high-volume surge for a grant application portal, a multi-layered approach is essential. Implementing a Content Delivery Network (CDN) and waiting rooms (A) manages the initial traffic influx and user experience. Offloading computationally intensive operations to asynchronous processes (C), such as Apex Batch or Queueable jobs, prevents synchronous transaction limits from being exceeded and keeps the user interface responsive. Finally, conducting thorough load testing (D) is critical to validate that the entire architecture—including code, configuration, and infrastructure—can withstand the anticipated peak user load and identify potential bottlenecks before the launch window opens.

B. IP restrictions are an access control mechanism to limit who can access the site, not a tool to manage a high volume of legitimate traffic.

E. User Acceptance Testing (UAT) focuses on functional correctness and business process validation from an end-user perspective, not on performance under high load.

1. Salesforce Architects. (n.d.). Architect's Guide to Building Forms on Experience Cloud. Salesforce. Retrieved from https://architect.salesforce.com/design/decision-guides/forms-experience-cloud. See section: "Scale and Performance Considerations".

2. Salesforce Help. (n.d.). Asynchronous Processing in Apex. Retrieved from https://help.salesforce.com/s/articleView?id=sf.codeapexasynch.htm&type=5. See section: "When to Use Asynchronous Apex".

3. Salesforce Developers. (n.d.). Best Practices for Improving Visualforce Performance. Retrieved from https://developer.salesforce.com/docs/atlas.en-us.salesforcevisualforcebestpractices.meta/salesforcevisualforcebestpractices/visualforcebestpracticesloadtesting.htm. See section: "Load Testing Your Applications".

4. Salesforce Help. (n.d.). Experience Cloud Sites with Salesforce CDN. Retrieved from https://help.salesforce.com/s/articleView?id=sf.networkscdnoverview.htm&type=5.

To address the security and privacy concerns, a multi-layered approach is necessary. Implementing CAPTCHA (A) directly mitigates the risk of bot spam on public-facing forms. Requiring login for grant application OmniScripts (B) ensures that only authenticated constituents can submit applications, enhancing data integrity and security. Setting the external organization-wide default for grant application objects to Private (C) is a fundamental security control that prevents constituents from viewing each other's sensitive application data, thereby complying with privacy regulations. Together, these measures provide robust protection against the specified threats.

D. A public search page could introduce security risks if not properly designed and does not protect the initial application submission process from spam or unauthorized access.

E. "Salesforce Spam Check for Experience Sites" is not a standard Salesforce feature name. The correct feature for bot protection on forms is reCAPTCHA.

1. Salesforce Help, Experience Cloud, "Use reCAPTCHA in Your Experience Cloud Site". This document details how to add a CAPTCHA widget to site pages to protect against spam.

2. Salesforce OmniStudio Documentation, "OmniScript LWC Element Reference". The documentation for the OmniScript element shows properties like login-required that can be set to true to enforce user authentication.

3. Salesforce Help, Security and Identity, "Organization-Wide Sharing Defaults". This guide explains that setting external access to Private is the most restrictive level, ensuring users can only see their own records.

The recommended approach for automatically generating a Violation record is to configure the relationship between the question and the potential violation type. This is achieved by creating a Violation Type and associating it with the relevant Assessment Indicator Definition (the inspection question template). This association is made using a junction object, Violation Type Assessment Indicator, where the administrator specifies which result value (e.g., "Fail" or "Issue") should trigger the violation. This declarative setup is the standard, intended mechanism within the Public Sector Solutions data model for this requirement.

A. A custom Flow is not the recommended approach, as Public Sector Solutions provides a standard, declarative feature to meet this specific requirement without custom code or complex automation.

B. This is incorrect because the configuration is not managed via a checkbox on the picklist values of the Results field on the Inspection Assessment Indicator object. This describes a feature that does not exist.

C. Action Plan Templates are used to define sets of follow-up tasks that can be assigned after an inspection, not to configure the real-time, automatic creation of violations from question responses.

1. Salesforce Public Sector Solutions Developer Guide: Associate a Violation Type with an Assessment Indicator Definition. This official guide details the process: "To automatically create a violation when an inspector selects a specific response to a question, associate a violation type with an assessment indicator definition." It specifies creating a Violation Type Assessment Indicator record and populating the Assessment Result Value field with the trigger value (e.g., "Fail"). This directly supports the mechanism described in option D.

2. Salesforce Public Sector Solutions Developer Guide: Inspection Management Data Model. The data model map shows that Assessment Indicator Definition is linked to Violation Type through the Violation Type Assessment Indicator junction object. This confirms the relationship is defined at the template/definition level, not on the Inspection Assessment Indicator result record's picklist values as suggested in option B.

Action Plan Templates in Public Sector Solutions are designed to standardize repeatable business processes. The template can be associated with a specific object, such as Business License Application. A key feature is the ability to include Document Checklist Items, which prompts users to upload required files, satisfying the driver's license image requirement. The other requirements, such as tasks with due dates and dependencies, are also standard features of Action Plans, making option A a true statement about the template's capabilities relative to the scenario.

B. Users with appropriate permissions can add ad-hoc tasks to an active Action Plan, providing flexibility beyond the predefined template.

C. Action Plans support task dependencies, allowing a task's due date to be calculated based on the completion of a predecessor task.

D. Document Checklist Items are a standard and integral component that can be added to Action Plan Templates to manage required document uploads.

1. Salesforce Help. Action Plans. "Create an action plan template for the Business License Application object."

2. Salesforce Help. Create Action Plan Templates. "Add tasks and document checklist items to the template."

3. Salesforce Help. Action Plan Template Items. "You can set task dependencies in an action plan template. For example, make a task dependent on the completion of a previous task."

Entitlement Management can be enabled on a custom object such as Permit Application. Milestones measure time-based steps (e.g., “Initial Review within 3 days”), and impending-breach warnings can fire actions and escalations, giving staff visibility before Service Level Agreements are violated—satisfying the need to detect and act proactively on SLA risks for applications stored outside the Case object model.

B. Uses Case object, which Bobahaven isn’t using; escalations occur only after breach, not proactive.

C. Same Case dependency as B; Bobahaven needs solution on Permit Application object.

D. Escalates only after breach; requirement is to act before the violation occurs.

• Salesforce Help, “Enable Entitlement Management for a Custom Object” (Spring ’24).

• Salesforce Help, “Set Up Milestones” > “Warning Escalations before a Violation” (Spring ’24).

• Public Sector Solutions Implementation Guide, “Tracking SLAs on Permit Applications with Entitlements”, pp. 134-138.

The Business Rules Engine (BRE) is the ideal feature for this use case. It is specifically designed to automate complex decisions based on a configurable set of conditions without writing code. For a large volume of grant applications, BRE can be configured with Expression Sets and Decision Matrices to evaluate application data against eligibility criteria, calculate scores, and determine qualification status automatically. This allows the agency to process applications efficiently and consistently, which is crucial when dealing with high volumes.

A. Process Builder is a retired automation tool and is less suitable for complex, multi-conditional decision logic compared to the purpose-built BRE.

B. An Apex Trigger involves custom code, which is not the easiest or most maintainable solution for business rules that may change over time.

C. Visual Flow (Flow) is a powerful automation tool but is better for guided processes and record updates, not for executing complex sets of rules to derive a single decision.

- Salesforce Help, Public Sector Solutions Documentation, "Business Rules Engine". This document states, "Business Rules Engine gives you a suite of services... to automate decisions. You can model and execute complex business rules to determine eligibility, compliance, benefits, and violations."

- Salesforce Help, Public Sector Solutions Documentation, "How Business Rules Engine Works". This section details the use of Expression Sets and Decision Matrices to look up rules and automate decisions for use cases like benefit eligibility.

To prevent external users (constituents) from seeing each other across all Experience Cloud sites by default, the organization-wide "Site User Visibility" setting must be disabled (unchecked). This setting, found under Sharing Settings, controls whether users in one site can see users in another site. When disabled, it enforces a baseline of privacy, restricting external users' visibility to other users within the same account or those explicitly shared with them. This is the most effective org-wide control to meet the PSO's privacy requirement for all its sites.

A. "Disable User Sharing" is not the correct name for the setting; the official term is "Site User Visibility" or "Portal User Visibility."

B. Removing access to the User object would break essential functionality, such as users viewing their own profiles.

D. Setting the User object OWD to "Public Read Only" would make all users visible to all other users, which is the opposite of the requirement.

1. Salesforce Help. (2023). User Visibility Settings. This document explicitly states, "Deselect the Portal User Visibility checkbox if you want portal users in the same community to see only other members of that community." (Note: The term "Portal" is often used interchangeably with "Site/Community" in this context).

2. Salesforce Help. (2023). Control User Visibility in Your Experience Cloud Site. This guide explains the different layers of user visibility control, highlighting the org-wide setting as the primary control.

3. Salesforce Architects. (2023). Who Sees Who in Communities. "Org-Wide Settings". This resource details that the "Portal User Visibility" checkbox in Sharing Settings is the first and most important control for external user visibility.

The Partner Central template is specifically designed for building digital experiences for partners, such as resellers, distributors, and associates. It includes pre-built features for channel sales and partner relationship management (PRM). Key functionalities like lead distribution, deal registration, marketing campaigns, and partner onboarding are core components of this template, making it the ideal choice for the agency's requirements without needing extensive custom development. It provides a collaborative space for the agency and its associates to manage the entire partner lifecycle.

A. The Aloha template is an internal-facing template used for creating a portal that connects internal users to various Salesforce apps and resources.

C. The Help Center template is designed for customer self-service, focusing on providing access to knowledge articles and case management, not for channel sales workflows.

D. The Customer Account Portal template is for customers to manage their own information, view orders, and pay bills. It is not intended for sales partners.

1. Salesforce Help. Which Experience Cloud Template Should I Use?. "Partner Central: A flexible, responsive template designed for channel sales workflows. Recruit, build, and grow your partner network... Manage leads and opportunities, and track your channel sales."

2. Salesforce Experience Cloud Basics Module, Trailhead. Meet Experience Cloud Templates. "Use the Partner Central template to create a PRM (partner relationship management) site. Onboard partners, manage channel sales, and access reports and dashboards."

To solve the problem with minimum coding, the best approach is to leverage the built-in Public Sector Solutions (PSS) toolset, which includes OmniStudio. PSS provides a pre-built Integration Procedure named GenericDocuSign specifically for this purpose. The sendEsignature action within this Integration Procedure is designed to send a document envelope to recipients for their signature. This can be called from an OmniScript, providing a guided, low-code process for the department staff. This method directly addresses the need to send the agreement and is the standard PSS configuration for e-signature integration.

A. Using an Apex action introduces custom code, which contradicts the "minimum/less coding" requirement. The standard PSS toolset provides a declarative way to achieve this.

C. While using a managed package and Flow is a low-code option, the native PSS approach utilizes OmniStudio, which is more tightly integrated with PSS data models and processes.

D. The ObtainEsignature action is used to download the already signed document, not to initiate the process by sending the agreement to the Grant Seeker for signature.

- Salesforce Public Sector Solutions Developer Guide, "Electronic Signature Integration". This section details the GenericDocuSign integration procedure and its actions, specifying that sendEsignature is used to send a document for signature.

- Salesforce OmniStudio Developer Guide, "Integration Procedures". This guide explains how Integration Procedures are used to execute business logic, including calling external APIs like DocuSign, without Apex code.