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

The requirement is for a repeatable document requirement , not one-off checklist records created manually on each application. The correct architecture therefore uses an Action Plan Template , document checklist items contained in that template, and automation to associate the template with every applicable Business License Application.

Salesforce documents that Document Checklist Items can be added to Action Plan Templates to standardize document-processing workflows. When an Action Plan is created from the template, the defined checklist items are automatically carried into that plan. Salesforce further requires the completed template to be published before operational use.

Option B establishes the reusable application-oriented template. Option E defines the three required document types within that template and publishes it. Option D ensures every newly created Business License Application receives the standardized Action Plan automatically, removing reliance on staff remembering to add the checklist manually.

Option C would create the checklist directly against an individual Business License Application. Salesforce supports that capability, but it doesn't satisfy the requirement to impose the same three-document package consistently on every application. Option A uses Tasks rather than Document Checklist Items, so it doesn't provide the dedicated applicant document-upload and tracking semantics.

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

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

Deploying DataPack Lightning Web Component files is the step that requires the Salesforce development toolchain represented in the question. Salesforce states that OmniStudio Lightning Web Components are managed and deployed by using Visual Studio Code with Salesforce DX and the Salesforce CLI . The same toolchain can deploy components from a development or sandbox organization into another target organization, including production.

Salesforce's current deployment guidance has evolved toward the Salesforce CLI for standard-runtime OmniStudio implementations, but Lightning Web Component deployment remains a metadata/development operation rather than a simple administrative activation step. Salesforce CLI can deploy OmniScripts, FlexCards, Integration Procedures, Data Mappers, generated OmniStudio LWCs, permission sets, and related metadata.

Activating imported OmniScripts or Integration Procedures is handled through OmniStudio configuration and doesn't inherently require VS Code. Downloading sample DataPacks from a process library is likewise not equivalent to deploying their generated LWC source files. OmniStudio package installation is an administrative package-installation procedure; it doesn't inherently require the consultant to author or deploy source through Salesforce DX.

Therefore, B identifies the point where development/deployment tooling is specifically required.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio installation; DataPack deployment; Lightning Web Components; VS Code; Salesforce DX/Salesforce CLI.

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

A published Action Plan Template is intentionally immutable . Salesforce explicitly states that after an Action Plan Template is published, it cannot be edited or deleted; depending on the implementation, it can be deactivated or made obsolete, and a replacement template must be created when process changes are required.

This behavior preserves process integrity. Existing Action Plans can be traced back to the exact template definition from which they were created, which is important for standardized licensing, inspection, compliance, and due-diligence workflows. Allowing administrators to alter a published template could change the apparent definition of a process after users had already executed tasks generated from that template.

Salesforce's document-automation guidance states the remediation directly: because a published template can't be changed, create a new template and remove or retire the old one. In practice, an administrator can clone the existing template, modify the draft copy with the updated assessment tasks, document requirements, signatures, or inspection steps, then publish the replacement.

The absence of Edit is therefore not a page-layout problem or missing System Administrator permission. Salesforce Support isn't required to modify the existing record because the immutability is an intentional product lifecycle rule.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plan Templates; Draft and Published lifecycle; template versioning; inspection-process governance.

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

The Public Sector Case Analytics App is specifically designed to analyze public-sector service cases and provides prebuilt dashboards and metrics for measuring organizational effectiveness, caseworker performance, service trends, and operational outcomes. This makes it preferable to creating a custom Salesforce reporting implementation.

More importantly, Salesforce documents exactly how the template handles case duration when an organization does not already maintain its own duration field. During Public Sector Case Analytics configuration, administrators can identify an existing duration field if one exists. If no case-duration field is tracked, CRM Analytics uses its own formula , calculating duration from the case opened and closed dates. For cases that remain open, the calculation uses the current date.

Consequently, Bobahaven does not need to introduce a custom duration field merely to obtain trend reporting. Options A and B add unnecessary data-model customization and would primarily benefit future records unless additional historical transformation were implemented. Option C similarly creates a custom reporting solution despite the presence of a purpose-built analytics template.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; CRM Analytics for Public Sector; Public Sector Case Analytics; case-duration metrics and prebuilt analytics dashboards.

Agentforce Public Sector already provides the Regulatory Code Assessment Indicator junction object to relate regulatory codes to Assessment Indicator Definitions. Consequently, a custom junction object or custom master-detail relationship is unnecessary.

Salesforce describes Assessment Indicator Definitions as the conditions inspectors evaluate when determining whether a business or site complies with regulatory requirements. After defining an assessment indicator, administrators relate it to its applicable regulatory code through the Regulatory Code Assessment Indicator related list.

Salesforce's documentation on Public Sector junction objects further confirms that Regulatory Code Assessment Indicator relates Regulatory Code and Assessment Indicator Definition , mapping the compliance standard to the measure used during an inspection. This is inherently a many-to-many requirement: one regulatory code may have multiple assessment indicators, and an assessment indicator can be associated where applicable within the regulatory framework.

Option A unnecessarily creates custom architecture for functionality already supplied by the Public Sector data model. Option B uses an incorrect object name. Option C imposes an inappropriate direct master-detail relationship rather than using the standard junction model.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Regulatory Compliance data model; Assessment Indicator Definition; Regulatory Code Assessment Indicator; inspection configuration.

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

Salesforce's Grants Management documentation provides a specific procedure for manual grantseeker registration . The administrator updates the appropriate Contact page layout and adds the Enable Customer User action. The agency can then open an existing Contact and manually create the corresponding Experience Cloud user rather than exposing self-registration.

Salesforce's documented sequence is to navigate to Object Manager, open Contact, edit the page layout assigned to the administrators managing grantseekers, and add Enable Customer User and, where required, Log in to Experience as User to the Lightning actions. An administrator then opens the Contact, selects Enable Customer User, specifies the email and external-user configuration, and assigns the required community license and grantseeker profile.

There is no separate "Enable manual registration" switch that replaces this configuration. Manual registration is achieved through administrator-controlled customer-user creation. Enabling self-registration would accomplish precisely the opposite of the stated requirement by allowing grantseekers to create their own portal identities.

"Register User" is also not the Salesforce action used to convert a Contact into an Experience Cloud customer user. Salesforce identifies Enable Customer User as the appropriate action on Contact records.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; grantseeker portal; manual registration; Contact page layouts; Enable Customer User; Experience Cloud users.

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

DocuSign is the eSignature integration represented by the Public Sector/Industries contract-management toolkit. Salesforce's Contract Lifecycle Management documentation explicitly states that Salesforce Contracts uses DocuSign to support electronic signatures .

The integration provides a substantial prebuilt eSignature workflow. Salesforce supports defining DocuSign tags in document templates, sending documents for review and signature, tracking completed documents, updating the associated contract status, and automatically invalidating a pending signature document when a newer contract version supersedes it.

For the Government/Public Sector architecture, Salesforce's Vlocity Contract Lifecycle Management documentation also explicitly includes the ability to send documents for signing through the DocuSign eSignature setup.

After signatures are collected, DocuSign returns the signed document and the integration can attach it to the applicable contract version while updating lifecycle status.

Adobe Sign, Conga, and eSignLive can potentially participate in Salesforce implementations through separately designed products or integrations, but none is the pre-integrated eSignature provider represented by the Public Sector solution architecture tested here.

"Without much coding/configuration" should not be interpreted as zero setup: an active DocuSign account, authentication, envelope configuration, recipient configuration, and applicable Salesforce setup are still required. The point is that the core integration is supplied rather than needing to be custom-built.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Contract Lifecycle Management; DocuSign; eSignature; document generation and contract execution.

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

The page component being present does not itself grant access to Decision Explainer functionality. The administrator must also ensure that the caseworker has the required Decision Explainer access. Therefore, A is the intended answer.

Current Salesforce documentation refers to Decision Explainer Service Access when describing the permission required by internal users to work with Decision Explainer entities and review decision information. Salesforce also documents a Decision Explainer Permission Set License as the entitlement that provides access to Decision Explainer features. The terminology in the question is therefore slightly simplified, but its technical intent is unambiguous: verify that the caseworker is authorized for Decision Explainer.

OmniStudio Admin provides configuration capabilities for OmniStudio components and is excessive for an ordinary caseworker. OmniStudio User enables runtime access to OmniStudio processes but does not specifically authorize Decision Explainer logs. Rules Engine Runtime permits execution of business rules; it does not by itself grant access to the Decision Explainer interface or its underlying records.

Study Guide Reference: Public Sector Solution Product Configuration – Decision Explainer permissions, Decision Explainer Service Access, Business Rules Engine integration, and decision-log visibility.

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

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.

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

VS Code and Salesforce DX provide the supported development and deployment tooling for OmniStudio Lightning Web Components associated with DataPacks. Salesforce explicitly states that administrators and developers use Visual Studio Code with Salesforce DX and the Salesforce CLI to manage, develop, and deploy OmniStudio Lightning Web Components between development, sandbox, and production organizations.

This distinction matters because an OmniStudio DataPack can include configuration metadata as well as generated or supporting Lightning Web Component artifacts. When LWC deployment is required, a Salesforce DX project provides the metadata structure, authentication, source management, and deployment commands needed to transfer the components reliably between environments.

VS Code by itself is only the development environment; it does not constitute the complete Salesforce deployment mechanism. Salesforce DX provides the Salesforce-specific project model and deployment capabilities, making option B incomplete. Standard Change Sets aren't the recommended deployment mechanism for these OmniStudio LWC assets, while the ANT Migration Tool represents an older Metadata API deployment approach and isn't the prescribed toolchain for this requirement.

Therefore, the complete supported combination identified by Salesforce is Visual Studio Code together with Salesforce DX.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio deployment, DataPacks, Lightning Web Components, VS Code, Salesforce DX/SF CLI.

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

The Work.com employee-service architecture represented by this question consists of Employee Workspace, Employee Concierge, and HR Service Center .

Employee Workspace provides the employee-facing digital hub. Salesforce describes it as a central location where employees can access resources, collaborate, and obtain the tools required to work effectively.

Employee Concierge extends Employee Workspace with a searchable knowledge base and employee ticketing capability. Salesforce specifically states that Employee Concierge requires Employee Workspace to be installed and configured before the Concierge package itself is installed.

HR Service Center extends the employee-service architecture further, adding HR ticket management and employee onboarding processes. Salesforce documents that HR Service Center can only be installed after both Employee Workspace and Employee Concierge are configured.

That dependency chain directly establishes A, E, and C as related Work.com managed-package features.

Workplace Strategy Planner and Workplace Command Center belong to workplace/facilities-oriented capabilities and are not the three employee-service packages identified by this Employee Experience implementation path.

Current Salesforce strategy has evolved: HR Service is now positioned as a redesign of Work.com, and Salesforce recommends migration for organizations using legacy Work.com features. The item, however, tests the Work.com-based Employee Experience architecture represented in its source curriculum.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Employee Experience for Public Sector; Employee Workspace; Employee Concierge; HR Service Center.

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

Volunteer Management for Community is the permission-set license intended for external community users who participate in the Volunteer Management experience. The constituent in this scenario isn't an internal emergency-management administrator; the person is an external volunteer who must access a digital experience and sign up for volunteer projects.

Public Sector's user-access architecture separates feature entitlement from the base Experience Cloud user license. Permission-set licenses extend the capabilities of the underlying Salesforce user license and must correspond to the Public Sector product functionality the user needs. Salesforce's Public Sector permissions documentation confirms this general architecture: users require the appropriate Public Sector permission sets and associated permission-set licenses for the features they consume.

For this specific legacy Volunteer Management implementation, the relevant external entitlement is Volunteer Management for Community . This enables the community-side functionality necessary for volunteers to interact with volunteer projects rather than granting internal emergency-response administration.

Option A relates to broader Community Response capabilities rather than the specific volunteer-user entitlement. Option B is generic Public Sector community access and doesn't, by itself, grant Volunteer Management functionality. Option D is aligned with internal Emergency Response functionality rather than the community volunteer persona.

Study Guide Reference: Public Sector Solution Product Configuration – Volunteer Management; Community Response; Experience Cloud user access; Permission Set Licenses.

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

The appropriate relationship is PersonAccount → Individual ← Employee . Salesforce's Employee data model uses the Individual object as the common privacy and identity relationship point connecting employee information to other person-centric representations.

Salesforce documentation states that Employee records are related to Individual records and that an Individual connects employee data with privacy and consent information. The Work.com data-model documentation further explains that when another Salesforce solution represents a person through a Person Account, the Person Account can be linked to the Employee through the Individual record—specifically, PersonAccount > Individual < Employee .

This arrangement is particularly appropriate when Public Sector represents an individual constituent as a Person Account while the Employee data model separately maintains an Employee record. The Individual object provides the linking layer rather than requiring the Person Account to connect directly to User or Employee.

Option B is a valid pattern for solutions that represent people through Contacts, but it does not satisfy the scenario's explicit Person Account requirement. Option D incorrectly routes the relationship through User, while option A does not even use the standard Employee object.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Public Sector person data model; Employee data model; Person Accounts; Individual; Employee relationships.

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

An approval process is the correct architecture because the requirement combines conditional approval routing with an auditable approval history. Salesforce approval processes define the criteria under which a record enters approval, specify the approval steps, identify the appropriate approvers, and preserve the state of the approval request.

The consultant can use the application's age or duration as the entry or step criterion and route qualifying records to the appropriate manager. Salesforce's approval framework tracks states such as Submitted, Pending, Approved, Rejected, Reassigned, and Recalled. The Approval History related list provides users with visibility into the record's progress and creates the audit trail required by the scenario.

A Flow that merely changes ownership doesn't constitute manager approval and doesn't inherently provide the same approval-process audit model. Chatter is a collaboration mechanism rather than a controlled regulatory approval system. An "approval escalation rule" isn't the correct Salesforce automation construct for this requirement.

Salesforce now recommends Flow Approval Processes as the modern successor for many new implementations, providing dynamic routing and detailed compliance logging; however, among the supplied answer choices, C precisely describes the required approval-process pattern.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – application approvals; approval criteria; manager routing; Approval History; regulatory auditability.

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.

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

Action Plans are the Public Sector capability designed to organize and automate repeatable sets of tasks associated with inspection visits. Salesforce allows administrators to create Action Plan Templates for specific inspection types and populate those templates with the assessment tasks inspectors must perform. A published template can subsequently be associated with a particular Visit record to generate the appropriate inspection work.

This model provides consistency across teams because inspection requirements are defined centrally rather than reconstructed manually for every visit. Tasks can be sequenced, marked as required, assigned, and surfaced through the inspection process, providing shared visibility into work that remains outstanding and work that has been completed. This is exactly the mechanism needed for coordinated inspection execution.

OmniStudio is primarily used for guided digital experiences and orchestration. Business Rules Engine evaluates business logic, calculations, and decision criteria. DataRaptors—now commonly represented within OmniStudio's data-mapping capabilities—retrieve or transform data. None of those alternatives is the standard feature for defining a repeatable collaborative task plan for an onsite inspection.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Inspection Management; Visits; Action Plans; Action Plan Templates; Assessment Task Definitions.

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

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.

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

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

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

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

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

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

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

Salesforce requires users who configure or use Action Plans to have the appropriate Action Plans permission set . Salesforce's Public Sector Action Plans documentation explicitly identifies the required user permission as the Action Plans permission set and directs administrators to assign it through the user's Permission Set Assignments.

The scenario isolates the problem to one newly onboarded inspector while every existing inspector can access the same feature. That strongly indicates a user-specific permission assignment rather than an organization-wide configuration problem. If Person Accounts weren't enabled and were genuinely required, the impact would affect the implementation generally rather than only one inspector.

Likewise, "Enable Notes" isn't the feature permission controlling Action Plans. Action Plans have dedicated access requirements covering objects such as Action Plan, Action Plan Template, Document Checklist Item, and Recurrence Schedule, together with the Action Plans feature permission where appropriate.

A completely disabled Salesforce user would be unable to log in to Salesforce at all, not merely unable to access Action Plans. The wording indicates the inspector is successfully using Salesforce but lacks access to this particular capability.

Therefore, checking and assigning the Action Plans permission set is the precise troubleshooting action.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; user access; Action Plans Permission Set; inspection-user configuration.

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

Decision Matrices are the Business Rules Engine component used to map combinations of application inputs to defined outputs such as application fees. Salesforce describes a Decision Matrix as a lookup table containing input values and corresponding output values. When an Expression Set invokes the matrix, Business Rules Engine finds the row matching the supplied inputs and returns the output associated with that row.

Salesforce specifically documents Decision Matrices for Public Sector application-fee calculation . For example, a business licensing matrix can contain authorization category and authorization type as inputs and a base application fee as the output. Different application characteristics can therefore automatically resolve to different required fees without custom code.

This architecture is preferable to hard-coding fee mappings because administrators can update the Decision Matrix as legislation, agency policy, permit categories, or fee schedules change. Expression Sets can subsequently call the matrix and perform additional calculations when needed.

"Data matrices" isn't the Business Rules Engine component name used for this function. Workflow Field Updates and Process Builder are legacy Salesforce automation capabilities; neither provides the structured multidimensional policy lookup behavior required for configurable fee schedules.

Salesforce's current BRE portfolio also includes Decision Tables , which support advanced rule logic, but for the specific matrix-based fee-mapping architecture represented by this exam item, Decision Matrix is the required answer.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Decision Matrices; Expression Sets; automated application-fee calculations.

Salesforce directly documents Action Plans on Accounts as the mechanism for standardizing grantmaking due-diligence processes. An Action Plan Template acts as a reusable blueprint that defines the activities reviewers must complete consistently for each grantseeking organization.

Salesforce's Grants Management documentation explicitly states that organizations can use Action Plans on Accounts to define due diligence steps, related tasks, and documents to collect . Tasks can represent actions such as requesting tax documentation, verifying organizational eligibility, or completing financial reviews. Document Checklist Items identify supporting documents that must be obtained and reviewed.

This architecture directly addresses the problem in the scenario: reviewers currently follow different processes. A published Action Plan Template converts an informal procedure into a repeatable Salesforce-controlled workflow, improving consistency, traceability, accountability, and reviewer productivity.

A Screen Flow or OmniScript could technically guide a user through steps, but both would duplicate functionality already supplied by Action Plans. Merely supplying procedural documentation also provides no technical enforcement, assignment, due-date management, or document checklist tracking.

Therefore, Action Plans represent the product-native and lowest-customization implementation.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Due Diligence; Action Plans; Action Plan Templates; Tasks; Document Checklist Items.

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

The three controls address separate security layers: authentication, automated abuse protection, and record-level access .

Setting grant application pages to Requires Login restricts application workflows to authenticated Experience Cloud users. Salesforce documents the Page Access property for Experience Cloud pages and supports setting pages containing OmniScripts to Requires Login when workflows should only be available to authenticated users.

CAPTCHA or reCAPTCHA provides bot mitigation. Salesforce explicitly uses reCAPTCHA with Experience Cloud application-style forms to confirm that applications are submitted by humans rather than automated bots and recommends it for preventing misuse and spam.

Finally, external organization-wide defaults should be Private for sensitive grant application data. Salesforce's external-user security guidance recommends keeping external OWD settings Private wherever possible so authenticated external users don't automatically gain access to records belonging to other constituents. Additional sharing mechanisms can then selectively expose only the records each user is authorized to access.

A public application-reference search would create unnecessary information-disclosure risk. "Salesforce Spam Check" isn't the appropriate Experience Cloud control represented by this architecture.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud security; authentication; OmniScripts; CAPTCHA/reCAPTCHA; external OWD; privacy and record sharing.

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