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

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.

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

Salesforce's official Grants Management installation prerequisites directly support B, C, and E . Grants Management requires the appropriate Grants Management licensing together with Customer Community Plus Login licenses for the external grantseeker experience. Salesforce also requires Lightning Experience and Chatter to be enabled.

Therefore, because the agency's employees currently operate in Salesforce Classic, they must move to Lightning Experience to use the supported Grants Management experience. Chatter must also be enabled because the package depends on Salesforce collaboration functionality. For the external grant portal, Customer Community Plus provides the supported external-user licensing required by the managed-package implementation.

The distinction between options B and D is significant. Although Customer Community is appropriate for many high-volume constituent portals, the Grants Management managed-package prerequisites specifically identify Customer Community Plus Login licensing. This is therefore a product-specific requirement, not merely a generic Experience Cloud licensing choice.

Web-to-Lead concerns conversion of public web submissions into Lead records and has no role in installing or enabling Grants Management.

Salesforce additionally lists Digital Experiences and My Domain among the overall prerequisites, although those choices are not provided in this question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Grants Management installation; Experience Cloud; Customer Community Plus; Chatter; Lightning Experience.

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

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

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

The required combination is Web-to-Case, Person Accounts, and the Emergency Response Management for Public Sector managed package . This question reflects the ERM deployment architecture in which the agency provides an external digital destination for constituents and organizations to submit emergency-related requests while Public Sector components manage those requests internally.

Person Accounts provide the appropriate Salesforce representation for individual constituents who are not operating as business accounts. Web-to-Case supplies a standard intake mechanism through which web-submitted constituent requests can become Salesforce cases. The managed ERM package supplies the purpose-built emergency-response functionality; the unmanaged-package alternative is therefore incorrect.

Current Salesforce documentation describes Emergency Program Management as an Agentforce Public Sector capability for exposing emergency program information, incident updates, permits, assistance programs, and constituent requests through an Experience Cloud site. Salesforce also identifies Emergency Program Management as a specific Public Sector implementation area in the current Agentforce Public Sector portfolio.

Email-to-Case processes inbound email into cases but does not satisfy the specified web-based constituent experience prerequisite.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Emergency Response Management; Person Accounts; constituent digital intake.

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

The Licenses and Permits Experience Cloud template should be used because Salesforce supplies it specifically for constituent licensing and permitting experiences. It includes preconfigured pages for applying for licenses or permits, renewing authorizations, viewing applications and licenses, reviewing inspection history, filing complaints, and identifying permit requirements.

Using this purpose-built template significantly reduces custom implementation and long-term maintenance compared with retrofitting a generic Help Center site. Salesforce also provides OmniStudio-driven application capabilities that can be placed directly into Experience Cloud, including dynamic application forms built with OmniScripts and supporting components.

Option C could technically be implemented, but it would require the agency to manually recreate capabilities that Salesforce already supplies through the dedicated template. That contradicts the requirement to minimize customization and maintenance.

OmniOut is intended for scenarios where OmniStudio experiences must run outside Salesforce-hosted environments. Since the requested constituent application experience is being implemented directly on Experience Cloud, OmniOut adds unnecessary architecture and deployment complexity. Therefore, neither A nor D represents the most maintainable design.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Licenses and Permits Experience Cloud Site; Experience Cloud templates; OmniScripts; FlexCards; reuse of preconfigured Public Sector components.

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

An unauthenticated Experience Cloud site backed by Salesforce Knowledge is the most efficient architecture for publishing frequently requested licensing and permitting information to the general public. Salesforce supports Knowledge articles in Experience Cloud and allows appropriately configured guest users to access publicly available articles without authenticating. This directly supports constituent self-service while reducing repetitive contact-center inquiries.

This approach also minimizes implementation and maintenance overhead because the agency can maintain its authoritative articles directly in Salesforce Knowledge and expose them through the Experience Cloud presentation layer. Salesforce specifically notes that an Experience Cloud site can function as a public knowledge base for unauthenticated users without requiring community licenses simply for public article access.

Option A introduces an unnecessary CMS integration and outbound API synchronization layer. Option B similarly adds unnecessary integration complexity through Lightning Out. Option D forces constituents to authenticate merely to read general application-process information, adding friction and potentially requiring additional license considerations.

The architectural best practice is therefore to keep public informational content openly accessible while reserving authentication for personalized records, applications, and protected constituent data.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud, Salesforce Knowledge, constituent self-service, guest-user access, and public information delivery.

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

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.

A DataRaptor , now called an OmniStudio Data Mapper , is specifically designed to read, transform, and write data to Salesforce objects. For the use case in this question, the external portal already exists; the primary requirement is therefore to take submitted application data and map it into the corresponding Public Sector Salesforce objects.

Salesforce states that a Data Mapper Load accepts JSON, XML, or supported custom input formats and writes the resulting data to Salesforce objects using configured object and field mappings. More importantly for this scenario, Salesforce exposes a Data Mapper REST API . An external application can POST a JSON payload to a Data Mapper Load, and the Data Mapper updates or creates Salesforce records according to its mappings.

That makes DataRaptor/Data Mapper an appropriate declarative bridge between the existing external portal and Public Sector's Grant application records.

An Integration Procedure is preferred when orchestration involves multiple data sources, several operations, conditional processing, REST integrations, error handling, or multiple Data Mappers. Salesforce recommends a single Data Mapper where the requirement is fundamentally a Salesforce-object write operation that can be handled through direct mappings.

FlexCards provide user-interface presentation. OmniOut runs OmniStudio UI components on third-party sites, but the question states that the agency will retain its existing portal and specifically needs to integrate submitted data .

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio DataRaptors/Data Mappers; Data Mapper Load; REST API; external application integration.

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

Public Sector Inspection Management provides the native framework for investigating regulatory complaints through Visits, inspections, and Action Plans . Salesforce explains that agencies perform inspections both for license and permit applications and when members of the public report compliance concerns. Visit records identify the location, account, inspector, purpose, and regulatory context of an inspection.

The Visit can be created from a license or permit application and linked through its context to the applicable application, thereby preserving the connection between the investigation and the underlying construction authorization. Salesforce's current documentation explicitly supports creating Visits from application records and associating them with inspection types.

Action Plans provide the repeatable task framework used by inspectors. They contain assessment tasks, signatures, checklists, and other required inspection work so that investigators follow a standardized process. Salesforce also documents Action Plan usage for Public Complaint investigations.

Business Rules Engine is unnecessary merely to determine whether a complaint is valid, and directly linking generic Case records is not the core LPI complaint-and-inspection architecture.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Public Complaints; Visits; Permit Applications; Action Plans; regulatory compliance investigations.

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

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.

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

Customer Community is the correct license because this is an extremely high-volume business-to-consumer Experience Cloud scenario. Salesforce explicitly categorizes Customer Community users as high-volume external users and describes the license as appropriate for large populations requiring limited access to Salesforce CRM functionality.

The decisive requirement is scalability beyond 100 million users . Salesforce's Experience Cloud licensing guidance states that Customer Community or External Apps licenses can support 100+ million users , whereas role-based licenses such as Customer Community Plus, Partner Community, and Channel Account are designed for more sophisticated sharing requirements and generally operate at lower standard user scales.

Customer Community users do not participate in the normal external role hierarchy. Eliminating those role calculations is precisely what allows the high-volume user architecture to scale efficiently. That design is appropriate where constituents primarily access their own data and execute defined portal transactions.

Customer Community Plus should be selected when external users require advanced sharing, reports, dashboards, and role-based access—not simply because they use authenticated portal functionality. Partner Community and Channel Account are primarily B2B/partner-oriented models and are inappropriate for the mass constituent population described.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud architecture, external-user licensing, high-volume user design, scalability, and sharing models.

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

The decisive requirement is pixel-perfect control over the digital experience . Salesforce specifically positions the Build Your Own (LWR) Experience Cloud template for organizations that need high-performance, highly customized experiences using Lightning Web Components. Salesforce states that the template enables developers to build pixel-perfect pages and create Lightning Web Components and themes that precisely match an organization's brand.

Lightning Web Runtime is optimized for performance because Lightning Web Components execute using browser-native standards, resulting in lightweight components and efficient rendering. LWR also includes performance capabilities such as HTTP caching and publish-time optimizations.

The Licenses and Permits template is excellent when the priority is rapid deployment and minimal customization. It provides preconfigured application, renewal, permit, complaint, inspection-history, and account-management pages. However, that was not the dominant requirement in this scenario. The sponsor has explicitly elevated pixel-perfect branded UX above minimizing implementation effort.

Help Center is designed primarily for public knowledge and support self-service. BYO Aura supports customization but does not provide the performance-oriented modern LWR architecture that Salesforce recommends for sophisticated custom digital experiences.

Therefore, BYO LWR with custom Lightning Web Components best satisfies the specified UX requirement.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud architecture; Build Your Own LWR; Lightning Web Components; branding and digital experience design.

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

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.

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

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.

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

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.

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

An OmniScript plus Decision Matrix provides the correct declarative architecture. OmniScript captures the constituent's answers through a guided, dynamic digital form, while the Decision Matrix stores the changeable business criteria used to determine which license type corresponds to those inputs.

Salesforce describes a Decision Matrix as a table containing input and output values. When invoked, the matrix identifies the row matching the supplied inputs and returns the corresponding output. Because thresholds and policy values are stored declaratively in matrix rows, administrators can update city/county conditions, revenue bands, building-size thresholds, and resulting license recommendations without rewriting Apex.

Salesforce also provides direct integration between OmniScripts and Decision Matrices. An OmniScript can pass selected input values to the matrix and capture the returned result in its JSON structure. This is analogous to Salesforce's documented Public Sector pattern in which constituent inputs from an OmniScript are evaluated against Business Rules Engine criteria to produce eligibility or fee results.

OmniChannel is a work-routing capability, not a public questionnaire framework. Einstein AI isn't appropriate for deterministic regulatory rules. LWC plus Apex could work but creates unnecessary code and maintenance.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScripts; Business Rules Engine; Decision Matrices; declarative eligibility and recommendation logic.

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

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.

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

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

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

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

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