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

Before an initial OmniStudio package installation, Salesforce requires the organization to prepare both the browser environment and the Salesforce org.

First, the browser and Salesforce environment must satisfy the published minimum requirements. Salesforce specifies supported browser requirements, JavaScript availability, minimum system resources, a supported Salesforce edition, and the necessary OmniStudio entitlement. Second, the org must have Orders enabled. Third, email deliverability must be configured with the access level set to All email. These settings are part of Salesforce ' s explicit pre-installation checklist. The preparation procedure is intended to avoid package-test and runtime failures caused by missing Salesforce platform dependencies. Salesforce also notes that Enhanced Email is normally enabled and that OmniStudio package testing uses functionality related to the EmailMessage object. Person Accounts can be an important Public Sector prerequisite when the agency needs to represent individual constituents, but Person Accounts are not a universal OmniStudio package installation prerequisite. Similarly, enabling Assets is not one of the specified package preparation requirements. The proper sequence is therefore to validate the supported browser and platform environment, enable Orders, and ensure Salesforce email deliverability is configured for All email before beginning installation.

Study Guide References: Prepare to Install OmniStudio; OmniStudio Package Prerequisites; Enable Orders; Email Deliverability; Browser and Platform Requirements.

Salesforce Shield is the appropriate add-on when an organization requires enhanced security, auditability, monitoring, and data-protection controls. Shield is a suite of security products designed to add additional layers of security, compliance, and governance to Salesforce applications. Its core capabilities include Event Monitoring, Field Audit Trail, and Shield Platform Encryption, with Data Detect also available for sensitive-data discovery.

For a public sector implementation, Shield Platform Encryption strengthens protection for sensitive information stored at rest. Field Audit Trail provides long-term field-level historical information that supports regulatory audits, governance, and forensic review. Event Monitoring provides detailed visibility into user activity and data access, helping security teams detect suspicious behavior and demonstrate operational monitoring controls. Salesforce specifically describes these capabilities as relevant to regulatory compliance and security governance. Setup Audit Trail and standard Field History Tracking provide narrower auditing functions, while Classic Encryption does not deliver the comprehensive monitoring, encryption, and audit framework represented by Shield. Shield does not itself confer ISO 27001 certification, but it provides significant technical controls that can support an organization ' s compliance program.

Study Guide References: Salesforce Shield; Platform Encryption; Event Monitoring; Field Audit Trail; Public Sector Security and Compliance.

Business Rules Engine Expression Sets provide a built-in simulation capability for validating complex business calculations before production activation. This is particularly relevant for licensing and permitting fee calculations where multiple customer attributes can affect the result.

Salesforce defines Expression Sets as logical sequences containing variables, constants, calculations, conditions, lookups, and aggregations. After an Expression Set version is configured, the administrator can simulate it with test values to verify the resulting output before activation. Salesforce explicitly recommends running simulations with both default and custom test input variables. Business users can alter the input data, execute the Expression Set repeatedly, compare outputs, revise the rule configuration if necessary, and resimulate until the results match the required policy. Only after validation should the Expression Set version be activated. Advanced simulation also supports supplying input values through JSON, which is useful when an Expression Set contains a large number of input variables. Integration Procedures and Data Mappers are primarily used for orchestration, integration, and data transformation. Flow is general-purpose automation. Neither provides the purpose-built Business Rules Engine simulation capability required for repeatedly testing complex fee scenarios.

Study Guide References: Business Rules Engine; Expression Sets; Expression Set Simulation; Test Inputs; Decision Matrices; Fee Calculation Validation.

Public Sector includes native configuration for automatically creating Regulatory Code Violation records from inspection assessment results. Salesforce ' s current terminology identifies the relevant field as Assessment Question Status on the Inspection Assessment Indicator record.

The administrator configures the applicable failure status—such as Fail—to indicate that the result represents a violation. When an inspector selects that configured result during inspection execution, Public Sector automatically creates the corresponding Regulatory Code Violation record. Salesforce explicitly includes Configure an Assessment Question Status to Automatically Create a Violation as part of standard Inspections Setup. This declarative configuration keeps regulatory behavior within the standard inspection model. Assessment Indicator Definitions define what inspectors evaluate, Assessment Task Definitions group indicators into inspection activities, and Inspection Assessment Indicators capture the actual results. The status configuration determines when those results generate violations. A custom Flow is unnecessary because the platform already provides the required automation. Similarly, Action Plan Templates determine the inspection workload but do not independently control the conversion of a failed result into a violation.

Study Guide References: Inspections Setup; Inspection Assessment Indicator; Assessment Question Status; Regulatory Code Violation; Assessment Indicator Definitions.

The Employee Experience application combines access to the employee-facing community experience, productivity capabilities, and Public Sector-specific employee functionality. The configuration represented by this question therefore requires Employee Experience Community Access, Employee Productivity Plus Access, and Employee Experience for Public Sector.

Salesforce documents that the Employee Experience for Public Sector permission set grants employees access to Public Sector objects and capabilities used by employee-focused applications. Current Public Sector documentation also describes Employee Experience as the mechanism for providing government employees access to capabilities such as licensing and permitting, grantmaking, benefits, inspection management, and employee portals. Employee Productivity Plus Access supplies access to employee productivity and onboarding-related functionality. Salesforce ' s HR Service Center permissions documentation identifies Employee Productivity Plus Access as the permission set associated with the Employee Productivity Plus entitlement and distinguishes it from the User Data Access permission set, which primarily provides application, object, record-type, and flow access for the supporting data layer. Together, the three selected permission sets provide the experience-site, productivity, and Public Sector application access required for the prebuilt Employee Experience configuration.

Study Guide References: Employee Experience for Public Sector; Employee Experience Community Access; Employee Productivity Plus; Employee Experience Application Access.

Business Rules Engine supports calculations across collections of values by using Aggregate Groups and Aggregate steps within an Expression Set. This is the appropriate pattern when a single application contains multiple selected permits and each permit contributes a fee to the final amount.

Salesforce documents that an Aggregate Group executes the preceding steps once for each set of input values and then aggregates the resulting values according to the configured aggregation logic. Within the Aggregate Group, the Aggregate step can perform SUM, AVG, MAX, or MIN operations. For this licensing scenario, each selected permit can be evaluated to determine its applicable fee. The Expression Set then places the repeated evaluation inside an Aggregate Group, and an Aggregate step using SUM produces the application ' s total permit fee. A custom Lightning component is unnecessary because Business Rules Engine already provides declarative list aggregation. Permission sets are required for appropriate design or runtime access, but assigning permissions does not implement the actual multi-permit fee calculation. This configuration keeps fee policy inside Business Rules Engine, making the logic easier to maintain and reducing the need for custom code.

Study Guide References: Business Rules Engine; Expression Sets; Aggregate Group; Aggregate Step; SUM Function; Licensing and Permit Fee Calculation.

Salesforce ' s DocuSign integration supplies a defined electronic-signature lifecycle without requiring a custom signing framework. Salesforce documentation identifies three capabilities that directly correspond to this scenario: sending a contract document for review and signature, tracking the signed document and updating the associated contract status, and automatically invalidating a contract document awaiting signature when a newer document supersedes it.

Automatic invalidation is part of the contract/eSignature lifecycle itself. It does not require the organization to construct a separate approval process merely to void the superseded signing document. This is important for version integrity because the signer should not complete an outdated document after a replacement has become authoritative. The integration also tracks the progression of the signed document so Salesforce can maintain synchronization between the eSignature transaction and the relevant contract record. Sending the document for review and signature is therefore paired with post-signature status management. Allowing a reviewer to modify the actual contract-document contents during the signing operation is not one of these standard signing functions. Changes should be handled through the controlled contract-document generation and revision process.

Study Guide References: DocuSign Integration; Electronic Signatures; Contract Documents; Signature Status Tracking; Superseded Contract Documents.

Volunteer Management provides structured functionality for organizing volunteer opportunities, shifts, registrations, and volunteer participation. A core requirement of volunteer coordination is maintaining accurate staffing information as assignments and shifts change. Consequently, volunteer-capacity information such as registered volunteers and remaining staffing requirements is maintained as shift participation changes, including when scheduled work is canceled.

Salesforce ' s current Volunteer Management documentation confirms the broader functional model: organizations can create volunteer opportunities, define shifts and required staffing, allow volunteers to browse and register for opportunities through Experience Cloud, and track the hours contributed by volunteers. Salesforce also explicitly identifies Experience Cloud capabilities that let volunteers register for roles and enable organizations to track volunteer hours. This makes volunteer project registration and time reporting native elements of the volunteer-management lifecycle. Expense-reimbursement processing is not one of the defining Volunteer Management capabilities described for this scenario, and a volunteer chatbot is not the core package feature being tested. The operational emphasis is on volunteer recruitment, scheduling, shift coverage, participation, and service-hour tracking.

Study Guide References: Emergency Response Management; Volunteer Management; Volunteer Projects; Volunteer Shifts; Volunteer Registration and Hours Tracking.

A formal approval process is appropriate because the requirement involves conditional manager authorization together with a persistent, auditable approval history. Salesforce approval processes define the conditions under which records enter approval, who receives each approval request, what happens on approval or rejection, and any subsequent automated actions.

Bobahaven can configure entry or step criteria so the additional approval is required when the application ' s duration exceeds 12 months. The approver can be determined through the submitter ' s or record owner ' s Manager hierarchy field, allowing the request to be dynamically routed to the appropriate manager. Salesforce explicitly supports automated approver assignment through hierarchical fields such as Manager. Approval processing also provides the traceability required for regulatory compliance. Approval History records the progress of the request and identifies approval activity, while Salesforce supports reporting on historical approval-process instances and individual steps. Reassigning record ownership through Flow does not constitute formal approval. A Chatter request is collaborative communication rather than a controlled authorization record, and escalation rules serve different process requirements.

Study Guide References: Approval Processes; Approval Entry Criteria; Manager-Based Routing; Approval History; Licensing and Permitting Governance and Auditability.

Public Sector Case Analytics is designed to provide prebuilt analytics for case-management performance, including case-resolution duration, workload, historical trends, case-owner activity, and service effectiveness. The decisive requirement is that Bobahaven has not historically tracked case duration and wants ongoing trend analysis without introducing unnecessary customization.

Salesforce explicitly documents that when an organization doesn ' t have a field that tracks case duration, Public Sector Case Analytics uses its own CRM Analytics formula. For closed cases, the calculation uses the case opening and closing dates; for open cases, the current date is used. Business-hours duration calculations can also be incorporated when configured. The application ' s prebuilt dashboards provide metrics such as average time to close and historical case-status duration, making it suitable for comparing current and prior operational performance. Creating a new custom field would only begin collecting duration prospectively and would add configuration overhead. A standard report with a custom formula also lacks the breadth of the prebuilt analytical model. Leveraging Public Sector Case Analytics therefore minimizes customization while supplying the required historical and ongoing trend analysis.

Study Guide References: Public Sector Case Analytics; CRM Analytics; Case Duration Metrics; Case Overview; Historical Case Analytics.

Visual Studio Code together with Salesforce Developer Experience (DX) is the documented deployment mechanism for Lightning Web Components contained in Public Sector process packages. Salesforce ' s current Public Sector deployment procedure explicitly states that after importing process packages, administrators use Visual Studio Code and Salesforce DX to deploy the package ' s Lightning Web Components into the target Salesforce org.

The deployment workflow involves creating a Salesforce DX project in Visual Studio Code, importing the Lightning Web Components downloaded with the Public Sector process package, authenticating the target org, and then deploying the source metadata. This is required because the Lightning Web Component portion of the process package is Salesforce metadata and must be deployed through the developer tooling workflow. Change Sets can migrate many Salesforce configuration components between related orgs, but they are not the prescribed mechanism for installing these downloaded Public Sector process-package LWCs. The ANT Migration Tool is likewise not the documented deployment workflow for these components. Visual Studio Code without the Salesforce DX tooling also does not provide the complete project, authentication, metadata, and deployment framework required by the published Public Sector procedure.

Study Guide References: Public Sector Process Library; DataPacks/Process Packages; Lightning Web Components; Visual Studio Code; Salesforce DX Deployment.

Expression Sets and Decision Matrices have distinct but complementary roles in Business Rules Engine. Salesforce defines a Decision Matrix as a lookup table that accepts input values, locates the matching table row, and returns the associated output values. Decision Matrices are particularly effective for complex policy tables because the business rules remain structured, visible, and maintainable.

An Expression Set provides the procedural logic around those lookups. It can perform calculations, evaluate conditional logic, use variables and constants, aggregate values, and invoke one or more Decision Matrices. Salesforce explicitly documents that when an Expression Set calls a Decision Matrix, the engine locates the matching matrix row based on the supplied inputs and returns that row ' s output to the Expression Set. Therefore, option B correctly describes the relationship. Option A reverses the responsibilities: Expression Sets perform sequences of calculations, whereas Decision Matrices perform lookup matching. Option C likewise describes a Decision Matrix rather than an Expression Set. Option D is incorrect because Decision Matrices work with JSON-based integrations; the described XML-to-JSON relationship does not represent the standard BRE relationship.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Rule Execution; OmniStudio and BRE Integration.

An OmniStudio Integration Procedure is the appropriate orchestration layer because the transaction requires information from multiple sources and several server-side processing steps. Salesforce describes Integration Procedures as declarative server-side processes that can retrieve, transform, and send information between Salesforce and external systems, perform REST API calls, apply conditional processing, and execute several actions within a single server request.

In this scenario, the Integration Procedure can retrieve the base permit fee from the external system, retrieve the site or address information and applicable discount from the Salesforce custom object, apply the required processing logic, and return the resulting fee to the calling application experience. Salesforce explicitly recommends Integration Procedures when data must be accessed from multiple data-source types or when processing cannot be handled by a simple single-object extraction. A Data Mapper is optimized for comparatively focused Salesforce data operations and transformations. An OmniScript controls the guided user interaction, while a FlexCard primarily presents information and actions. Neither replaces the server-side orchestration required to combine external fee information with Salesforce data.

Study Guide References: OmniStudio Integration Procedures; External Data Integration; Data Mappers; OmniScripts; Licensing and Permitting Fee Processing.

The appropriate design combines authentication, bot protection, and restrictive external record access. Experience Cloud allows individual pages to be configured as Requires Login, which prevents unauthenticated visitors from accessing those pages even when other portions of the site are publicly available. Grant application OmniScripts should therefore be placed behind authenticated access when they collect or expose constituent-specific information.

CAPTCHA or reCAPTCHA adds automated abuse protection by distinguishing legitimate human submissions from bots. Salesforce documents reCAPTCHA implementations for Experience Cloud scenarios specifically to prevent automated or fraudulent form submissions. The external organization-wide default for sensitive application records should also be Private. Salesforce recommends keeping external OWD settings Private whenever possible and then opening access only through controlled sharing mechanisms. With Private external access, authenticated external users cannot automatically see other constituents ' records. A public application-reference search page would risk unnecessary information exposure and does not prevent form abuse. The combination of authentication, CAPTCHA, and restrictive sharing implements defense in depth for constituent application data.

Study Guide References: Experience Cloud Security; Requires Login; CAPTCHA/reCAPTCHA; External Organization-Wide Defaults; Grant Application Privacy; OmniScripts.

FlexCards are designed to present contextual information at a glance and expose relevant actions that users can execute directly from the card. Salesforce defines a FlexCard as a configurable information block that combines pertinent data with links or actions for processes within a specific context.

This makes option B a valid use case. A FlexCard can retrieve and display information from one or more configured data sources and summarize complex or related data into a concise, quick-glance user interface. Salesforce also documents FlexCards as presenting contextual data and actions together. Option D is also appropriate because FlexCards support numerous actions. Administrators can configure them to launch an OmniScript, navigate to another page or application, display a flyout, trigger data operations, or initiate other supported processes. A homepage FlexCard can therefore provide shortcuts into commonly used workflows. A multi-page questionnaire is more appropriately implemented with an OmniScript, whose primary purpose is guided interaction. Likewise, although FlexCards can support actions and data updates, complex inline tabular editing and calculation is not the primary use case represented here.

Study Guide References: OmniStudio FlexCards; Contextual Information; Data Sources; FlexCard Actions; OmniScript Launching; Quick-Glance User Experiences.

The Analytics for Licenses, Permits, and Inspections template performs a data compatibility check before creating the analytics application. Salesforce requires the Public Sector org to contain source records from the LPI operational data model so that the template can build its datasets and dashboards.

Salesforce ' s current data-requirements documentation identifies Visit as one of the supported source objects used by LPI analytics, along with Business License Application, Individual Application, Public Complaint, and Regulatory Transaction Fee. If the org lacks qualifying source data, the template returns an error during application creation and instructs the administrator to add the required data before trying again. Among the choices, missing Visit data is the relevant operational-data problem associated with the inspection portion of the analytics application. Visits represent actual inspection activity and are therefore central to metrics such as inspections performed, inspection volume, and related operational trends. Violation records, active Action Plan Templates, and Person Account enablement are not listed as the prerequisite represented by this compatibility-check scenario.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Data Requirements; Visit Object; Analytics Compatibility Check.

Salesforce provides the ContractEnvelopeStatusScheduler Apex class specifically for polling DocuSign envelope statuses in the supported eSignature integration. Salesforce documentation explicitly states that this class can be scheduled to poll DocuSign for envelopes submitted through the eSignature process.

The scheduled job queries envelope status and updates Salesforce so contract and document records reflect states such as sent, completed, or voided. Salesforce notes that when scheduled through the Salesforce UI, the job can run hourly. It can also be scheduled through Apex at shorter intervals, subject to DocuSign ' s minimum polling interval requirements. DocuSign requires at least 15 minutes between successive polling calls. Salesforce ' s recent support guidance also confirms that ContractEnvelopeStatusScheduler remains the scheduled job responsible for retrieving envelope-state updates and discusses asynchronous handling when many envelopes require updates simultaneously. Using Salesforce ' s provided scheduler is preferable to building a separate REST polling implementation because it follows the supported Industries/DocuSign integration architecture. The other scheduler class names do not correspond to the documented component.

Study Guide References: DocuSign Integration; ContractEnvelopeStatusScheduler; eSignature Envelope Status; Scheduled Apex; Contract Lifecycle Management.

The standard Public Sector regulatory data model provides the Regulatory Code Assessment Indicator object for associating regulatory requirements with the indicators inspectors evaluate. Salesforce describes assessment indicator definitions as the conditions inspectors check during onsite visits and explicitly supports relating those indicators to applicable regulatory codes so inspectors can reference the governing code while evaluating compliance.

The broader regulatory data model also identifies Regulatory Code Assessment Indicator as part of the standard licensing, permitting, inspection, fee, and enforcement model. This enables organizations to model compliance requirements declaratively rather than introducing unnecessary custom junction objects or custom master-detail relationships. Using the standard relationship is important because downstream Public Sector capabilities—inspection checklists, assessment execution, regulatory-code visibility, violations, and enforcement processes—are designed around the Salesforce industry data model. Creating a custom Regulatory Code Map would duplicate standard functionality and increase maintenance and integration complexity. A direct master-detail relationship also would not represent the intended mapping architecture.

Study Guide References: Public Sector Regulatory Data Model; Regulatory Code; Assessment Indicator Definition; Regulatory Code Assessment Indicator; Inspections and Regulatory Compliance.

Inspection configuration in Agentforce Public Sector separates the reusable checklist definition from the inspection classification used when a visit is created. An Action Plan Template contains the assessment tasks, assessment indicator definitions, signatures, and related inspection work that inspectors must complete. Salesforce requires inspection Action Plan Templates to target the Visit object and to use the assessment-oriented Action Plan type before they are published and used for inspection execution.

The Inspection Type determines the type of onsite inspection being created. During Visit creation, the user selects an inspection type, and the configured inspection framework determines which assessment process applies. Salesforce ' s documented inspection process establishes the relationship among Visit, Inspection Type, and the relevant published Action Plan Template. Therefore, when an administrator clones an existing template to produce a revised version, the configuration that references the prior template must also be updated. Otherwise, newly generated Business Re-Opening inspections continue to use the previously associated template even though a newer template exists. Merely giving the templates identical names does not change the underlying record association, and creating a separate Inspection Type version is unnecessary when the existing type should use the new template.

Study Guide References: Inspection Types; Action Plan Templates; Visits; Assessment Tasks; Inspection Configuration and Template Associations.

The appropriate architecture uses an Action Plan Template to standardize document requirements across every Business License Application. Business License Application is a supported Action Plan target object, so the template provides the repeatable framework from which individual application-specific action plans are generated.

Each required document should be represented as a Document Checklist Item within the Action Plan Template. Salesforce explains that document checklist items added to a template are automatically included in action plans generated from that template. The checklist gives applicants a structured view of required supporting documents while allowing uploaded files and document status to be managed consistently. After the template and its three checklist items are configured, the template must be published. Automation can then associate or generate the corresponding action plan when a new Business License Application enters the applicable process. This ensures that every application receives the same prescribed document requirements. Creating standalone checklist records manually on every application would be repetitive and susceptible to inconsistent configuration. Tasks also do not substitute for Document Checklist Items because checklist items are specifically designed to represent required documents and support upload-management processes.

Study Guide References: Action Plans; Action Plan Templates; Business License Application; Document Checklist Items; Intelligent Document Automation.

Salesforce Entitlement Management applies service-level processes to supported service records, particularly Cases. An Entitlement Process defines the service timeline, while Milestones represent required service steps such as response or resolution deadlines. Salesforce confirms that entitlement processes for this pattern run on Cases and can enforce milestone-based service levels.

The requirement is explicitly proactive management. Milestone Warning Actions are therefore essential because they execute when a milestone is approaching violation. Salesforce supports actions such as email alerts, tasks, field updates, flows, and outbound messages before an SLA deadline is missed. Violation Actions, by contrast, execute after the milestone has already been breached. Bobahaven can use Cases to operationally track applications requiring service intervention, associate them with the appropriate entitlement process, and configure milestones representing expected approval-response times. Warning actions can alert owners or supervisors while enough time remains to intervene. The alternatives that trigger escalation only after an SLA breach are reactive rather than preventive. Furthermore, standard entitlement processes are designed around supported service records such as Cases rather than being attached directly to Public Sector application objects in the manner proposed by the other options.

Study Guide References: Service Cloud Cases; Entitlements; Entitlement Processes; Milestones; Warning Actions; SLA Management and Escalation.

The configuration should begin by turning on Document Checklist functionality, because Intelligent Document Automation uses document checklist items to organize, associate, and manage documents received for application-processing workflows. Salesforce ' s documented Document Type setup procedure explicitly requires enabling Document Checklist before creating the relevant document structure.

The consultant must then create a Document Type representing the Business License Application. Document types define the category of incoming information and provide the structure required for document extraction and transformation. Finally, the intake officer must receive the appropriate permissions and permission sets. Salesforce specifies the Document Checklist and Intelligent Document Workspace permissions for users who work with documents and forms and also requires appropriate object-level access to objects such as Received Document and Received Document Type. This is the configuration layer that allows document-processing access to be limited to the intended users. Document types are configured through Salesforce ' s Document Type functionality, not Notes and Attachments. The resulting architecture supports controlled document intake, checklist management, structured extraction, and review of business license applications.

Study Guide References: Intelligent Document Automation; Document Checklist; Document Types; Intelligent Document Workspace; User Access and Permission Sets.

Employee Experience for Public Sector brings together employee-facing service capabilities intended to give government workers a centralized digital workplace for accessing information, obtaining support, and completing common employee-service processes.

Employee Workspace supplies the employee-facing environment where users can access relevant services, information, and productivity capabilities from a unified experience. HR Service Center supports structured employee requests and human-resources service delivery, allowing HR teams to manage employee cases and provide consistent support. Employee Concierge provides a guided entry point through which workers can locate assistance and connect with relevant employee services. Together, these capabilities align with the Employee Experience objective of improving how public employees obtain organizational information and support while reducing fragmented service interactions. Workplace Strategy Planner and Workplace Command Center focus on workplace or physical-location planning and operational workplace management rather than the core employee-service experience represented by this question. They therefore belong to a different functional area from the employee workspace, HR service delivery, and concierge capabilities.

Study Guide References: Employee Experience for Public Sector; Employee Workspace; HR Service Center; Employee Concierge; Employee Service Delivery.

Employee Experience and HR-service processes commonly use the Case object to represent sensitive employee requests, including HR, workplace, and employee-support matters. Because these cases can contain confidential personal or employment information, the appropriate baseline sharing model is to restrict access and then selectively grant it to authorized personnel.

Salesforce ' s Employee Concierge configuration explicitly sets the organization-wide default for the Case object to Private. This establishes the most restrictive standard access level and ensures that unrelated users don ' t automatically gain visibility into HR cases. Organization-wide defaults form the foundation of Salesforce record-level security. When Case is Private, the record owner and users who receive access through appropriate sharing mechanisms, queues, role hierarchy behavior, teams, or administrative privileges can access the case as configured. This supports least-privilege handling of employee information. Mirroring the organization chart into the role hierarchy could unintentionally widen access to confidential cases and does not itself secure HR data. Disabling approval processes has no direct relationship to record confidentiality. Likewise, the key security control required here is establishing Private OWD rather than relying on a hierarchy configuration as the primary protection.

Study Guide References: Employee Experience for Public Sector; HR Service; Case Security; Organization-Wide Defaults; Least-Privilege Record Access.

An Action Plan Template can standardize the recurring work required for each Business License Application while also including a Document Checklist Item for the applicant ' s driver ' s-license image.

Action Plan Templates serve as reusable blueprints containing Tasks, Document Checklist Items, or a combination of both. Salesforce documentation explicitly describes these templates as structures for defining repeatable work and required supporting documentation. Public Sector ' s Intelligent Document Automation guidance further confirms that Document Checklist Items can be incorporated into Action Plan Templates and are automatically created in Action Plans generated from those templates. This architecture maps cleanly to the scenario. Tasks can represent the background check, entry of results into the external system, recommendation preparation, and submission for approval. The driver ' s-license upload is represented by a Document Checklist Item associated with the required document type. The resulting Action Plan gives reviewers a consistent operational checklist while still allowing application-specific work to be managed where required. Option C contradicts the documented ability to add Document Checklist Items to Action Plan Templates. The other restrictive statements do not reflect the flexibility of Action Plans for managing and extending operational work.

Study Guide References: Action Plans; Action Plan Templates; Tasks; Document Checklist Items; Business License Application; Intelligent Document Automation.

The appropriate relationship pattern is Person Account → Individual ← Employee. In the relevant employee-model architecture, the Individual record provides the common person-centric relationship layer through which Employee information can be associated with another Salesforce representation of the same person. Salesforce ' s Work.com data-model documentation describes Employee records being associated with Individual records and synchronization mechanisms that maintain the Individual relationship as employee information is created or updated.

Public Sector uses Person Accounts to represent individual constituents. A Person Account combines the Account and Contact representation into a single constituent-facing record and is the recommended Public Sector model for individual people applying for licenses, permits, benefits, grants, or government services. Consequently, when the Employee data model must coexist with the Public Sector constituent model, the Individual relationship provides the bridge between the Employee representation and the Person Account representation. Routing the association through User would incorrectly make the Salesforce user identity the integration point, and using Contact would not satisfy the scenario ' s explicit requirement to connect the employee model with a Person Account.

Study Guide References: Public Sector Person Accounts; Employee Data Model; Individual Object; Constituent Data Modeling; Cross-Cloud Person Relationships.

Salesforce ' s DocuSign integration provides a packaged electronic-signature lifecycle for contract documents. Salesforce explicitly documents that the integration can send a contract document for review and signatures, track the signed document and update the contract record status, and automatically invalidate a pending signature document when a newer contract document supersedes it.

These features maintain transactional integrity throughout the signature process. Sending the document initiates the controlled signature workflow. Status tracking keeps Salesforce synchronized with the state of the DocuSign envelope and enables the contract record to reflect completion. Automatic invalidation prevents a signer from executing an outdated document version after a newer authoritative version is generated. An additional Salesforce approval process is not required simply to invalidate the superseded signature document because that behavior is already part of the supported eSignature lifecycle. Similarly, changing contract contents during the signing process is not one of the standard DocuSign capabilities represented here. Document changes should occur through the controlled document revision and regeneration process before a new signature request is issued.

Study Guide References: DocuSign Integration; Electronic Signatures; Contract Documents; Signature Tracking; Superseded Document Invalidation.

Grants Management provides the complete grantseeker portal capability required for this scenario. Salesforce describes Grants Management as enabling organizations to launch a portal where grantseekers can discover funding opportunities, apply for funding, view application status, and submit ongoing progress information for awarded grants.

The portal is implemented through Experience Cloud using the Grantee Portal template. Salesforce states that this preconfigured template provides a place where applicants can view available Funding Programs, submit applications, and manage their applications after submission. The Grants Management workflow also supports application materials and attachments, allowing supporting documentation to be incorporated into the funding-request process. Although Grants Management uses the Outbound Funds Module data model underneath its grantmaking functionality, Salesforce distinguishes the products functionally. Grants Management provides enhanced portal capabilities, application workflows, self-registration, application mapping, review workspaces, Action Plans, and other grantmaker functionality beyond the basic Outbound Funds foundation. Foodvania therefore does not need to design a separate relief portal around the underlying Outbound Funds Module. Grants Management supplies the packaged portal experience required for external recipients to apply, provide supporting information, and monitor application status.

Study Guide References: Grants Management; Grantee Portal; Experience Cloud; Funding Programs; Funding Requests; Grantseeker Application Management.