Salesforce AP-222 Dumps

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.

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

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.

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.

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

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.

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

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.

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

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.

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.

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

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.

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

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.

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

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.

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

Partner Central is specifically designed for partner relationship management and channel-sales workflows. Salesforce documents Partner Central as a responsive Experience Cloud template intended to help organizations recruit, build, and grow partner networks while supporting channel sales and marketing activities. Its standard capabilities include lead distribution, deal registration, partner recruitment and onboarding, marketing campaigns, enablement, pipeline management, and related reporting.

Those capabilities correspond directly to the scenario. The external associates function as channel partners, and the agency needs a collaborative portal for onboarding those partners and managing sales-style workflows around licensing activities.

Customer Account Portal is designed primarily for customers managing their own account information and accessing customer-oriented services. Help Center is focused on support and self-service knowledge experiences rather than partner sales processes. Aloha is a legacy template and is no longer the preferred architecture for a new implementation.

Salesforce also requires appropriate partner licensing for Partner Central functionality and explicitly associates the template with Partner Community and related partner-oriented licenses.

Study Guide Reference: Public Sector Solution Product Configuration – Experience Cloud templates, Partner Central, partner onboarding, lead distribution, deal registration, and channel collaboration.

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

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.

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

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.

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

Public Sector uses business accounts to represent businesses and Person Accounts to represent individual constituents . Salesforce explicitly states that Person Accounts should represent people applying for licenses, permits, programs, benefits, grants, and government services, while business accounts represent organizations or businesses.

Because the agency has explicitly selected a phased implementation—business constituents first and private constituents later—the appropriate implementation is to establish the Business Account and Contact model for the first release and introduce Person Accounts when the individual-constituent phase is implemented.

Salesforce supports enabling Person Accounts in an existing Public Sector organization. However, the decision requires appropriate planning because Salesforce warns that Person Accounts can't be turned off after they're enabled . Administrators should therefore evaluate and test the implications before activation.

Household Accounts aren't the standard constituent model for Public Sector license and permit applications. Person Accounts are specifically integrated with Individual Applications, Cases, public complaints, and Public Sector constituent experiences. Therefore, C and D use the wrong individual data model. Option A unnecessarily implements the second-phase architecture immediately despite the government's explicit phased rollout.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Public Sector data model; Business Accounts; Contacts; Person Accounts; phased implementation strategy.

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

Volunteer Management provides capabilities for coordinating volunteer demand, registrations, assignments, projects, shifts, and volunteer activity. Salesforce's official Work.com documentation describes Volunteer Management as supporting volunteer projects at scale and explicitly states that volunteers can sign up for volunteer projects through a community experience and update the time spent on volunteer activities . This directly validates option C.

The package also maintains volunteer capacity and registration information associated with volunteer work. Volunteer-management records track shift requirements and registered resources so that changes in a shift—including cancellation—can be reflected in the volunteer counts. This supports option A's requirement to keep registered-volunteer and volunteer-demand figures synchronized.

Salesforce's volunteer data architecture similarly includes volunteer shifts, volunteer hours, volunteer counts, and "Volunteers Still Needed" information, demonstrating that capacity and participation tracking are integral functions of volunteer management.

Automatic reimbursement claiming is not a standard Volunteer Management capability described for this package. Likewise, a volunteer chatbot is not one of the core Volunteer Management features represented by the question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Volunteer Management; volunteer projects, shifts, registrations, capacity, and volunteer-hour reporting.

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

The lowest-customization Public Sector architecture is to reuse the prebuilt Emergency Service Request flow and deploy the constituent experience through the preconfigured Emergency Response Management digital-experience template .

Emergency Response Management is designed to accelerate deployment of emergency programs and constituent-service workflows. Its digital experience provides the public-facing channel through which citizens and businesses can obtain emergency information and submit requests for assistance or services. Using the purpose-built template prevents the agency from recreating emergency-specific navigation, pages, and constituent processes from a generic Experience Cloud template.

The Emergency Service Request flow provides the intake layer. It captures the basic information needed for an emergency request and creates the corresponding Salesforce records through the configured Emergency Response architecture. This provides a declarative alternative to developing a custom request workflow.

A Help Center template is primarily designed for knowledge and customer-support self-service and would require additional configuration to reproduce Emergency Response functionality. Creating a custom Case record type and relying on a generic Contact Support Form similarly duplicates functionality already supplied by the solution and introduces unnecessary technical debt.

The Set 3 source shows C and D as the selected combination for this item.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Emergency Response Management; Emergency Service Requests; Experience Cloud; preconfigured emergency-response digital experiences.

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.

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

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

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

Administrators responsible for creating and managing the Analytics for Licenses, Permits, and Inspections application require both platform-level CRM Analytics administrator access and Public Sector analytics-template administrator access.

Salesforce's current official documentation specifies the combination as CRM Analytics Plus Admin AND TCRM for Public Sector Admin for users who create, share, and view the Analytics for Licenses, Permits, and Inspections application. The question's option D, "CRMA for Public Sector Admin," represents the corresponding Public Sector analytics administrator permission-set naming in the version of the product on which this item is based. Therefore A and D are the intended pair.

CRM Analytics Plus Admin grants the broad CRM Analytics administrative capabilities required to create and manage templated applications, datasets, dashboards, and analytics assets. Salesforce confirms that the Plus Admin permission set provides full platform administration as well as Einstein Discovery capabilities.

The second Public Sector-specific administrator permission set provides access to the LPI template and its industry assets. Generic CRM Analytics administration alone is insufficient because templated industry applications impose additional product-specific permissions.

Study Guide Reference: Public Sector Solution Product Configuration – CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; CRM Analytics Plus Admin; Public Sector analytics permissions.

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

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

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

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

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

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

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

The secure Experience Cloud design follows a restrict-first, selectively-share model. Salesforce recommends setting external organization-wide defaults to Private wherever possible , ensuring authenticated external users receive no automatic access to records they do not own or that have not explicitly been shared with them. External OWD therefore establishes the least-privilege baseline required by the scenario.

After establishing that restrictive baseline, Sharing Sets provide authenticated Experience Cloud users access to records associated with their own Account or Contact. Salesforce states that Sharing Sets use access mappings between the external user's Account/Contact and the target record. For example, a user can receive access to Cases associated with the Account identified through their Contact. Sharing Sets support Accounts, Cases, Business License Applications, custom objects, and numerous Public Sector objects.

This mechanism is particularly important for high-volume Customer Community users because conventional role-based sharing isn't the appropriate scalability model. Salesforce specifically recommends Sharing Sets for Customer Community users when access should follow Account or Contact relationships.

Option C is invalid because Hidden isn't an external OWD access level. Option A is less appropriate than Sharing Sets for the account/contact-relative community access model described.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud Security; External OWD; Private access; Sharing Sets; least-privilege external record access.

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.

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

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

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

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

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

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

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

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.