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

Decision Explainer provides the explainability framework required to expose how Business Rules Engine calculations and determinations were reached. After a prioritization Expression Set and its supporting Decision Matrix have been configured, the rule must be integrated with Decision Explainer so that execution metadata and decision details are captured. Salesforce specifically states that integrating Business Rules Engine with Decision Explainer makes business rules available so Public Sector reviewers can access decision logs.

The Decision Explainer Log History component must then be added to the appropriate application Lightning record pages. This component displays each decision ' s timestamp, Expression Set name, and version, and allows reviewers to inspect variables, values, and formulas that contributed to the determination. Finally, reviewers require the appropriate Decision Explainer access. Salesforce identifies Decision Explainer Service Access as the permission needed to use Decision Explainer entities. A custom Screen Flow or Apex trigger is unnecessary because the platform already provides native logging, explainability entities, and the Lightning component.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Decision Explainer; Decision Explainer Log History; Public Sector User Access.

Salesforce ' s DocuSign integration provides a packaged electronic-signature lifecycle for contract documents. Salesforce explicitly documents that the integration can send a contract document for review and signatures, track the signed document and update the contract record status, and automatically invalidate a pending signature document when a newer contract document supersedes it.

These features maintain transactional integrity throughout the signature process. Sending the document initiates the controlled signature workflow. Status tracking keeps Salesforce synchronized with the state of the DocuSign envelope and enables the contract record to reflect completion. Automatic invalidation prevents a signer from executing an outdated document version after a newer authoritative version is generated. An additional Salesforce approval process is not required simply to invalidate the superseded signature document because that behavior is already part of the supported eSignature lifecycle. Similarly, changing contract contents during the signing process is not one of the standard DocuSign capabilities represented here. Document changes should occur through the controlled document revision and regeneration process before a new signature request is issued.

Study Guide References: DocuSign Integration; Electronic Signatures; Contract Documents; Signature Tracking; Superseded Document Invalidation.

A Funding Program represents the overall strategic or thematic initiative through which an organization offers funding. In this scenario, the Department of Disaster Assistance has authorization to establish a funding initiative for government agencies affected by qualifying disasters. The program itself therefore needs to hold the program-level context, objectives, requirements, and supporting material that prospective applicants use when determining whether and how to apply.

Salesforce defines a Funding Program as a thematic or strategic program that an organization champions and funds. Programs can exist in parent-child hierarchies, allowing a broad disaster-assistance initiative to contain more specific regional or purpose-based programs. Salesforce also supports attaching files to a Funding Program so supporting information can be made available to grantseekers. A Funding Request, by contrast, represents an individual application for money submitted against a Funding Program. It captures the applicant ' s specific request rather than defining the funding initiative itself. A Business License Application belongs to licensing and permitting workflows and does not model grant programs.

Study Guide References: Grants Management; Outbound Funds Data Model; Funding Program; Funding Request; Program Requirements and Supporting Files.

DocuSign is the eSignature provider integrated with the Salesforce Industries contract and document-signature framework used by this Public Sector implementation pattern. Salesforce documentation states that Salesforce Contracts uses DocuSign to support electronic signatures and that a DocuSign integration and active DocuSign account are required for the supported eSignature workflow.

The integration provides a complete signature lifecycle. Documents can be sent for review and signature, the signed contract can be tracked, the contract record status can be updated, and an unsigned contract document can automatically be invalidated when a newer version supersedes it. Salesforce also provides OmniStudio-based DocuSign functionality for sending documents generated from supported objects. The GenericDocuSign/sendEsignature OmniScript can initiate an electronic-signature transaction and the related envelope components can expose signature status. This packaged integration reduces the amount of custom development required compared with building a bespoke electronic-signature integration through APIs, custom Apex, or custom UI components. Adobe Sign, Conga, and eSignLive are not the provider identified by the Public Sector/Industries eSignature implementation represented in this scenario.

Study Guide References: eSignature Technologies; DocuSign Integration; Salesforce Contracts; OmniStudio eSignature; Contract Document Signing and Status Tracking.

The Licenses and Permits Experience Cloud site template is specifically designed for constituent-facing licensing, permitting, and inspection processes. Salesforce provides this template with preconfigured pages for assessing license or permit requirements, applying for licenses or permits, renewals, permits, complaints, applications, inspection history, and related constituent interactions.

Using this purpose-built template significantly reduces custom site development and ongoing maintenance. Public Sector also supplies dedicated components that can be added to the template ' s pages for licensing and permitting functions. These components support processes such as submitting applications, searching licenses and permits, renewing authorizations, and filing complaints. OmniStudio components such as OmniScripts can provide guided application experiences, while FlexCards can surface contextual information and actions. Maintaining these processes within a dedicated licensing-and-permitting site keeps the digital architecture aligned with the Public Sector product model rather than expanding a generic Help Center into a specialized regulatory application portal. OmniOut is principally used when OmniStudio experiences must run outside Salesforce-hosted experiences, so it is unnecessary for a standard Experience Cloud implementation.

Study Guide References: Licenses and Permits Experience Cloud Template; OmniStudio; OmniScripts; FlexCards; Constituent Digital Experiences.

Emergency Hotspots and Global Emergency View are the preconfigured analytical dashboards identified for the Emergency Response Management solution in the supplied Agentforce Public Sector material. These dashboards are intended to give emergency-management teams rapid situational insight without requiring administrators to design an analytics application from the ground up.

The Emergency Hotspots capability focuses on identifying geographic or operational areas where emergency-intake demand is increasing. Salesforce ' s Emergency Response analytics documentation confirms that the analytics application is designed to identify hotspots in which emergency requests are increasing so resources can be allocated quickly. The Global Emergency View complements that localized perspective by giving decision-makers a higher-level consolidated view of emergency operations, supporting prioritization and resource allocation across the response program. This type of packaged analytics is valuable during an active incident because agencies need operational visibility immediately rather than after a lengthy custom dashboard-development cycle. Visits is primarily an operational record type rather than the named packaged emergency dashboard in this scenario. Emergency Requests Overview is also not one of the two dashboard names identified by the supplied curriculum question.

Study Guide References: Emergency Response Management; Analytics for Emergency Response Management; Emergency Hotspots; Global Emergency View; Emergency Intake Analytics.

An Action Plan Template becomes immutable after it is published. Salesforce explicitly states that published Action Plan Templates cannot be edited or returned to Draft status.

This behavior protects the integrity of repeatable operational processes. Existing Action Plans may already have been generated from the template, and allowing administrators to alter the underlying published definition could create inconsistent inspection requirements between records created at different times. When inspection requirements change, the administrator should use the supported versioning approach: deactivate the published template if necessary, clone it to create a new template/version, modify the cloned Draft version, add or revise its tasks, checklist items, assessment content, or other configuration, and then publish the new version. Salesforce documents this same approach for application requirements and other Action Plan implementations. The absence of an Edit button is therefore expected behavior and is not resolved by adding the action to a page layout or granting additional permissions. Salesforce Support is also not required to modify the template. The same design principle applies broadly across Action Plans: all required content should be finalized before publication because the published template is treated as the controlled definition of the repeatable process.

Study Guide References: Action Plan Templates; Template Lifecycle; Draft and Published Status; Cloning Templates; Inspection Action Plans; Version Management.

Employee Experience for Public Sector brings together employee-facing service capabilities intended to give government workers a centralized digital workplace for accessing information, obtaining support, and completing common employee-service processes.

Employee Workspace supplies the employee-facing environment where users can access relevant services, information, and productivity capabilities from a unified experience. HR Service Center supports structured employee requests and human-resources service delivery, allowing HR teams to manage employee cases and provide consistent support. Employee Concierge provides a guided entry point through which workers can locate assistance and connect with relevant employee services. Together, these capabilities align with the Employee Experience objective of improving how public employees obtain organizational information and support while reducing fragmented service interactions. Workplace Strategy Planner and Workplace Command Center focus on workplace or physical-location planning and operational workplace management rather than the core employee-service experience represented by this question. They therefore belong to a different functional area from the employee workspace, HR service delivery, and concierge capabilities.

Study Guide References: Employee Experience for Public Sector; Employee Workspace; HR Service Center; Employee Concierge; Employee Service Delivery.

A formal approval process is appropriate because the requirement involves conditional manager authorization together with a persistent, auditable approval history. Salesforce approval processes define the conditions under which records enter approval, who receives each approval request, what happens on approval or rejection, and any subsequent automated actions.

Bobahaven can configure entry or step criteria so the additional approval is required when the application ' s duration exceeds 12 months. The approver can be determined through the submitter ' s or record owner ' s Manager hierarchy field, allowing the request to be dynamically routed to the appropriate manager. Salesforce explicitly supports automated approver assignment through hierarchical fields such as Manager. Approval processing also provides the traceability required for regulatory compliance. Approval History records the progress of the request and identifies approval activity, while Salesforce supports reporting on historical approval-process instances and individual steps. Reassigning record ownership through Flow does not constitute formal approval. A Chatter request is collaborative communication rather than a controlled authorization record, and escalation rules serve different process requirements.

Study Guide References: Approval Processes; Approval Entry Criteria; Manager-Based Routing; Approval History; Licensing and Permitting Governance and Auditability.

A Screen Flow provides the most flexible declarative experience for simplifying Visit creation. Instead of requiring users to navigate through related lists and manually populate every field, the flow can present only the fields required for the specific inspection process, prepopulate known values, apply validation, derive contextual values from the originating application, and create the Visit record automatically.

Salesforce ' s standard inspection documentation confirms that Visits are normally created from the Visits related list on a license application or public complaint and require information such as location, account, context, visit type, schedule, and inspector. A Screen Flow can streamline that sequence into a guided interaction launched directly from the application page. Flow is particularly appropriate because the requirement is user-interface simplification and record creation rather than custom programmatic processing. The flow can receive the application ' s record ID as context, retrieve related information, display the appropriate input controls, and create the Visit. Moving a related list does not eliminate manual data entry. A predefined action can prepopulate static or predictable fields, but a Screen Flow provides significantly greater control over conditional fields, validation, lookups, and multi-step creation logic.

Study Guide References: Inspection Management; Visit Creation; Salesforce Flow; Screen Flow; Business License Application; Individual Application.

Intelligent Form Reader is the Public Sector capability designed to extract structured information from scanned forms and identity documents. It combines document processing and OCR-based extraction so data contained within a driver ' s license, passport, or other submitted document can be interpreted and mapped to Salesforce data.

Salesforce ' s Intelligent Document Automation architecture allows agencies to take paper or scanned documents and extract information into digital application records. This reduces manual transcription and allows reviewers to validate submitted information against the source document. For identity verification scenarios, the configured extraction process identifies fields such as name or date of birth from the document and maps those fields to the appropriate target Salesforce record. The resulting value can then be compared with information supplied in the application. Salesforce Files, Attachments, or Content can store the driver ' s license or passport, but storage does not perform document interpretation, OCR extraction, or field mapping. Intelligent Form Reader supplies the intelligence layer required to turn the uploaded document into structured information that can participate in validation.

Study Guide References: Intelligent Form Reader; Intelligent Document Automation; OCR and Data Extraction; Identity Documents; Application Field Mapping.

Visual Studio Code together with Salesforce Developer Experience (DX) is the documented deployment mechanism for Lightning Web Components contained in Public Sector process packages. Salesforce ' s current Public Sector deployment procedure explicitly states that after importing process packages, administrators use Visual Studio Code and Salesforce DX to deploy the package ' s Lightning Web Components into the target Salesforce org.

The deployment workflow involves creating a Salesforce DX project in Visual Studio Code, importing the Lightning Web Components downloaded with the Public Sector process package, authenticating the target org, and then deploying the source metadata. This is required because the Lightning Web Component portion of the process package is Salesforce metadata and must be deployed through the developer tooling workflow. Change Sets can migrate many Salesforce configuration components between related orgs, but they are not the prescribed mechanism for installing these downloaded Public Sector process-package LWCs. The ANT Migration Tool is likewise not the documented deployment workflow for these components. Visual Studio Code without the Salesforce DX tooling also does not provide the complete project, authentication, metadata, and deployment framework required by the published Public Sector procedure.

Study Guide References: Public Sector Process Library; DataPacks/Process Packages; Lightning Web Components; Visual Studio Code; Salesforce DX Deployment.

Business Rules Engine separates reusable lookup logic from procedural rule execution. Decision Matrices contain business-rule lookup tables with defined input and output columns. When supplied with input values, the matrix searches for the applicable row and returns its configured output. Salesforce describes Decision Matrices as useful for implementing complex rules in a systematic and readable manner.

Expression Sets orchestrate more sophisticated decision logic. They can execute calculations, conditional branches, aggregations, constants, variables, and matrix lookups. An Expression Set can therefore call a Decision Matrix at the appropriate point in a licensing or eligibility process and use the returned value in subsequent calculations or decisions. Salesforce specifically documents Expression Sets calling Decision Matrices and consuming the output corresponding to the matching matrix row. This architecture allows policy data and procedural calculations to be maintained independently. For example, a licensing fee table can be maintained in a Decision Matrix while an Expression Set calculates intermediate values, invokes the matrix, and produces the final fee. The other options reverse these functions or mischaracterize the data interface. Decision Matrices do not perform the broader sequence of calculations attributed to Expression Sets.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Licensing Business Rules; Declarative Decision Automation.

Public Sector Case Analytics is designed to provide prebuilt analytics for case-management performance, including case-resolution duration, workload, historical trends, case-owner activity, and service effectiveness. The decisive requirement is that Bobahaven has not historically tracked case duration and wants ongoing trend analysis without introducing unnecessary customization.

Salesforce explicitly documents that when an organization doesn ' t have a field that tracks case duration, Public Sector Case Analytics uses its own CRM Analytics formula. For closed cases, the calculation uses the case opening and closing dates; for open cases, the current date is used. Business-hours duration calculations can also be incorporated when configured. The application ' s prebuilt dashboards provide metrics such as average time to close and historical case-status duration, making it suitable for comparing current and prior operational performance. Creating a new custom field would only begin collecting duration prospectively and would add configuration overhead. A standard report with a custom formula also lacks the breadth of the prebuilt analytical model. Leveraging Public Sector Case Analytics therefore minimizes customization while supplying the required historical and ongoing trend analysis.

Study Guide References: Public Sector Case Analytics; CRM Analytics; Case Duration Metrics; Case Overview; Historical Case Analytics.

Document processing for a Business License Application requires Document Checklist functionality, an appropriate Document Type, and controlled user permissions. Salesforce ' s current Public Sector configuration guidance first directs administrators to turn on Checklist Items with Attachments under Document Checklist Settings. This activates the document-checklist framework used to associate required documents with applications.

The administrator then creates an appropriate Document Type, such as Business License Application, so submitted documents can be categorized and used consistently in document-management and extraction workflows. Salesforce ' s Intelligent Document Automation documentation likewise identifies Document Types and Document Checklist Items as core components for managing documents received from constituents. Access must then be restricted to the intended intake officer. Salesforce directs administrators to assign the Document Checklist license and corresponding permission set to users who work with application documents. Object, field, and application-form permissions should be limited according to the intake officer ' s responsibilities. Notes and Attachments is not the Document Type framework used by Intelligent Document Automation. The secure configuration therefore combines Document Checklist enablement, a purpose-defined Document Type, and the appropriate permission assignments.

Study Guide References: Intelligent Document Automation; Document Checklist Settings; Document Types; Application Forms; Document Permissions and Access Control.

Customer Community is designed for high-volume business-to-consumer Experience Cloud implementations in which very large populations of external users require access to selected Salesforce functionality. Salesforce specifically documents that Customer Community licenses can support 100 million users, whereas Customer Community Plus supports substantially fewer users because it includes capabilities such as roles and more extensive sharing functionality.

Salesforce also classifies Customer Community users as high-volume community users. These users do not receive Salesforce roles, which avoids the role-hierarchy calculation overhead that would become impractical at very large scale. This architectural characteristic is particularly important for public-sector portals serving millions of residents, customers, borrowers, or other external constituents. Partner Community is oriented toward business-to-business partner relationship management and access to sales-oriented capabilities. Channel Account licensing is also targeted toward partner/channel scenarios rather than massive constituent-facing portals. Customer Community Plus adds reporting, dashboards, roles, and standard sharing features, but those features increase the complexity and supported-user considerations and are unnecessary when the dominant requirement is extreme external-user scale.

Study Guide References: Experience Cloud Licensing; Customer Community; High-Volume External Users; Customer Community Plus; Public Sector Constituent Portals.

Salesforce Shield is the appropriate add-on when an organization requires enhanced security, auditability, monitoring, and data-protection controls. Shield is a suite of security products designed to add additional layers of security, compliance, and governance to Salesforce applications. Its core capabilities include Event Monitoring, Field Audit Trail, and Shield Platform Encryption, with Data Detect also available for sensitive-data discovery.

For a public sector implementation, Shield Platform Encryption strengthens protection for sensitive information stored at rest. Field Audit Trail provides long-term field-level historical information that supports regulatory audits, governance, and forensic review. Event Monitoring provides detailed visibility into user activity and data access, helping security teams detect suspicious behavior and demonstrate operational monitoring controls. Salesforce specifically describes these capabilities as relevant to regulatory compliance and security governance. Setup Audit Trail and standard Field History Tracking provide narrower auditing functions, while Classic Encryption does not deliver the comprehensive monitoring, encryption, and audit framework represented by Shield. Shield does not itself confer ISO 27001 certification, but it provides significant technical controls that can support an organization ' s compliance program.

Study Guide References: Salesforce Shield; Platform Encryption; Event Monitoring; Field Audit Trail; Public Sector Security and Compliance.

Shield Platform Encryption and Event Monitoring provide complementary controls for protecting and monitoring sensitive information such as protected health information.

Platform Encryption protects sensitive Salesforce data at rest while preserving critical application functionality. Salesforce specifically identifies Platform Encryption as a capability that can help organizations address requirements associated with storing PHI, personally identifiable information, confidential data, and other sensitive information. Organizations retain control over encryption keys and can determine which supported fields and data categories are encrypted. Event Monitoring addresses the monitoring and audit side of the security model. It captures detailed information about user activity and system interactions, including who accesses Salesforce data, when access occurs, and the context of that activity. These event records can support security investigations, threat detection, compliance monitoring, and integration with external security platforms such as SIEM solutions. Together, these tools provide defense in depth: encryption protects sensitive PHI stored within the platform, while Event Monitoring supplies visibility into access and usage. Field Audit Trail is valuable for long-term field-change retention, and Setup Audit Trail tracks administrative configuration changes, but the pair explicitly aligned to PHI protection in the supplied scenario is Platform Encryption and Event Monitoring.

Study Guide References: Salesforce Shield; Platform Encryption; Event Monitoring; Protected Health Information; Public Sector Security and Compliance.

Public Sector ' s inspection and complaint capabilities are designed to maintain operational traceability from a reported concern through investigation and regulatory follow-up. Salesforce supports Public Complaint records for constituent-reported issues and allows an agency to create visits directly from complaints so inspectors can investigate concerns onsite. The complaint can also surface related visits, regulatory code violations, enforcement actions, and supporting documentation.

Consequently, the agency should configure the standard Inspections and Visits framework and associate the resulting inspection activity with the relevant permit application. Salesforce describes Public Sector inspections as the mechanism for evaluating regulatory compliance through onsite visits, standardized assessment questions, recorded findings, violations, and enforcement activity. Cases can provide the managed investigation or service record associated with the reported issue and can participate in the broader Public Sector complaint and investigative data model alongside Business License Applications, Public Complaints, Visits, and regulatory records. Linking the appropriate case and field-inspection activity to the existing permit preserves the context required by reviewers and enforcement personnel. Business Rules Engine is intended for structured rule evaluation rather than determining whether a complaint is inherently valid. Action Plans can organize repeatable work but are not the essential linkage requested here.

Study Guide References: Public Complaints; Cases; Inspections; Visits; Permit Applications; Licensing, Permitting and Inspections Data Model.