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

Emergency Response Management provides a purpose-built Public Sector architecture for rapidly exposing emergency services to constituents. The appropriate implementation combines the preconfigured ERM digital-experience template with the prebuilt Emergency Service Request flow.

The template provides a starting point tailored to emergency-response scenarios rather than requiring the agency to assemble a generic portal from the ground up. Using the packaged experience reduces implementation time, preserves alignment with the Public Sector data model, and simplifies maintenance. The Emergency Service Request flow supplies the guided intake process through which a constituent can provide the basic information required for an emergency request. Public-facing Salesforce flows can be embedded in Experience Cloud so external users can submit information through a structured digital process. Creating a custom Case record type and adapting a generic support form would duplicate available emergency-response functionality. Likewise, the Help Center template is primarily designed for knowledge and support use cases rather than emergency program intake.

Study Guide References: Emergency Response Management; Emergency Service Request; Experience Cloud; Emergency Digital Experience; Public-Sector Emergency Intake.

An OmniStudio Integration Procedure is the appropriate orchestration layer because the transaction requires information from multiple sources and several server-side processing steps. Salesforce describes Integration Procedures as declarative server-side processes that can retrieve, transform, and send information between Salesforce and external systems, perform REST API calls, apply conditional processing, and execute several actions within a single server request.

In this scenario, the Integration Procedure can retrieve the base permit fee from the external system, retrieve the site or address information and applicable discount from the Salesforce custom object, apply the required processing logic, and return the resulting fee to the calling application experience. Salesforce explicitly recommends Integration Procedures when data must be accessed from multiple data-source types or when processing cannot be handled by a simple single-object extraction. A Data Mapper is optimized for comparatively focused Salesforce data operations and transformations. An OmniScript controls the guided user interaction, while a FlexCard primarily presents information and actions. Neither replaces the server-side orchestration required to combine external fee information with Salesforce data.

Study Guide References: OmniStudio Integration Procedures; External Data Integration; Data Mappers; OmniScripts; Licensing and Permitting Fee Processing.

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.

An Action Plan Template targeted at Account is the appropriate configuration because Grants Management due diligence is performed against the grantseeking organization represented by the Account record. Salesforce explicitly recommends using Action Plans on Accounts to define due-diligence steps, required tasks, and documentation that must be collected and verified.

The Action Plan Template acts as the reusable blueprint. It can include Tasks for activities such as validating organization details and Document Checklist Items for collecting statutory or financial documentation. When the template is published, grant managers can instantiate separate Action Plans against an Account, allowing multiple due-diligence processes to proceed in parallel while retaining their own tasks, ownership, deadlines, and verification records. Salesforce specifically supports Account as the target object when creating Grants Management due-diligence Action Plan Templates. An individual Action Plan is an execution instance rather than the reusable configuration requested in the scenario. Path is designed to guide records through stages, and Support Processes control Case status values; neither provides the structured task-and-document framework required for organizational due diligence.

Study Guide References: Grants Management; Due Diligence; Action Plan Templates; Accounts; Tasks; Document Checklist Items; Verification Checks.

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.

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.

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.

The Licenses and Permits Experience Cloud template is the purpose-built template for constituent-facing licensing, permitting, and related regulatory interactions. Salesforce explicitly instructs administrators to select the Licenses and Permits template when creating an Experience Cloud site for Public Sector licensing and permitting use cases.

The template supplies a preconfigured foundation through which constituents can perform activities such as applying for licenses and permits, filing complaints, viewing inspection history, and interacting with other regulatory processes. Because the structure and supported Public Sector components are already aligned to the Licenses, Permits, and Inspections data model, implementation teams can deploy a constituent portal faster and with less custom development than if they started with a generic Experience Cloud template. The Customer Account Portal template is designed for broader customer account self-service and is not specifically configured around Public Sector regulatory processes. Likewise, there is no generic template named simply Public Sector Solutions Template that replaces the dedicated Licenses and Permits experience in this scenario. The specialized template is particularly appropriate when minimizing implementation effort and maintaining compatibility with standard Public Sector components are higher priorities than building a completely bespoke user interface.

Study Guide References: Experience Cloud; Licenses and Permits Template; Constituent Portal; Licensing and Permitting; Inspections; Public Sector Digital Experience.

For implementations using the OmniStudio managed-package runtime, Tracking Service captures detailed interaction and performance information about OmniStudio components. Salesforce describes the Tracking Service as an event-tracking capability that records actions performed by users and can be used to identify process-improvement opportunities.

A directly relevant example is measuring how long users take to complete individual steps in an OmniScript. If one stage of a licensing application consistently requires substantially more time than expected, the implementation team can inspect the interaction data and determine whether the step contains unnecessary fields, confusing navigation, inefficient integrations, or another processing bottleneck. Tracking information can also capture events from Integration Procedures and Cards and store the results for analysis. Salesforce ' s managed-package architecture combines Tracking Service with OmniAnalytics to analyze user interaction and component performance. For OmniStudio standard runtime, Salesforce now provides OmniAnalytics rather than the legacy managed-package Tracking Service, so runtime architecture should be considered during implementation. Event Monitoring is a broader Salesforce security/activity product, while Field History Tracking records changes to Salesforce fields. Neither provides the same process-level OmniStudio interaction timing.

Study Guide References: OmniStudio Tracking Service; OmniAnalytics; OmniScript Event Tracking; Integration Procedure Tracking; Process Profiler; Performance Optimization.

A standardized eligibility and prioritization solution requires three complementary layers: structured applicant intake, declarative rule data, and executable decision logic. An OmniScript provides the guided application experience through which the grant seeker supplies the information required for eligibility assessment and prioritization. OmniScripts support multi-step questions, validations, conditional presentation, and integration with downstream rule processing.

A Decision Matrix stores decision data such as thresholds, categories, eligibility conditions, or scoring mappings. An Expression Set orchestrates the logic: it consumes application data, invokes the appropriate decision matrices, evaluates expressions, and returns eligibility or prioritization results. Salesforce ' s Business Rules Engine architecture uses Decision Matrices and Expression Sets together for declarative decision processing. A closely related Public Sector eligibility workflow is explicitly configured by customizing an OmniScript, creating a Decision Matrix, building an Expression Set, and then activating the experience. This architecture separates frequently changing policy data from the constituent-facing form and from executable rule orchestration, which improves maintainability and auditability. Web-to-Lead is designed to capture leads, while Web-to-Case creates service cases. Neither provides the purpose-built guided application and Business Rules Engine integration required for eligibility-based grant prioritization.

Study Guide References: OmniScript Designer; Business Rules Engine; Decision Matrices; Expression Sets; Grant Eligibility and Prioritization.

Volunteer Management provides structured functionality for organizing volunteer opportunities, shifts, registrations, and volunteer participation. A core requirement of volunteer coordination is maintaining accurate staffing information as assignments and shifts change. Consequently, volunteer-capacity information such as registered volunteers and remaining staffing requirements is maintained as shift participation changes, including when scheduled work is canceled.

Salesforce ' s current Volunteer Management documentation confirms the broader functional model: organizations can create volunteer opportunities, define shifts and required staffing, allow volunteers to browse and register for opportunities through Experience Cloud, and track the hours contributed by volunteers. Salesforce also explicitly identifies Experience Cloud capabilities that let volunteers register for roles and enable organizations to track volunteer hours. This makes volunteer project registration and time reporting native elements of the volunteer-management lifecycle. Expense-reimbursement processing is not one of the defining Volunteer Management capabilities described for this scenario, and a volunteer chatbot is not the core package feature being tested. The operational emphasis is on volunteer recruitment, scheduling, shift coverage, participation, and service-hour tracking.

Study Guide References: Emergency Response Management; Volunteer Management; Volunteer Projects; Volunteer Shifts; Volunteer Registration and Hours Tracking.

Business Rules Engine supports calculations across collections of values by using Aggregate Groups and Aggregate steps within an Expression Set. This is the appropriate pattern when a single application contains multiple selected permits and each permit contributes a fee to the final amount.

Salesforce documents that an Aggregate Group executes the preceding steps once for each set of input values and then aggregates the resulting values according to the configured aggregation logic. Within the Aggregate Group, the Aggregate step can perform SUM, AVG, MAX, or MIN operations. For this licensing scenario, each selected permit can be evaluated to determine its applicable fee. The Expression Set then places the repeated evaluation inside an Aggregate Group, and an Aggregate step using SUM produces the application ' s total permit fee. A custom Lightning component is unnecessary because Business Rules Engine already provides declarative list aggregation. Permission sets are required for appropriate design or runtime access, but assigning permissions does not implement the actual multi-permit fee calculation. This configuration keeps fee policy inside Business Rules Engine, making the logic easier to maintain and reducing the need for custom code.

Study Guide References: Business Rules Engine; Expression Sets; Aggregate Group; Aggregate Step; SUM Function; Licensing and Permit Fee Calculation.

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.

Public Sector provides a standard Business Regulatory Authorization Type Dependency model specifically for representing prerequisite and dependent licenses or permits. The administrator defines the first required authorization as the Parent Business Regulatory Authorization Type and the subsequent authorization as the Dependent Business Regulatory Authorization Type.

This configuration allows the agency to model relationships such as a business license that must be obtained before a fire permit, operating permit, or other dependent authorization. The standard data model should be used instead of recreating dependency logic with custom objects or hard-coded OmniScript conditions. Salesforce also provides the Permit component for displaying permits associated with a particular business type. In the Licenses and Permits Experience Cloud experience, constituents can view the licenses and permits required for their business type together with dependency information. This approach minimizes custom development and ensures that changes to permit dependencies are maintained declaratively in regulatory configuration data rather than embedded in presentation logic. It also keeps the Experience Cloud implementation aligned with the standard Public Sector regulatory data model.

Study Guide References: Business Regulatory Authorization Type; Authorization Dependencies; Business Types; Permit Requirements; Licenses and Permits Experience Cloud.

User Stories and a Functional Requirements Specification (FRS) are key implementation artifacts because they translate business objectives into requirements that can be designed, configured, tested, and accepted.

User Stories describe required behavior from the perspective of a particular persona or stakeholder. They help implementation teams break large public-sector processes into manageable requirements with clear outcomes and acceptance criteria. For example, a permitting implementation can contain separate stories for applicants, intake officers, inspectors, supervisors, and licensing administrators. The Functional Requirements Specification provides a more consolidated description of what the solution must accomplish. It documents functional processes, business rules, data requirements, integrations, security considerations, roles, and expected system behavior so that the implementation team has a controlled reference for solution design and validation. This aligns directly with Salesforce ' s official Agentforce Public Sector exam objectives. The exam guide expects consultants to document business needs and customer outcomes and, given a customer scenario, map and document the business process, personas, and requirements. A Marketing Plan concerns external promotion rather than solution requirements. A Budget Plan is part of project and financial governance but is not one of the two functional implementation documents identified in this context.

Study Guide References: Requirements Gathering; User Stories; Functional Requirements Specification; Personas; Business Process Mapping; Solution Design Documentation.

Deploying the DataPack or process-package Lightning Web Component files to the Salesforce org is the step that requires development tooling. Salesforce ' s documented Public Sector deployment procedure explicitly instructs administrators to use Visual Studio Code and Salesforce Developer Experience (DX) to deploy Lightning Web Components that are downloaded as part of Public Sector process packages.

The deployment workflow requires creation of a Salesforce DX project, placement of the supplied Lightning Web Component source into the project structure, authorization of the destination Salesforce org, and source deployment through the Salesforce extensions and DX tooling. This differs from importing the declarative portions of a process package. Downloading Public Sector process packages or DataPacks is performed through the relevant Salesforce process-library mechanisms and does not itself require custom development. Similarly, activating imported OmniScripts or Integration Procedures is an administrative OmniStudio operation. Installing the OmniStudio package is package installation and setup rather than source-code deployment through VS Code. The agency should therefore ensure that somebody with basic Salesforce DX deployment capability is available specifically for the Lightning Web Component deployment portion of the implementation.

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

FlexCards are designed to present contextual information at a glance and expose relevant actions that users can execute directly from the card. Salesforce defines a FlexCard as a configurable information block that combines pertinent data with links or actions for processes within a specific context.

This makes option B a valid use case. A FlexCard can retrieve and display information from one or more configured data sources and summarize complex or related data into a concise, quick-glance user interface. Salesforce also documents FlexCards as presenting contextual data and actions together. Option D is also appropriate because FlexCards support numerous actions. Administrators can configure them to launch an OmniScript, navigate to another page or application, display a flyout, trigger data operations, or initiate other supported processes. A homepage FlexCard can therefore provide shortcuts into commonly used workflows. A multi-page questionnaire is more appropriately implemented with an OmniScript, whose primary purpose is guided interaction. Likewise, although FlexCards can support actions and data updates, complex inline tabular editing and calculation is not the primary use case represented here.

Study Guide References: OmniStudio FlexCards; Contextual Information; Data Sources; FlexCard Actions; OmniScript Launching; Quick-Glance User Experiences.

Action Plans provide the standard Public Sector mechanism for organizing, assigning, tracking, and completing repeatable groups of activities. Salesforce describes Action Plans as collections of tasks or checklist items that support repeatable business processes, with individual tasks capable of carrying an owner, priority, and deadline. This structure allows multiple reviewers, inspectors, caseworkers, and other employees to collaborate while retaining visibility into work status and accountability.

For inspections specifically, Public Sector uses Action Plan Templates to define the tasks required for a particular type of inspection visit. Templates can include assessment task definitions, required activities, task sequencing, and signature tasks. Published templates can then generate standardized action plans for individual visits, producing consistent inspection execution across teams. OmniStudio is suited to guided user interactions and integration orchestration, Business Rules Engine evaluates declarative decision logic, and Data Mappers/DataRaptors handle data transformation and persistence. None serves primarily as the collaborative task-management framework for inspection execution. Action Plans directly satisfy both requirements: automated creation of repeatable inspection work and coordinated execution by internal teams.

Study Guide References: Action Plans; Action Plan Templates; Inspection Visits; Assessment Tasks; Public Sector Inspections.

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.

DataRaptor—called OmniStudio Data Mapper in current Salesforce terminology—provides the declarative data-mapping capability required to convert incoming application data into records on Salesforce objects.

A Data Mapper Load accepts JSON, XML, or custom-formatted input and creates or updates Salesforce records according to configured field mappings. Salesforce explicitly states that Data Mapper Load writes input data to Salesforce objects and can populate multiple mapped records without requiring custom Apex. This capability is particularly relevant when the source application runs outside Salesforce. Salesforce provides a Data Mapper REST API through which an external system can issue a POST request containing the application payload and invoke a Data Mapper Load to update the appropriate Salesforce objects. For the agency, grant application information collected in the existing external portal can therefore be transformed and mapped into Agentforce Public Sector records such as constituent, application, or funding-related objects. Integration Procedures provide broader server-side orchestration and can themselves invoke Data Mappers, but the specific requirement emphasized here is mapping submitted data into Salesforce objects. FlexCards are presentation components, while OmniOut is primarily used to run OmniStudio UI components outside Salesforce rather than serving as the direct object-mapping mechanism.

Study Guide References: OmniStudio DataRaptors/Data Mappers; Data Mapper Load; REST API; External Portal Integration; Public Sector Grant Application Data Mapping.

Grants Management and the Outbound Funds Module provide the Salesforce funding data model and grant-management capabilities required to manage applications, awards, disbursements, and expenditure tracking.

Salesforce documents that Grants Management leverages the Outbound Funds Module data model. A Funding Request represents the application for funding and is the primary record through which the grantmaker evaluates and administers the applicant ' s request. Outbound Funds Module provides the underlying framework for tracking funding requests and outgoing funds such as grants and scholarships. Salesforce ' s feature comparison also shows that Grants Management and Outbound Funds support management of Disbursements against Funding Requests. Expenditure management can associate disbursements with accounting allocations, allowing the organization to categorize how awarded funding was used. This structure supports Foodvania ' s requirement to distinguish categories such as mortgage arrearage and utility assistance while retaining an auditable relationship back to the funding request and award. Grants Management supplies the richer grantmaker workflow—including application, review, requirements, portal, and grant lifecycle functionality—while the Outbound Funds architecture provides the foundational outgoing-funds records.

Study Guide References: Grants Management; Outbound Funds Module; Funding Request; Disbursement; Expenditure Tracking; Grant Review and Award Management.

Salesforce Knowledge combined with a public, unauthenticated Experience Cloud site provides the most direct self-service architecture for this requirement. Salesforce Knowledge centralizes permit and licensing guidance in managed articles, while Experience Cloud can expose approved Knowledge content directly to guest users. Salesforce explicitly supports making Knowledge articles available to unauthenticated users when the appropriate article visibility, guest-user access, and sharing configuration are established.

This architecture minimizes integration overhead because the agency does not need to maintain outbound API synchronization with a separate CMS or develop a Lightning Out implementation. It also avoids imposing an unnecessary authentication step on constituents who merely need general process information before starting an application. Articles can be updated centrally in Salesforce and surfaced immediately through the digital experience according to publication and visibility settings. An authenticated site is appropriate when information is constituent-specific or access must be restricted, but general licensing instructions, FAQs, prerequisites, and application guidance can be exposed publicly. This lowers call-center demand while preserving Salesforce as the authoritative content-management location.

Study Guide References: Experience Cloud for Public Sector; Salesforce Knowledge; Guest User Access; Public Self-Service; License and Permit Digital Experiences.

Grants Management provides the complete grantseeker portal capability required for this scenario. Salesforce describes Grants Management as enabling organizations to launch a portal where grantseekers can discover funding opportunities, apply for funding, view application status, and submit ongoing progress information for awarded grants.

The portal is implemented through Experience Cloud using the Grantee Portal template. Salesforce states that this preconfigured template provides a place where applicants can view available Funding Programs, submit applications, and manage their applications after submission. The Grants Management workflow also supports application materials and attachments, allowing supporting documentation to be incorporated into the funding-request process. Although Grants Management uses the Outbound Funds Module data model underneath its grantmaking functionality, Salesforce distinguishes the products functionally. Grants Management provides enhanced portal capabilities, application workflows, self-registration, application mapping, review workspaces, Action Plans, and other grantmaker functionality beyond the basic Outbound Funds foundation. Foodvania therefore does not need to design a separate relief portal around the underlying Outbound Funds Module. Grants Management supplies the packaged portal experience required for external recipients to apply, provide supporting information, and monitor application status.

Study Guide References: Grants Management; Grantee Portal; Experience Cloud; Funding Programs; Funding Requests; Grantseeker Application Management.

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.

Volunteer Management for Community is the permission set license intended to extend the external user ' s base community license with access to Volunteer Management capabilities. Public Sector external users require both an appropriate Experience Cloud identity and the product-specific entitlement necessary to use specialized Public Sector functionality. Salesforce explains generally that permission set licenses extend the capabilities available from a user ' s base license and that Public Sector users require the applicable permission sets and permission set licenses for the features they use.

For a volunteer-facing digital experience, the required functionality includes access to volunteer opportunities or projects, registration activities, associated volunteer assignments or shifts, and related participation processes. The Volunteer Management community entitlement is aligned directly with that functional scope. Community Response for Public Sector and Emergency Response for Public Sector relate to broader emergency/community-response use cases and do not specifically represent the external Volunteer Management entitlement. Public Sector for Community provides broader Public Sector access but does not replace the dedicated Volunteer Management permission set license when volunteer functionality is required. Assigning the specialized permission set license follows Salesforce ' s least-privilege model by granting the feature entitlement appropriate to the user ' s actual external role.

Study Guide References: Volunteer Management; Experience Cloud Volunteer Access; Permission Set Licenses; Public Sector External Users; Community Volunteer Experience.

An Action Plan Template can standardize the recurring work required for each Business License Application while also including a Document Checklist Item for the applicant ' s driver ' s-license image.

Action Plan Templates serve as reusable blueprints containing Tasks, Document Checklist Items, or a combination of both. Salesforce documentation explicitly describes these templates as structures for defining repeatable work and required supporting documentation. Public Sector ' s Intelligent Document Automation guidance further confirms that Document Checklist Items can be incorporated into Action Plan Templates and are automatically created in Action Plans generated from those templates. This architecture maps cleanly to the scenario. Tasks can represent the background check, entry of results into the external system, recommendation preparation, and submission for approval. The driver ' s-license upload is represented by a Document Checklist Item associated with the required document type. The resulting Action Plan gives reviewers a consistent operational checklist while still allowing application-specific work to be managed where required. Option C contradicts the documented ability to add Document Checklist Items to Action Plan Templates. The other restrictive statements do not reflect the flexibility of Action Plans for managing and extending operational work.

Study Guide References: Action Plans; Action Plan Templates; Tasks; Document Checklist Items; Business License Application; Intelligent Document Automation.