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

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.

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

The requirement is straightforward operational reporting rather than advanced analytical modeling, so standard Salesforce Reports and Dashboards provide the lowest-cost and lowest-complexity solution. A custom dashboard can consolidate multiple approval metrics—pending application count, aging, application duration, and longest-pending items—into a single visual view.

The second requirement is that approvers see the information when they log in . Salesforce supports adding Dashboard and Report Chart components directly to a Lightning Home page through Lightning App Builder. A customized Home page can then be activated for the appropriate user context, including assignment by profile.

That makes A superior to B. A dashboard provides the requested summary , whereas a report primarily presents rows of data. More importantly, Lightning Home page activation supports profile-based assignment; a role isn't the appropriate activation mechanism expressed in option B.

CRM Analytics would be technically capable of presenting approval analytics, but it introduces additional licensing, datasets, configuration, and operational overhead without providing a material advantage for the relatively simple requirement. Salesforce already supplies native approval user-interface capabilities and Home page support for approval work.

Therefore, a standard custom Approvals dashboard placed on an Approver-profile Home page satisfies the requirement while minimizing customization and cost.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Reports and Dashboards; Lightning Home Pages; approval monitoring; user-profile page assignment.

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

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.

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

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.

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

Grants Management and Outbound Funds Module provide the Salesforce-native funding architecture represented by this scenario. Salesforce states that Grants Management uses the Outbound Funds Module data model , which includes Funding Programs, Funding Requests, Reviews, Requirements, Disbursements, and related financial-tracking entities.

The grantseeker's submitted application is represented by a Funding Request . Review records capture the reviewers' status and feedback, while Disbursement records represent funds that have been made or are scheduled to be made to the recipient. Salesforce's Outbound Funds documentation specifically states that the module manages Funding Requests and outgoing funds and can create disbursements for expenditures.

For more detailed expenditure accounting, the Outbound Funds data model includes GAU Expenditure , which connects a Disbursement to a General Accounting Unit and identifies which allocation or accounting category funded the disbursement. This supports audit scenarios in which expenditures need to be distinguished among categories such as mortgage arrearage and utility assistance.

FinancialForce Accounting is an external accounting solution and is not required by this Public Sector design. Nonprofit Success Pack can extend certain GAU functionality, but selecting NPSP alone would not replace the Grants Management/Outbound Funds framework specified by the scenario.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management; Outbound Funds Module; Funding Requests; Disbursements; GAU Expenditures.

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

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

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

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

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

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

Salesforce's documented preparation process for installing the OmniStudio package directly validates A, B, and E . Before installing OmniStudio into an organization that doesn't already have the package, administrators must verify that the browser and Salesforce environment satisfy OmniStudio's minimum technical requirements. This includes supported browser behavior, JavaScript availability, sufficient environment capability, and a supported Salesforce edition.

Salesforce also instructs administrators to verify that Orders are enabled . OmniStudio installation tests and configuration depend on underlying Salesforce functionality, so this is an explicit prerequisite rather than an optional Public Sector data-model choice.

The same preparation procedure requires Salesforce email deliverability to use the All email access level. Salesforce specifically directs administrators to configure Access to Send Email accordingly.

Person Accounts aren't a generic OmniStudio package-installation prerequisite. They are enabled for Public Sector business requirements that need individual constituent representation, but OmniStudio can operate in organizations that don't use Person Accounts. Similarly, enabling Assets isn't identified in Salesforce's package-preparation checklist.

One current-version consideration is that Salesforce states that, beginning with newer OmniStudio licensing arrangements, the standard designer/runtime may be available without installing the legacy managed package. The question nevertheless targets the managed-package prerequisite sequence.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio Installation; package prerequisites; Orders; email deliverability; browser requirements.

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

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.

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

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.

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

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.

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

Salesforce explicitly recommends setting Organization-Wide Defaults for Case to Private when configuring employee and HR-service solutions containing sensitive information. A Private OWD establishes the restrictive baseline: users don't automatically receive access to another employee's HR Case unless access is subsequently provided through ownership, queues, public groups, sharing rules, or another authorized sharing mechanism.

Salesforce's HR data-protection guidance is particularly direct. HR Cases may include payroll, benefits, leave, employee-relations, disciplinary, and other sensitive information. Salesforce recommends that such cases be accessible only to the case owner and the appropriate HR agent or HR group. It also specifically warns against mirroring the organizational chart into the Salesforce role hierarchy because managers could otherwise inherit visibility into records owned by employees beneath them.

The Employee Concierge installation similarly configures the Case object's organization-wide default to Private , reinforcing this as the standard security model for employee service records.

Option A would potentially broaden sensitive-data exposure. Option C isn't the appropriate Case security mechanism for this requirement, and disabling approval processes has no relationship to baseline record confidentiality.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Employee Experience security; HR Service Center; Case sharing; Organization-Wide Defaults; least privilege.

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

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

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

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

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

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

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

An Integration Procedure is the correct orchestration component because this requirement combines information from different data sources: an external fee system and Salesforce custom-object data. OmniStudio Integration Procedures are declarative server-side processes designed to execute multiple data operations within a single server call.

Salesforce specifically states that Integration Procedures can retrieve, transform, and send information between Salesforce and external systems, invoke REST APIs, perform conditional processing, and combine information from multiple sources into a single response.

That architecture maps directly to this scenario. The Integration Procedure can retrieve the base permit fee from the external system, retrieve site or address information and applicable discount information from Salesforce, apply the required transformations or calculations, and return the resulting fee to the calling application process.

A Data Mapper is more suitable for straightforward Salesforce object reads, writes, and transformations. It is not the preferred component when multiple heterogeneous data sources and external REST services are involved. A FlexCard primarily presents information and actions to users. An OmniScript manages the interactive guided process, but it would normally invoke an Integration Procedure to execute this server-side integration.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; external data access; REST integration; multi-source orchestration; license and permit fee processing.

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

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

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

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.

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

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

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

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

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

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

Scope, schedule, and cost constitute the classic project-management triple constraint and are the correct considerations for an Agentforce Public Sector implementation. Salesforce Trailhead explicitly identifies scope, schedule, and cost as the three interconnected project constraints. A modification to one dimension generally affects at least one of the others.

Scope defines what capabilities and requirements the implementation must deliver—for example, licensing, permitting, grants management, constituent portals, or integrations. Schedule defines when those deliverables must be completed, including statutory deadlines, procurement milestones, fiscal-year constraints, or mandated program launch dates. Cost represents the approved implementation budget, including Salesforce products, implementation resources, integration work, testing, migration, training, and operational readiness.

For a public-sector implementation, these constraints require particularly disciplined governance because agencies commonly operate under fixed budgets and formally approved scopes while also facing regulatory or legislative deadlines. Expanding scope without changing schedule usually requires additional cost or resources. Conversely, reducing the budget may require scope reduction or schedule extension.

Resources certainly affect project execution, but they are not part of the standard three-way constraint identified by Salesforce project-management guidance. Workshops and tools are implementation mechanisms rather than primary project constraints.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – implementation planning; project governance; scope management; schedule management; budget/cost management.

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

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.

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

Salesforce's official restriction-of-processing guidance directly addresses this scenario. When an organization no longer needs a person's data but must preserve it because the person is involved in a legal proceeding, Salesforce recommends exporting the data for retention and then deleting the person's data from Salesforce . This preserves the required historical evidence while preventing normal Salesforce processing of the retained information.

This distinction is important. Merely making Salesforce records invisible to ordinary users does not necessarily stop automated processing, integrations, background services, reporting, analytics, or administrative access. Therefore, option C does not provide the same level of processing restriction.

Salesforce provides the same guidance for constituent-oriented scenarios: if a constituent no longer engages with an organization but requests preservation because of potential legal proceedings while also requesting that processing stop, export the data and delete the Salesforce records.

Modern implementations with Privacy Center can also use Privacy Hold for defined legal-retention policies, but that is an additional licensed capability and isn't an option in this question.

Verified correction: the Set 2 screenshot marks C; official Salesforce restriction-of-processing documentation supports D .

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – data privacy; restriction of processing; retention; legal proceedings; data export and deletion.

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