AP-222 Salesforce Accredited Agentforce 360 for Public Sector Professional Questions and Answers

Public Sector provides native inspection configuration for automatically generating regulatory-code violations based on an inspector's assessment response. Salesforce documents this through the Assessment Question Status field on the Inspection Assessment Indicator object. The standard status values include Pass, Fail, NA, and Issue. An administrator can configure a status such as Fail as a violation-producing value; when an inspector records that result, Public Sector automatically creates the associated regulatory code violation record.

This native configuration makes option C the intended answer. Although the option refers to the field generically as "Results," its described mechanism—editing assessment-result/status picklist values and designating them as violations—matches Salesforce's documented architecture.

Option A introduces unnecessary Flow automation for functionality already supplied declaratively. Option B incorrectly places violation-generation behavior on an Action Plan Template. Action Plans define the inspection tasks but don't determine whether a particular assessment result constitutes a regulatory violation. Option D invents an auto-generate mechanism on a Violation Type/Assessment Indicator relationship that isn't the documented configuration approach.

Verified correction: the source image marks D, but Salesforce's official current configuration supports C .

Study Guide Reference: Public Sector Solution Product Configuration – Inspections Setup; Inspection Assessment Indicator; Assessment Question Status; Regulatory Code Violations.

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

Grants Management is the appropriate product because it includes the grantseeker portal experience required for external applicants to discover funding opportunities, apply online, supply application information, and manage their applications.

Salesforce describes the Grants Management managed package as providing program management, financial commitments, relationship management, and a grantee portal . The portal is specifically intended to improve the applicant/grantee experience while allowing grantmakers to manage the complete funding lifecycle.

Salesforce's portal setup documentation explains that the Grantee Portal Experience Cloud template provides a location where people can review available Funding Programs, apply to programs, and manage their applications. Grants Management also supports enhanced application flows, organization self-registration, application mapping, collaboration, and other functions beyond the lightweight funding-management capabilities of Outbound Funds Module.

This matches Foodvania's requirement for a constituent-facing relief application experience with supporting documentation and ongoing application management.

Outbound Funds Module supplies the underlying funding data model and can manage Funding Programs, Funding Requests, reviews, and disbursements. However, Grants Management provides the richer preconfigured portal and application experience targeted by the scenario. Therefore, it is unnecessary to combine the products as option A suggests simply to obtain the applicant-facing capabilities described.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management; Grantee/Grants Portal; Funding Programs; Funding Requests; application management and constituent self-service.

Intelligent Form Reader is the appropriate capability because it is specifically designed to extract structured information from uploaded documents through optical character recognition and then use that extracted information to create, update, or verify Salesforce record data. Salesforce documentation explicitly describes a validation scenario in which a person's birth date stored in Salesforce is compared against the birth date extracted from a scanned passport. This directly matches the requirement in the question.

For identity documents such as driver's licenses and passports, Intelligent Form Reader can use document types, extraction templates, field mappings, and Amazon Textract capabilities to identify values such as date of birth. The extracted field can then be mapped to the corresponding Salesforce field and used as part of an automated verification process.

Content, Attachments, and Files provide mechanisms for storing or associating documents, but none independently performs OCR-based extraction and validation of document data. They can participate in document storage, but they do not satisfy the stated automation requirement.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Intelligent Form Reader; document extraction, OCR, document types, field mappings, and identity-document verification.

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

Action Plans are intended for exactly this type of repeatable licensing workflow. Salesforce identifies Business License Application as a supported target object for Action Plan Templates, allowing the agency to define standardized reviewer activities that are instantiated whenever the plan is applied to a specific application.

Salesforce also supports Document Checklist Items within action-plan-based document-processing workflows. Document checklist items identify the specific documents that applicants or staff must supply, such as a driver's license. When a document checklist item is included in a published Action Plan Template, it can be propagated to Action Plans created from that template, creating consistent document requirements.

Therefore, option A accurately combines the correct target record—Business License Application—with document tracking for the required identity-document image.

The other statements are overly restrictive. Salesforce supports Action Plan task dependencies in applicable Public Sector implementations, including prerequisite and successor task relationships, so dependent execution can be modeled declaratively. Action Plans also use ordinary task records, and Salesforce supports ad hoc task creation when configured, so staff can supplement standardized plans when case-specific work is necessary.

This gives the agency both governance and flexibility: required standard tasks come from the template, while exceptional application-specific work can still be accommodated.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; Action Plan Templates; Business License Applications; Tasks; task dependencies; Document Checklist Items.

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

The Funding Program represents the funding opportunity or strategic initiative established by the grantmaking organization. Salesforce describes Funding Program as representing a thematic or strategic program that an organization champions and funds. Programs can also be organized hierarchically using parent and child Funding Program records.

That makes Funding Program the appropriate record for defining a disaster-assistance funding initiative and maintaining information associated with the program itself, including program-level documentation made available to prospective grantseekers. Salesforce specifically supports uploading files to a Funding Program so that eligible site users can view program documentation.

A Funding Request , by contrast, represents an applicant's request or application for money under a Funding Program. Salesforce's Grants Management data model clearly distinguishes the two: the grantmaker creates the Funding Program, while an external organization or individual submits a Funding Request against that program.

Therefore, D is appropriate only after an individual government agency applies for disaster funding. Business License Application belongs to licensing and permitting, not grantmaking. "Funding Program Request" isn't the standard Grants Management object for defining a program.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Grants Management data model; Funding Program; Funding Request; program documentation.

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

Cloning an Action Plan Template creates a separate template configuration; it doesn't automatically redirect existing inspection configuration to the cloned version. Therefore, if the "Business Re-Opening" inspection continues to generate work based on the previous template, the configuration that identifies which Action Plan Template applies to that inspection must be updated. This makes C the intended configuration correction.

Salesforce's current Public Sector inspection architecture maintains the same fundamental principle: an inspection visit must be explicitly associated with the intended published Action Plan Template . Salesforce documents Action Plan Templates as reusable definitions containing assessment tasks, signature tasks, and other activities. When creating the inspection workflow, the appropriate template must be associated with the Visit so that the corresponding Action Plan and assessment indicators are generated.

Merely cloning the template doesn't alter existing references. Option A is unnecessary because creating a new template doesn't inherently require cloning the Inspection Type. Option D is also irrelevant; record identity, rather than display-name similarity, governs the relationship.

The terminology and association workflow have evolved in newer Public Sector releases, but the configuration principle tested by this item remains: the inspection must reference the new template rather than the previous template record .

Study Guide Reference: Public Sector Solution Product Configuration – Inspection Types; Action Plan Templates; Inspection Visits; template associations and version management.

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

Salesforce's DocuSign integration provides exactly the three capabilities identified in C, D, and E . Salesforce Contracts uses DocuSign to support electronic-signature workflows without requiring the implementing agency to create the core signing infrastructure through custom code.

Official Salesforce documentation specifies that the integration can send a contract document for review and signatures , track the signed contract document and update the contract record status , and automatically invalidate a contract document that is pending signatures when a newer contract document supersedes it .

The distinction between A and C is important. Invalidating a superseded document is a native lifecycle capability of the integration; the agency doesn't need to build a separate Salesforce Approval Process merely to accomplish that action. Therefore, C is correct while A introduces unnecessary automation.

Option B is also incorrect. Updating document content during the review/signing operation isn't listed as one of the standard DocuSign contract-signature functions represented by this integration. Contract content should be finalized through the appropriate document-generation and review process before execution.

Together, C, D, and E cover the core end-to-end electronic-signature lifecycle: issue the document for signature, maintain its validity relative to newer versions, and synchronize completed-signature status back to Salesforce.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; DocuSign Integration; eSignature; contract-document lifecycle and status tracking.

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

Option A provides the complete low-code architecture required for a Public Sector employee digital-transformation program. Salesforce's Employee Experience for Public Sector enables government employees to use Public Sector capabilities for benefits, grants, inspections, licensing, permitting, recruitment, and other internal processes through purpose-built employee experiences.

OmniStudio is critical because Public Sector uses OmniScripts to replace static and paper-based forms with dynamic, guided digital forms. OmniScripts support conditional questions, validation, guided workflows, Data Mappers, and reusable application processes with little or no custom code. Salesforce specifically positions OmniStudio as the suite for building interactive Public Sector applications and workflows using Salesforce and external data.

Flows then automate surrounding business processes, while the Employee and Public Sector data models provide standardized records rather than creating unnecessary custom objects. Employee Community/Employee Experience provides the authenticated employee-facing channel.

Option B omits OmniStudio, which is the key technology for converting large numbers of forms into guided experiences. Option C unnecessarily introduces Apex, Visualforce, and custom objects. Option D uses Customer Community and an inappropriate person-data architecture rather than the employee-focused experience.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Employee Experience; OmniStudio; OmniScripts; Public Sector data model; employee digital experiences.

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

Intelligent Document Automation (IDA) directly addresses the conversion of paper-driven government processes into structured digital workflows. Salesforce describes IDA as a mechanism for simplifying and centralizing document management while reducing manual data entry. In Public Sector, it can extract and store data from paper or handwritten forms into digital Salesforce records such as Business License Applications and Individual Applications.

IDA supports PDF and image-based documents, creates Received Document records, allows relevant pages to be processed, uses OCR-based extraction through Intelligent Form Reader, and enables reviewers to compare extracted data against the original scanned document. The resulting information can then participate in downstream Salesforce workflows.

This matches both aspects of the requirement: digitizing files and automating the processing associated with those files. Business Rules Engine performs calculations and repeatable policy decisions but does not digitize paper. Generic workflows automate record-based processes but do not provide the document ingestion, OCR, document classification, or extracted-data mapping capabilities required. "Smart Forms" is not the appropriate Public Sector document-processing solution for the described legacy-paper migration.

IDA therefore supplies the specialized document layer needed to modernize a twenty-year-old paper-intensive environment.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Intelligent Document Automation; Intelligent Form Reader; Received Documents; OCR; digital application processing.

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

Salesforce explicitly states that the Person Account model uses the standard Account object to hold the details about a person . In Public Sector, Person Accounts represent individual constituents who apply for licenses, permits, programs, benefits, grants, and government services.

A Person Account combines selected Account and Contact behavior into a single person-oriented record. Salesforce's Public Sector data-model documentation explains that this record can contain personhood information such as birth date and tax identification information and can relate directly to Cases, Individual Applications, and Public Complaints.

Option B is incorrect because Person Accounts combine Account and Contact characteristics, not Opportunity and Contract fields. Option C is incorrect because the Person Account record type is fundamental to the implementation; Salesforce explicitly identifies Person Account as an Account record type.

Option D is particularly important from an implementation-governance perspective. Salesforce warns that after Person Accounts are enabled in an organization, they cannot be disabled . This is why enabling them requires deliberate architectural planning and testing before activation.

For Public Sector, business constituents should normally be represented by Business Accounts, while individual constituents can use Person Accounts. This separation supports Public Sector data relationships while maintaining a consistent CRM data model.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Person Accounts; Account data model; constituents; Person Account record type; implementation considerations.

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

CRM Analytics for Public Sector is the purpose-built analytics solution described by Salesforce for gaining intelligent operational insights from Public Sector data through preconfigured analytics applications and dashboards.

Salesforce specifically provides an Analytics for Licenses, Permits, and Inspections template. The application is designed to help licensing and permitting agencies evaluate departmental productivity and constituent satisfaction. Its prebuilt dashboards include Compliance Insights, Executive Summary, Department Summary, and Account Insights. These dashboards analyze Public Sector operational data without requiring the city to design a complete analytics model from scratch.

Standard Salesforce Reports and Dashboards can report on licensing records, but they don't provide the same purpose-built CRM Analytics data preparation and preconfigured analytical experience. Salesforce Einstein represents a broader AI capability rather than the specific analytics application requested.

Salesforce now also provides Tableau Next dashboards for Public Sector in supported editions, but the question specifically asks which listed product supplies the established prebuilt Public Sector analytics templates. Among the supplied answers, that remains CRM Analytics for Public Sector .

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Compliance Insights; Executive Summary; Department Summary.

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

An Aggregate Group is the Business Rules Engine construct designed to repeat prior Expression Set logic for multiple input-value sets and then consolidate the resulting values. This matches a licensing scenario where one application contains multiple permits and the system must calculate a fee for each permit and then produce the total.

Salesforce explains that an Aggregate Group runs the preceding steps once for each input set and then applies aggregation logic to the results. Inside the Aggregate Group, the Aggregate step must be the first element and can perform SUM, AVG, MAX, or MIN calculations. Aggregate steps cannot exist independently outside an Aggregate Group.

Accordingly, the consultant first places an Aggregate Group at the appropriate point in the Expression Set and then adds an Aggregate step configured with the SUM function. If the rule calculates each selected permit's fee independently, SUM consolidates those calculated fee values into the total application fee.

A custom Lightning Component is unnecessary because Business Rules Engine already provides aggregation declaratively. Permission sets may be required to execute or administer BRE, but they don't implement the fee-calculation logic requested in the question.

Therefore, B and D represent the functional configuration required to support multiple selected permits and aggregate their calculated fees.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Aggregate Groups; Aggregate step; SUM function; multi-permit fee calculations.

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

The Intelligent Form Reader implementation requires the consultant to enable Intelligent Form Reader, configure data extraction, and map the extracted form/document data to Salesforce objects and fields . Salesforce explicitly documents enabling Intelligent Form Reader from Setup so that its OCR capability can process uploaded documents using Amazon Textract.

The next stage is data-extraction configuration. The consultant defines the applicable form or document type and supplies the mapping information needed to identify values in the scanned document. Salesforce then maps the extracted document fields to the selected target Salesforce object and record-type fields.

For the scenario, the constituent's date of birth can therefore be extracted from a driver's license, passport, or similar document and mapped to the relevant field on the Application-related target object. Salesforce specifically documents birth-date verification against a scanned passport as an Intelligent Form Reader use case.

The terminology has evolved in current releases from "form type/object mapping" toward Document Types, Templates, and document-field-to-object mapping , but option D represents the equivalent configuration concept tested by this item.

DataRaptor/Data Mapper isn't the OCR engine and does not read scanned-document content. There is also no generic Document-object OCR checkbox that replaces Intelligent Form Reader configuration.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Form Reader; OCR; data extraction; form/document types; target object and field mapping.

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

Two Decision Matrices provide the cleanest and appropriate Business Rules Engine design because the scenario contains two independent lookup domains . The first matrix represents the federal income-limit values applicable to household size or related criteria. The second maps the calculated percentage of Area Median Income to the appropriate prioritization pool.

Salesforce defines Decision Matrices as tables that match supplied input values against rows and return corresponding output values. Expression Sets can invoke these matrices and combine the results with calculations, variables, and constants.

The Expression Set would therefore obtain or calculate the applicable household AMI percentage by referencing the federal-income-limit criteria and then pass that calculated percentage into the prioritization matrix. Separating these rule sets is preferable to placing unrelated policy dimensions into one monolithic matrix. It improves maintainability because federal limits can change independently of an agency's prioritization thresholds.

Option D unnecessarily creates a third matrix for household data. Household income and household size are transactional inputs , not reference-policy values that inherently require their own Decision Matrix. Option A omits the Federal Income Limit lookup, while B improperly combines two independently maintained rule sets.

This modular design also supports policy changes without rebuilding the Expression Set itself.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Decision Matrices; policy lookup tables; AMI and prioritization calculations.

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

An Integration Procedure is the appropriate OmniStudio component when a solution must retrieve, combine, transform, and calculate data from multiple sources without custom Apex. Integration Procedures execute server-side and can orchestrate multiple data-access and transformation operations before returning a consolidated response to a FlexCard, OmniScript, Lightning component, or another consumer.

Salesforce defines OmniStudio Integration Procedures as components that can read and write data between Salesforce and external systems , while Data Mappers handle Salesforce data retrieval, transformation, and persistence. Integration Procedures can invoke multiple Data Mappers, conditional actions, calculations, HTTP actions, and other services within one declarative process.

That orchestration capability is particularly important when the records being aggregated aren't connected through one simple Salesforce relationship. The Integration Procedure can independently query each required data set, calculate or transform the results, merge the outputs into a JSON response, and provide the resulting data to the presentation widget.

SOQL is a query language, not a standalone declarative OmniStudio orchestration component. Apex could implement the requirement but introduces unnecessary custom code. MuleSoft is appropriate for enterprise integration scenarios but is excessive when the required aggregation can be handled natively through OmniStudio.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; Data Mappers/DataRaptors; server-side orchestration; data aggregation and transformation.

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

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.

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

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.

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

User Stories and a Functional Requirements Specification (FRS) are core implementation artifacts because both translate stakeholder needs into requirements that can guide Salesforce solution design, configuration, development, and testing.

Salesforce defines a user story as a concise description of functionality that a business system should provide from a user's perspective. The commonly used structure is: As a [user], I want [capability] , so that [business value]. User stories become development work items and allow requirements to be prioritized, implemented, and validated incrementally.

Salesforce describes the Functional Requirements Specification as documentation of business requirements from the end-user or business perspective, specifying the expected functional outcomes. It becomes a more comprehensive reference for how required capabilities should operate and supports scope control, solution design, QA, and user acceptance testing.

A Marketing Plan addresses promotion, audience positioning, and communication strategy rather than technical implementation requirements. A Budget Plan is an important project-governance artifact but isn't one of the two requirements-definition documents being tested.

In a Public Sector project, these artifacts are particularly important because requirements commonly involve statutory rules, eligibility criteria, licensing processes, data governance, integrations, and auditable approval workflows that must be defined precisely before implementation.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – discovery; requirements gathering; user stories; functional requirements specifications; implementation documentation.

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

Salesforce provides a dedicated Licenses and Permits Experience Cloud site template specifically for Public Sector licensing and permitting use cases. It is therefore unnecessary to construct the entire constituent portal from a generic Experience Cloud template.

Salesforce documents that the template includes preconfigured pages covering major constituent workflows, including Assess Your License or Permit Needs, Apply for a License or Permit, Renew a License or Permit, Permits, Search for License or Permit Holder, File a Complaint, My Complaints, My Applications and Licenses, and View Inspection History .

Public Sector additionally provides dedicated Lightning components that can be added to these pages for activities such as submitting license and permit applications, renewing authorizations, filing complaints, and reviewing permit requirements.

The Customer Account Portal is a general-purpose external customer template and doesn't provide the Public Sector licensing-specific page structure and processes. Option B is factually incorrect because Salesforce explicitly supplies the Licenses and Permits template. "Public Sector Solutions Template" isn't the name of the appropriate Experience Cloud template.

For implementations where rapid deployment, standard functionality, and reduced custom maintenance are important, this purpose-built template should normally be preferred before considering custom portal development.

Study Guide Reference: Public Sector Solution Product Configuration – Experience Cloud; Licenses and Permits template; licensing and permitting constituent portal; Public Sector Lightning components.

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

The three foundational configuration records are Business Type, Regulatory Authorization Type, and Regulatory Authority . Salesforce's regulatory authorization model defines Regulatory Authority as the government agency or department responsible for issuing and enforcing licenses and permits. Regulatory Authorization Type represents the specific license or permit, while Business Type identifies the category of business and activities that require regulatory authorization.

After these components exist, Public Sector uses the Business Regulatory Authorization Type junction object to map a Business Type to the applicable Regulatory Authorization Type. This establishes which licenses or permits are required for a given business activity.

A Business Profile is used to capture information about the applicant's business or individual during application processing, but it is not one of the three foundational authorization-definition records asked for here. Inspection Type belongs to inspection configuration and therefore is not necessary simply to define the license authorization.

Salesforce's configuration sequence explicitly includes creation of Regulatory Authorities, Regulatory Authorization Types, and Business Types as core elements of regulatory authorization setup.

Study Guide Reference: Public Sector Solution Product Configuration – Regulatory Authorization Model; Regulatory Authority; Regulatory Authorization Type; Business Type; Business Regulatory Authorization Type.

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

For the managed-package OmniStudio architecture represented by this question, OmniStudio Tracking Service is specifically designed to capture user interactions and component-performance information so that consultants can identify inefficient steps in a business process.

Salesforce describes Tracking Service as an event-tracking service that records details of actions performed by users. A documented example is tracking how long users take to complete individual steps in an OmniScript specifically to identify process improvements . The service receives interaction events from OmniScripts, FlexCards, Integration Procedures, and other supported components and stores tracking details such as elapsed time, timestamps, event types, session information, and contextual data.

This makes it directly applicable after go-live: the consultant can determine where constituents or employees spend excessive time, abandon processes, encounter errors, or experience inefficient navigation.

Event Monitoring is a broader Salesforce security and activity-monitoring capability and does not provide the same OmniStudio process-level interaction analytics. Roll-up libraries and generic field tracking don't measure OmniScript process efficiency.

A release distinction is important: Salesforce's standard OmniStudio runtime doesn't implement the legacy Tracking Service , while OmniStudio for Managed Packages does. Salesforce currently provides OmniAnalytics and related analytics capabilities for modern OmniStudio environments. The question uses the managed-package-era feature terminology, for which A is correct.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – OmniStudio Tracking Service; OmniAnalytics; process optimization; user-interaction tracking.

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

The inspection checklist belongs to the actual onsite Visit , not directly to the Business License Application. Consequently, the Action Plan Template must target the Visit object. In the terminology used by this exam item, the inspection-oriented template type is Visit Execution , making B the correct selection.

The underlying Salesforce design is explicit. An inspection Action Plan Template groups assessment tasks and additional visit activities, such as signature capture, into a repeatable inspection process. Salesforce documents that the target object for an inspection Action Plan Template is Visit . Assessment Task Definitions provide the regulatory-compliance checklist, while Signature Tasks allow signatures to be collected during the visit.

A terminology update is important for current implementations: current Salesforce documentation uses Assessment Execution as the Action Plan Type for Public Sector inspection templates rather than the older Visit Execution terminology appearing in this question. The architectural answer remains unchanged—an inspection template is associated with the Visit .

Targeting Business License Application would incorrectly attach the execution checklist to the application rather than the physical inspection event.

Study Guide Reference: Public Sector Solution Product Configuration – Inspection Management; Action Plan Templates; Assessment Execution/Visit Execution; Visit target object; Assessment Tasks; Signature Tasks.

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