AP-222 Salesforce Accredited Agentforce 360 for Public Sector Professional Free Practice Exam Questions (2026 Updated)

The Analytics for Licenses, Permits, and Inspections template performs a data compatibility check before creating the analytics application. Salesforce requires the Public Sector org to contain source records from the LPI operational data model so that the template can build its datasets and dashboards.

Salesforce ' s current data-requirements documentation identifies Visit as one of the supported source objects used by LPI analytics, along with Business License Application, Individual Application, Public Complaint, and Regulatory Transaction Fee. If the org lacks qualifying source data, the template returns an error during application creation and instructs the administrator to add the required data before trying again. Among the choices, missing Visit data is the relevant operational-data problem associated with the inspection portion of the analytics application. Visits represent actual inspection activity and are therefore central to metrics such as inspections performed, inspection volume, and related operational trends. Violation records, active Action Plan Templates, and Person Account enablement are not listed as the prerequisite represented by this compatibility-check scenario.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Data Requirements; Visit Object; Analytics Compatibility Check.

Administrator users responsible for creating and managing Public Sector analytics require both the CRM Analytics platform-level administrator capability and the Public Sector-specific analytics administrator capability.

CRM Analytics Plus Admin supplies the permissions required to administer CRM Analytics, including creation and management of templated analytics applications. Salesforce describes this prebuilt permission set as providing the administrative permissions for CRM Analytics Plus and associated application-management functionality. The administrator must also receive the Public Sector analytics administrator permission set represented in the options by CRMA for Public Sector Admin. Current Salesforce documentation identifies this Public Sector-specific administrative permission as TCRM for Public Sector Admin. Salesforce ' s setup procedure explicitly instructs administrators to assign CRM Analytics Plus Admin AND TCRM for Public Sector Admin to users who create and manage Public Sector analytics applications. The combination separates platform administration from industry-template access. CRM Analytics Plus Admin alone does not provide the full Public Sector-specific entitlement required by the LPI application, while the industry permission alone does not supply the necessary CRM Analytics platform administration rights.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Admin Permissions; CRM Analytics Plus Admin; Public Sector Analytics Admin.

OmniStudio provides the complete low-code toolset required for a sophisticated constituent-facing application experience. OmniScripts implement the guided, responsive form flow and can structure the application ' s pages, questions, branching behavior, validations, and navigation to reflect a complex government paper form while supporting a digital user experience.

DataRaptors, now referred to as Data Mappers in current OmniStudio terminology, retrieve, transform, and persist Salesforce data. Integration Procedures provide reusable server-side orchestration for complex data operations, external integrations, and calculations. FlexCards present contextual information and actions in a compact, configurable user interface. Salesforce describes these four components as complementary OmniStudio capabilities: OmniScripts contain user-interaction logic, DataRaptors transfer and transform data, Integration Procedures bundle server-side integration operations, and FlexCards display information and launch actions. This architecture is particularly appropriate for high-volume digital applications because processing can be shifted into reusable server-side Integration Procedures while the browser handles the optimized guided experience. OmniStudio also provides declarative styling and layout capabilities that support branded digital experiences without requiring a fully custom application stack.

Study Guide References: OmniStudio; OmniScripts; DataRaptors/Data Mappers; Integration Procedures; FlexCards; Grants Digital Application Experience.

Dynamic Assessments use categories to organize Assessment Questions so that different subsets of questions can participate in conditional assessment paths. This directly supports the restaurant scenario, where specific questions need to apply to take-away businesses, dining establishments, or businesses operating under both models.

Salesforce ' s Dynamic Assessments setup sequence explicitly directs administrators to create categories for similar types of assessment questions, create the assessment questions themselves, and then add those questions to Omni Assessment Tasks. The resulting form is used in an OmniScript, where conditional logic controls which questions are shown for a particular assessment scenario. The distinction between the objects is important. An Assessment Task Definition or Omni Assessment Task represents a broader group of questions or work to be performed. An Action Plan organizes the overall repeatable inspection workflow. Assessment Indicator Definitions are used heavily in regulatory inspection assessment models, but they are not the object on which this Dynamic Assessment question categorization is being configured. By categorizing the individual Assessment Question records, the agency can reuse a broader assessment while selectively presenting only the questions relevant to the type of food outlet being inspected.

Study Guide References: Dynamic Assessments; Assessment Questions; Question Categories; Omni Assessment Tasks; OmniScripts; Conditional Assessment Logic.

Salesforce Entitlement Management applies service-level processes to supported service records, particularly Cases. An Entitlement Process defines the service timeline, while Milestones represent required service steps such as response or resolution deadlines. Salesforce confirms that entitlement processes for this pattern run on Cases and can enforce milestone-based service levels.

The requirement is explicitly proactive management. Milestone Warning Actions are therefore essential because they execute when a milestone is approaching violation. Salesforce supports actions such as email alerts, tasks, field updates, flows, and outbound messages before an SLA deadline is missed. Violation Actions, by contrast, execute after the milestone has already been breached. Bobahaven can use Cases to operationally track applications requiring service intervention, associate them with the appropriate entitlement process, and configure milestones representing expected approval-response times. Warning actions can alert owners or supervisors while enough time remains to intervene. The alternatives that trigger escalation only after an SLA breach are reactive rather than preventive. Furthermore, standard entitlement processes are designed around supported service records such as Cases rather than being attached directly to Public Sector application objects in the manner proposed by the other options.

Study Guide References: Service Cloud Cases; Entitlements; Entitlement Processes; Milestones; Warning Actions; SLA Management and Escalation.

The standard Hierarchical View component is specifically designed to display multi-level related Public Sector records in a single structured view. Salesforce describes Hierarchical View as a Lightning web component that presents cascading relationships and allows users to avoid repeatedly navigating through individual related lists and record tabs. It can display up to four levels of related records.

For an Account, Salesforce provides a directly relevant configuration pattern. The first level can display Business License Applications, the second level associated Visits, the third level Regulatory Code Violations, and the fourth level Violation Enforcement Actions. This precisely matches a scenario in which reviewers want to start from an Account and understand its inspection and compliance history. The component supports standard Public Sector objects including Account, Visit, Inspection Assessment Indicator, Regulatory Code Violation, Violation Enforcement Action, and several other regulatory objects. It can therefore provide the requested multi-level visibility without requiring a custom UI component. Although Hierarchical View is technically implemented as a Lightning web component, the appropriate configuration choice is the named Hierarchical View component, because Salesforce supplies and supports it specifically for this use case. Building a generic custom LWC, Aura component, or installing an AppExchange component would add unnecessary development and maintenance.

Study Guide References: Hierarchical View; Account Unified View; Visits; Regulatory Code Violations; Enforcement Actions; Public Sector Record Relationships.

Decision Explainer provides the explainability layer for decisions generated through Public Sector business processes, including eligibility, prioritization, and other Business Rules Engine outcomes. Adding the Decision Explainer Log History component to the Lightning record page makes the interface available, but component placement alone does not grant the user access to Decision Explainer functionality or its underlying records.

Salesforce specifies Decision Explainer access permissions for users who create, use, or review explainability information. Current Public Sector documentation identifies Decision Explainer Service Access for internal users working with Decision Explainer entities and decision logs. Salesforce also provides a Decision Explainer permission set license for access to Decision Explainer functionality. Therefore, after confirming that the component is correctly placed on the application Lightning page, the administrator should validate the caseworker ' s Decision Explainer permissions. OmniStudio Admin and OmniStudio User concern OmniStudio configuration and execution, while Rule Engine Runtime enables execution of Business Rules Engine logic. Those permissions do not independently provide access to the Decision Explainer user interface and decision history.

Study Guide References: Decision Explainer; Decision Explainer Log History; Business Rules Engine Integration; Public Sector Permission Sets and Permission Set Licenses.

The Employee Experience application combines access to the employee-facing community experience, productivity capabilities, and Public Sector-specific employee functionality. The configuration represented by this question therefore requires Employee Experience Community Access, Employee Productivity Plus Access, and Employee Experience for Public Sector.

Salesforce documents that the Employee Experience for Public Sector permission set grants employees access to Public Sector objects and capabilities used by employee-focused applications. Current Public Sector documentation also describes Employee Experience as the mechanism for providing government employees access to capabilities such as licensing and permitting, grantmaking, benefits, inspection management, and employee portals. Employee Productivity Plus Access supplies access to employee productivity and onboarding-related functionality. Salesforce ' s HR Service Center permissions documentation identifies Employee Productivity Plus Access as the permission set associated with the Employee Productivity Plus entitlement and distinguishes it from the User Data Access permission set, which primarily provides application, object, record-type, and flow access for the supporting data layer. Together, the three selected permission sets provide the experience-site, productivity, and Public Sector application access required for the prebuilt Employee Experience configuration.

Study Guide References: Employee Experience for Public Sector; Employee Experience Community Access; Employee Productivity Plus; Employee Experience Application Access.

Grants Management requires a modern Lightning and Experience Cloud architecture rather than a Salesforce Classic-only implementation. Salesforce ' s Grants Management installation requirements specify the appropriate Grants Management entitlement together with Customer Community Plus Login licensing and Lightning Experience enabled in the org. Digital Experiences and My Domain are also part of the broader installation prerequisites.

Customer Community Plus is required because grantseekers need authenticated access to richer application records and sharing capabilities than a basic high-volume customer community provides. Lightning Experience is necessary for the modern Grants Management application, components, workflows, and administrative experience. In the implementation model represented here, Chatter is also enabled to support Salesforce collaboration capabilities used alongside Grants Management processes. Web-to-Lead does not provide the grant application architecture; grant applications are modeled using Grants Management funding records and Experience Cloud processes rather than sales leads. Basic Customer Community licensing also does not satisfy the specified Grants Management portal entitlement. The consultant should therefore transition the relevant staff to Lightning Experience, provision the appropriate Customer Community Plus licensing for external grantseekers, and enable Chatter as part of the solution prerequisites.

Study Guide References: Grants Management Installation; Lightning Experience; Customer Community Plus; Chatter; Experience Cloud Grantee Portal.

Intelligent Document Automation is designed to convert document-heavy, manually processed information into structured digital Salesforce data. Salesforce describes the capability as centralizing document-management tasks, handling information received in PDFs and image files, extracting data from incoming documents, and converting physical or scanned documentation into usable digital records.

For Public Sector specifically, Salesforce states that Intelligent Document Automation can extract and store information from paper or handwritten forms into digital records such as Business License Applications or Individual Applications. The solution reduces manual data entry and allows reviewers to compare extracted application information with the scanned source document. This directly addresses an agency migrating from decades of paper-based operations. Document types, document checklist items, OCR-based extraction, Received Documents, and review components provide a controlled path from document intake through structured digital processing. Business Rules Engine is intended for decision logic and eligibility or fee calculations, not document conversion. Workflows automate process steps but do not inherently extract information from paper files. Smart Forms address data capture but do not provide the document-ingestion and extraction framework required here.

Study Guide References: Intelligent Document Automation; Intelligent Form Reader; Received Documents; Document Checklist; Public Sector Digital Transformation.