Practice Free AP-222 Salesforce Accredited Agentforce 360 for Public Sector Professional Exam Questions Answers With Explanation

Salesforce Entitlement Management and Milestones provide the correct mechanism for tracking SLA-based support response requirements. An entitlement process defines the service timeline, while milestones represent required time-dependent steps such as first response or resolution. Salesforce supports entitlement processes for support records such as Cases , and milestones can generate warning actions before an SLA is violated.

The word proactively is decisive. Salesforce distinguishes three milestone action categories: success, warning, and violation. Warning actions execute when a milestone is approaching violation, allowing email alerts, tasks, field updates, or other escalation actions to occur before the target is missed.

Therefore, A provides both the supported record architecture and the required proactive behavior. Option B waits until the SLA is already breached and thus fails the proactive requirement.

Options C and D incorrectly imply that standard entitlement processes can simply be placed directly on arbitrary Public Sector application records. Salesforce's supported Milestone objects include Cases, Work Orders, and Incidents; standard Business License Application records aren't listed as direct Milestone targets.

The appropriate pattern is therefore to manage the response/escalation process through Cases associated with the underlying application context and apply Entitlements and Milestones to those Cases.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – constituent service; Cases; Entitlements; Milestones; SLA warning actions and proactive escalation.

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

An Integration Procedure is the correct orchestration component because this requirement combines information from different data sources: an external fee system and Salesforce custom-object data. OmniStudio Integration Procedures are declarative server-side processes designed to execute multiple data operations within a single server call.

Salesforce specifically states that Integration Procedures can retrieve, transform, and send information between Salesforce and external systems, invoke REST APIs, perform conditional processing, and combine information from multiple sources into a single response.

That architecture maps directly to this scenario. The Integration Procedure can retrieve the base permit fee from the external system, retrieve site or address information and applicable discount information from Salesforce, apply the required transformations or calculations, and return the resulting fee to the calling application process.

A Data Mapper is more suitable for straightforward Salesforce object reads, writes, and transformations. It is not the preferred component when multiple heterogeneous data sources and external REST services are involved. A FlexCard primarily presents information and actions to users. An OmniScript manages the interactive guided process, but it would normally invoke an Integration Procedure to execute this server-side integration.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; external data access; REST integration; multi-source orchestration; license and permit fee processing.

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

The Licenses and Permits Experience Cloud template should be used because Salesforce supplies it specifically for constituent licensing and permitting experiences. It includes preconfigured pages for applying for licenses or permits, renewing authorizations, viewing applications and licenses, reviewing inspection history, filing complaints, and identifying permit requirements.

Using this purpose-built template significantly reduces custom implementation and long-term maintenance compared with retrofitting a generic Help Center site. Salesforce also provides OmniStudio-driven application capabilities that can be placed directly into Experience Cloud, including dynamic application forms built with OmniScripts and supporting components.

Option C could technically be implemented, but it would require the agency to manually recreate capabilities that Salesforce already supplies through the dedicated template. That contradicts the requirement to minimize customization and maintenance.

OmniOut is intended for scenarios where OmniStudio experiences must run outside Salesforce-hosted environments. Since the requested constituent application experience is being implemented directly on Experience Cloud, OmniOut adds unnecessary architecture and deployment complexity. Therefore, neither A nor D represents the most maintainable design.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Licenses and Permits Experience Cloud Site; Experience Cloud templates; OmniScripts; FlexCards; reuse of preconfigured Public Sector components.

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

Salesforce defines Expression Sets and Decision Matrices as the key components of Business Rules Engine and explicitly establishes their relationship. Expression Sets perform a sequence of calculations using matrix lookups, user-defined variables, constants, conditional logic, and other BRE elements. During execution, an Expression Set can call a Decision Matrix , which stores business rules as a structured table of input and output values.

A Decision Matrix does not itself perform the sequence of calculations described in option A. Instead, it accepts input values, locates the table row that satisfies those values, and returns the corresponding output. That behavior makes option C reversed: matching inputs to rows is the responsibility of the Decision Matrix, not the Expression Set.

Option D is also technically incorrect. Salesforce documents that Expression Sets and Decision Matrices can receive JSON input from OmniScripts and return JSON output , not XML input.

This architecture is particularly effective for Public Sector licensing because frequently changing regulatory criteria, fee schedules, eligibility conditions, and authorization rules can be maintained declaratively in Decision Matrices while Expression Sets orchestrate the calculations and matrix lookups.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Decision Matrices; matrix lookups; JSON integration with OmniScripts.

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

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.

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

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.

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

The Hierarchical View component is the standard Public Sector feature designed for precisely this requirement. Salesforce states that Hierarchical View provides users with a unified visualization of related records across up to four levels of a relationship hierarchy, eliminating the need to navigate multiple related lists and individual records.

The component supports Account as well as numerous Public Sector objects relevant to this scenario, including Visit, Inspection Assessment Indicator, Regulatory Code Violation, Violation Enforcement Action, Business License Application, Public Complaint, Regulatory Transaction Fee , and other related records. Salesforce gives a closely aligned example in which reviewers need to understand records associated with a business license application: an application leads to an inspection visit, the inspection can identify regulatory-code violations, and violations can result in enforcement actions and regulatory transaction fees. Hierarchical View presents those relationships as a connected structure rather than disconnected lists.

Custom Aura or Lightning Web Components could reproduce this functionality, but doing so would introduce unnecessary development and maintenance when Public Sector already supplies the purpose-built component. An AppExchange component creates the same unnecessary dependency.

Therefore, the lowest-customization and product-native solution is Hierarchical View .

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Hierarchical View; unified record visualization; Accounts; Visits; regulatory violations and enforcement records.

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

Salesforce's documented preparation process for installing the OmniStudio package directly validates A, B, and E . Before installing OmniStudio into an organization that doesn't already have the package, administrators must verify that the browser and Salesforce environment satisfy OmniStudio's minimum technical requirements. This includes supported browser behavior, JavaScript availability, sufficient environment capability, and a supported Salesforce edition.

Salesforce also instructs administrators to verify that Orders are enabled . OmniStudio installation tests and configuration depend on underlying Salesforce functionality, so this is an explicit prerequisite rather than an optional Public Sector data-model choice.

The same preparation procedure requires Salesforce email deliverability to use the All email access level. Salesforce specifically directs administrators to configure Access to Send Email accordingly.

Person Accounts aren't a generic OmniStudio package-installation prerequisite. They are enabled for Public Sector business requirements that need individual constituent representation, but OmniStudio can operate in organizations that don't use Person Accounts. Similarly, enabling Assets isn't identified in Salesforce's package-preparation checklist.

One current-version consideration is that Salesforce states that, beginning with newer OmniStudio licensing arrangements, the standard designer/runtime may be available without installing the legacy managed package. The question nevertheless targets the managed-package prerequisite sequence.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio Installation; package prerequisites; Orders; email deliverability; browser requirements.

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

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.

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

An unauthenticated Experience Cloud site backed by Salesforce Knowledge is the most efficient architecture for publishing frequently requested licensing and permitting information to the general public. Salesforce supports Knowledge articles in Experience Cloud and allows appropriately configured guest users to access publicly available articles without authenticating. This directly supports constituent self-service while reducing repetitive contact-center inquiries.

This approach also minimizes implementation and maintenance overhead because the agency can maintain its authoritative articles directly in Salesforce Knowledge and expose them through the Experience Cloud presentation layer. Salesforce specifically notes that an Experience Cloud site can function as a public knowledge base for unauthenticated users without requiring community licenses simply for public article access.

Option A introduces an unnecessary CMS integration and outbound API synchronization layer. Option B similarly adds unnecessary integration complexity through Lightning Out. Option D forces constituents to authenticate merely to read general application-process information, adding friction and potentially requiring additional license considerations.

The architectural best practice is therefore to keep public informational content openly accessible while reserving authentication for personalized records, applications, and protected constituent data.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud, Salesforce Knowledge, constituent self-service, guest-user access, and public information delivery.

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

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 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.

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.

Categories for Dynamic Assessment questions are configured on the Assessment Question object. Salesforce explicitly instructs administrators to create categories by navigating to the Assessment Question object's Category picklist field and adding the required values.

Categories create logical groupings of assessment questions so that designers can efficiently locate and select the correct questions for different assessment contexts. Salesforce provides examples such as Fire Safety Inspection, Roof Inspection, Electrical Inspection, Solar Permit, and Public Safety Complaint. The same architecture applies here: categories could represent Take-Away, Dining, or another relevant inspection context and then be assigned to the specific questions to which each category applies.

The critical clue is that categorization applies to specific questions . Assessment Indicator Definitions represent predefined compliance indicators used primarily in the traditional inspection model; they aren't the object on which Dynamic Assessment question-category picklist values are maintained. Assessment Task Definitions group work performed during inspection execution but don't define the category metadata of individual Dynamic Assessment questions.

Action Plans organize repeatable tasks and assessment activities and are therefore also at the wrong layer.

Salesforce additionally supports Question Sets for grouping questions by context, but the question asks specifically where new categories are created.

Study Guide Reference: Public Sector Solution Product Configuration – Dynamic Assessments; Assessment Question; Category picklist; inspection question organization.

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

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.

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

The requirement maps directly to the OmniStudio component architecture. Salesforce describes OmniStudio as the no-code/low-code suite used in Public Sector to create guided, responsive constituent applications and workflows that consume Salesforce and external data. Its principal components include OmniScripts, Integration Procedures, FlexCards, and Data Mappers , historically referred to as DataRaptors.

OmniScripts create the application-form experience. They support dynamic questions, conditional sections, navigation, validation, document collection, saved sessions, and guided application processes. Salesforce specifically states that Public Sector uses OmniScripts for applications involving licenses, permits, benefits, services, and grants.

DataRaptors/Data Mappers retrieve, transform, and save application data. Integration Procedures perform server-side orchestration and connect forms to other Salesforce or external data sources. FlexCards display contextual information and actions in compact, reusable user-interface components.

Together, these capabilities support complex application structures while allowing the agency to closely reproduce its paper application process and apply Experience Cloud branding without building the entire solution in Apex or custom Lightning Web Components.

The alternatives contain either unrelated products or unnecessarily code-intensive technologies.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; OmniScripts; DataRaptors/Data Mappers; Integration Procedures; FlexCards; Experience Cloud application forms.

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

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.

Grants Management provides native Funding Request Collaboration , making Invite Collaborators the correct design rather than implementing an email-based or custom collaboration mechanism.

Salesforce allows applicants to invite other people to collaborate directly on a Funding Request. The invitation contains a secure, time-limited link. After the invitee accepts it and has the appropriate portal identity, that collaborator can participate in completing the Funding Request. Administrators enable this capability through the Grants Management settings and configure the collaborator invitation URL, expiration period, certificate, and associated email template.

Salesforce also provides a Manage Collaborators component on Funding Requests. From this component, authorized users can invite collaborators, view pending and confirmed collaborators, and remove access when necessary. The solution also contains automation for controlling the collaborator's access to the Funding Request.

This directly satisfies the requirement for application collaboration without creating a parallel data or communication model. Option A relies on email and loses the controlled application-level collaboration experience. Option B creates unnecessary custom metadata and does not provide collaboration. Option C relies on a feed rather than the purpose-built collaborator-access capability and would not independently provide secure external access.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Funding Request Collaboration; Invite Collaborators; Manage Collaborators; grants portal security.

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

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.

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

The Public Sector inspection experience provides purpose-built Lightning components that support inspectors while they execute onsite Visits. The three applicable components are Inspection Details, Inspection Action, and Inspection Tab Container .

Inspection Details presents the contextual information an inspector needs for the Visit, such as the inspection subject, location, relevant authorization information, and related inspection data. Inspection Action exposes inspection-specific actions that allow inspectors to execute the operational steps associated with the Visit. Inspection Tab Container organizes the various inspection functions into a usable tabbed workspace, allowing the inspector to move efficiently between inspection information, assessment activities, violations, signatures, and associated tasks.

These components belong to the execution layer of Public Sector inspection management and are intended to reduce navigation between unrelated Salesforce records while an inspector is conducting field work.

Inspection Dynamic Dashboards is not one of the standard built-in inspection execution components represented by this configuration. Inspection Calendar can be useful for scheduling and viewing inspection appointments, but it does not constitute one of the three embedded Visit-execution components asked for here.

The Set 3 question itself also identifies A, D, and E as the selected combination.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Visits; Inspection Details; Inspection Action; Inspection Tab Container; inspector workspace.

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