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

The native Public Sector design combines an OmniScript application form with Business Rules Engine . Salesforce explicitly documents this architecture for automatically calculating processing fees associated with business license applications. Business Rules Engine uses Decision Matrices and Expression Sets to determine fee amounts from multiple input criteria, while the OmniScript captures those constituent inputs.

For example, a Decision Matrix can contain base-fee values indexed by authorization type, industry category, location, revenue band, or another applicable parameter. An Expression Set invokes one or more matrices, performs any additional arithmetic, and returns a calculated currency amount. Salesforce documents that Expression Sets and Decision Matrices accept JSON input from and return JSON output to OmniScripts.

The integration is direct: Salesforce explains that an Expression Set Action can be added to the OmniScript so that, when the applicant supplies the required information, the Business Rules Engine processes those values and returns the appropriate license fee.

Triggered Flow could calculate values, but it would duplicate a purpose-built policy calculation engine. Integration Procedures are appropriate for data orchestration and external integrations, not for replacing BRE as the authoritative fee-policy engine. A generic Flow application also bypasses the Public Sector OmniScript application architecture.

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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.

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

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.

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

Person Accounts must be enabled when the Public Sector implementation needs to represent individual constituents as applicants through the person-oriented Public Sector data model. The Individual Application object is designed to capture an individual's application for a government program, benefit, grant, license, permit, or similar service. The applicant therefore needs an appropriate person record with which the Individual Application can be associated.

Public Sector uses Person Accounts to represent constituents acting as individuals rather than organizations. A Person Account combines Account and Contact characteristics into a single person-centric record and integrates with Public Sector objects such as Individual Application, Case, and Public Complaint. This makes it the appropriate foundation for a grants program targeted at individual scholars.

Salesforce Flow is an automation technology and may participate in the implementation, but enabling Flow is not the prerequisite that establishes the individual-applicant data model. A custom Application object is unnecessary because Public Sector already provides Individual Application. Product Schedule is associated with product and revenue scheduling and has no functional relationship to grant applicants.

An important implementation consideration is that Person Accounts cannot simply be disabled after they are enabled , so agencies should validate their constituent data architecture before activation.

The uploaded Set 3 item likewise identifies Person Accounts as the required feature.

Study Guide Reference: Public Sector Solution Product Configuration – Person Accounts; Individual Applications; constituent data model; Grants Management for individual applicants.

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

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.

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.

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

The verified configuration sequence is B, C, and E . Salesforce's Public Sector documentation explicitly instructs administrators to turn on document checklists , assign the required permissions to users who process documents, and configure Document Types for the information extracted from submitted documents.

Document Checklist must first be enabled through Document Checklist Settings. The intake officer then requires the appropriate permission-set licensing and object access so that only authorized personnel can work with Received Documents, Document Checklist Items, extracted information, and the relevant application records. Salesforce's Intelligent Document Automation user-setup guidance specifically requires assigning Document Checklist and Intelligent Document Workspace access to document-processing users.

Finally, a Document Type must be created to define the type of incoming document—in this case, a Business License Application. Salesforce lists creating a Document Type as a foundational IDA setup task.

Option D is incorrect because Document Types are configured through the dedicated Document Type functionality, not under Notes and Attachments.

Verified correction: the uploaded screenshot marks A, C, E , but Salesforce's documented configuration requirements support B, C, E . There is no equivalent generic "Enable Intelligent Document Automation" step that replaces enabling Document Checklist.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Document Automation; Document Checklist Settings; Document Types; user permissions; intake officer access.

A Sharing Set is the appropriate Experience Cloud sharing mechanism when external users need access to records associated with their account or contact but don't own those records themselves.

Salesforce states that a sharing set grants Experience Cloud site users access to records by mapping the user's Account or Contact relationship to a corresponding Account or Contact lookup on the target record. Salesforce gives Cases as a specific example: administrators can grant site users access to all Cases associated with the Account identified on the user's Contact record.

That matches this scenario precisely. The internal support team creates the Case, so the external constituent isn't necessarily its owner. A Sharing Set can expose the appropriate Cases to the authenticated external user based on the associated Account or Contact while keeping unrelated constituent Cases inaccessible.

Changing Case OWD to Public Read/Write would be excessively permissive and violate least-privilege principles. A permission set provides object- and field-level authorization but doesn't by itself grant access to specific records restricted by the Salesforce sharing model. Share Groups solve the opposite direction of high-volume sharing: they primarily give internal users access to records owned by high-volume external site users.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud sharing; Sharing Sets; Cases; Account/Contact access mappings; external OWD and least-privilege 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.

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

The Public Sector inspection experience provides purpose-built Lightning components that support inspectors while they execute onsite Visits. The three applicable components are Inspection Details, Inspection Action, and Inspection Tab Container .

Inspection Details presents the contextual information an inspector needs for the Visit, such as the inspection subject, location, relevant authorization information, and related inspection data. Inspection Action exposes inspection-specific actions that allow inspectors to execute the operational steps associated with the Visit. Inspection Tab Container organizes the various inspection functions into a usable tabbed workspace, allowing the inspector to move efficiently between inspection information, assessment activities, violations, signatures, and associated tasks.

These components belong to the execution layer of Public Sector inspection management and are intended to reduce navigation between unrelated Salesforce records while an inspector is conducting field work.

Inspection Dynamic Dashboards is not one of the standard built-in inspection execution components represented by this configuration. Inspection Calendar can be useful for scheduling and viewing inspection appointments, but it does not constitute one of the three embedded Visit-execution components asked for here.

The Set 3 question itself also identifies A, D, and E as the selected combination.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Visits; Inspection Details; Inspection Action; Inspection Tab Container; inspector workspace.

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

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.

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

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.

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

Categories for Dynamic Assessment questions are configured on the Assessment Question object. Salesforce explicitly instructs administrators to create categories by navigating to the Assessment Question object's Category picklist field and adding the required values.

Categories create logical groupings of assessment questions so that designers can efficiently locate and select the correct questions for different assessment contexts. Salesforce provides examples such as Fire Safety Inspection, Roof Inspection, Electrical Inspection, Solar Permit, and Public Safety Complaint. The same architecture applies here: categories could represent Take-Away, Dining, or another relevant inspection context and then be assigned to the specific questions to which each category applies.

The critical clue is that categorization applies to specific questions . Assessment Indicator Definitions represent predefined compliance indicators used primarily in the traditional inspection model; they aren't the object on which Dynamic Assessment question-category picklist values are maintained. Assessment Task Definitions group work performed during inspection execution but don't define the category metadata of individual Dynamic Assessment questions.

Action Plans organize repeatable tasks and assessment activities and are therefore also at the wrong layer.

Salesforce additionally supports Question Sets for grouping questions by context, but the question asks specifically where new categories are created.

Study Guide Reference: Public Sector Solution Product Configuration – Dynamic Assessments; Assessment Question; Category picklist; inspection question organization.

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

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.

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

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.

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

The lifecycle begins with Plan , where the grantmaker defines the funding program, objectives, eligibility, funding availability, and program structure. The organization then Engages prospective grantseekers by publishing and communicating the funding opportunity. Eligible grantseekers subsequently Apply , after which the grantmaker conducts the formal Review process and determines which applications receive an Award . The award then enters the Manage stage, covering requirements, disbursements, progress reporting, compliance, and performance monitoring, followed by formal Close Out .

This sequence aligns with Salesforce's Grants Management architecture. Salesforce Trailhead describes the lifecycle operationally: the grantmaker creates and publishes Funding Programs, a grantseeker applies by creating a Funding Request, verification and reviews occur, requirements are processed, and successful applications proceed to disbursement and continuing management.

Salesforce's Grantmaking material likewise separates application decisions from the subsequent Funding Award, then uses the award as the central record for post-award disbursements, requirements, expenditure tracking, progress reporting, and eventual completion.

Options C and D put lifecycle stages in an illogical order. Option A is structurally invalid because it places Apply before planning and repeats Apply.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management lifecycle; Funding Programs; applications; reviews; awards; post-award management; closeout.

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

Decision Explainer provides transparency into calculations and decisions produced by Business Rules Engine. For the Public Sector curriculum version represented by this question, Salesforce explicitly identifies Decision Explainer use cases that include individual and business application fees, unemployment benefits, and education loan eligibility checks . Therefore, among the available options, A and B correspond to supported Public Sector Decision Explainer scenarios. Salesforce's Public Sector Developer Guide specifically lists these examples when describing how Decision Explainer exposes the reasoning behind Expression Set calculations.

The architecture is based on Business Rules Engine executing an Expression Set, potentially calling Decision Matrices containing policy criteria, and Decision Explainer recording the inputs, calculations, intermediate values, and resulting decision. Reviewers can then inspect why a claimant qualified, failed eligibility requirements, or received a particular calculated amount.

Person Loans and Car Loan are not identified Public Sector Decision Explainer examples in this curriculum. They represent generic lending concepts rather than the documented Public Sector scenarios.

A versioning point is relevant: newer Salesforce Help currently uses housing loan eligibility checks in its example list, while the Salesforce developer documentation associated with the exam-era content uses education loan eligibility checks.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Decision Explainer; Business Rules Engine; Expression Sets; benefits eligibility and application-fee calculations.

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

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.