Free Public-Sector-Solutions Practice Test Questions and Answers (2026)

To successfully implement the Salesforce Grants Management package and an accompanying portal, specific prerequisites must be met. The Grants Management application is built exclusively for the Lightning Experience, necessitating the migration of internal users from Salesforce Classic. Chatter is a core requirement for the application's collaborative features and record feeds to function correctly. For the external portal, where grant applicants will manage their applications, Customer Community Plus licenses are required. These licenses provide the necessary object access and advanced sharing capabilities for grantseekers to interact with their specific funding request records within the portal.

A. Customer Community Licenses: This license type is insufficient. The Grants Management portal requires the advanced sharing and object access capabilities provided by the Customer Community Plus license to function as designed.

C. Enable Web-to-Lead: This feature is used for capturing marketing leads from a website into the Lead object. The Grants Management intake process uses a dedicated portal and custom objects, not the standard Web-to-Lead functionality.

1. Salesforce Help, Public Sector Solutions Documentation, "Set Up Grants Management": This document explicitly lists the prerequisites for installing and using the Grants Management package.

Reference for Answer D (Lightning Experience): Under the "Prerequisites for Grants Management" section, it states, "Grants Management is available in Lightning Experience only."

Reference for Answer B (Enable Chatter): In the same "Prerequisites for Grants Management" section, a required step is to "Enable Chatter."

2. Salesforce Help, Public Sector Solutions Documentation, "Set Up a Portal for Grantseekers": This guide details the requirements for creating the external-facing portal for applicants.

Reference for Answer E (Customer Community Plus Licenses): In the "Assign Permissions and a License to Grantseekers" subsection, the instructions state, "Then assign them a Customer Community Plus license." This confirms the specific license type needed for external users.

During a Salesforce Public Sector Solutions implementation, a consultant's primary role is to elicit, analyze, and document the client's needs to configure the system correctly. Functional Requirements Specifications (FRS) and User Stories are two standard, key artifacts used for this purpose. An FRS is a formal document common in traditional (waterfall) methodologies that details what the system must do. User Stories are the primary method for capturing requirements in Agile methodologies, describing a feature from an end-user's perspective. Both are central to defining the scope and functionality of the solution, making them core deliverables for a consultant.

A. Budget Plan: The budget plan is typically created and managed by the public sector agency's project manager or leadership, not the implementation consultant whose focus is on solution design and configuration.

C. Marketing Plan: A marketing plan is irrelevant as it focuses on promoting a product to external customers. A Public Sector Solutions implementation is an internal project to improve service delivery.

1. Salesforce Trailhead, Module: Consultant's Guide to Business Analysis, Unit: Document and Confirm Requirements. This unit explicitly details the methods for documenting requirements. It states, "User stories are the most common way to document requirements on an agile project... For more traditional projects, you might create a business requirements document (BRD) or a functional requirements document (FRD)." This directly supports that both User Stories (D) and Functional Requirements Specifications (B) are key documents a consultant produces.

2. Salesforce Trailhead, Module: Salesforce Agile Basics, Unit: Write and Review User Stories. This module establishes User Stories as a fundamental component of Salesforce implementations using an Agile framework. It defines a user story as "a way of describing a feature of a product from the perspective of the user," confirming its role as a primary requirements document.

3. Sommerville, I. (2016). Software Engineering (10th ed.). Pearson. Chapter 4, "Requirements Engineering," extensively covers different methods for documenting system requirements. Section 4.5, "Requirements specification," describes the Software Requirements Specification (SRS), of which an FRS is a key component. Section 4.2.3, "Scenarios and user stories," details the use of user stories in agile methods. This academic source validates both FRS and User Stories as standard, key document types in software implementation projects.

The optimal solution is a standard Salesforce Approval Process. This feature is designed specifically for formal, multi-step approvals that require an audit trail. The process can be configured with entry criteria to trigger only for applications with a duration exceeding 12 months. It can then automatically route the approval request to the submitter's manager. Most importantly, every action (submission, approval, rejection, comments) is logged in the "Approval History" related list, which directly satisfies the regulatory compliance and auditability requirement.

A. "Approval escalation rule" is not a standard Salesforce feature. Escalation rules are primarily used for Case management to reassign records that are not actioned in time, not for formal sign-offs.

C. While the Business Rules Engine can identify the correct records, using Chatter for approval is informal and lacks the structured, reportable audit trail necessary for regulatory compliance.

D. A Flow changing record ownership does not constitute a formal approval or "sign-off." It merely transfers responsibility for the record, failing to capture an explicit, auditable approval decision.

1. Salesforce Help, Approval Process Overview: "An approval process is an automated process your organization can use to approve records in Salesforce... An approval process specifies the steps necessary for a record to be approved and who must approve it at each step... Salesforce maintains a history of the approval process..." This directly supports the use of an Approval Process for auditable, conditional approvals. (Salesforce Help, Document ID: sf.approvalsconsiderations.htm)

2. Salesforce Help, Considerations for Approval Processes: "When a record is submitted for approval, it’s locked. Users can’t edit it until it’s approved, recalled, or rejected." This locking mechanism is crucial for maintaining data integrity during a formal review, a feature not inherent in the other proposed solutions. (Salesforce Help, Document ID: sf.approvalsconsiderations.htm, Section: "What Happens When a Record Is Locked?")

3. Salesforce Help, Business Rules Engine in Public Sector Solutions: "Business Rules Engine gives you a suite of services... to automate decisions... Use Business Rules Engine to create rules that evaluate complex criteria..." This shows BRE is for decision automation (e.g., determining eligibility), not for managing the human workflow of an approval, which is the core requirement. (Salesforce Help, Document ID: sf.pssadminbre.htm)

According to the official Salesforce OmniStudio documentation, several prerequisite tasks must be completed within the Salesforce org before initiating the package installation. These include enabling specific standard features that OmniStudio components depend on. The three critical org-level configurations are: enabling Orders, enabling Person Accounts to support business-to-consumer or government-to-citizen models, and setting the organization-wide email deliverability access level to "All email". Completing these steps ensures that the target org has the required object schema and settings to prevent installation failures and ensure the proper functioning of post-installation scripts and core package features.

B. Enable Assets: The official OmniStudio installation guide does not list enabling Assets as a mandatory prerequisite for installing the core package.

E. Confirm browser settings meet published minimum requirements: While using a supported browser is a documented requirement for operating OmniStudio tools, the other three options are specific org configurations grouped as "Required Features" essential for the server-side package installation to succeed.

1. Salesforce Help. (2023). Before You Install the OmniStudio Package.

Reference: Under the section "Enable Required Features," the documentation explicitly lists the following prerequisites:

"Enable Orders"

"Enable Person Accounts"

"Set Email Deliverability to All Email"

This source directly validates answers A, C, and D as mandatory org-level configurations. It also validates that enabling Assets (B) is not a listed prerequisite.

2. Salesforce Help. (2023). OmniStudio Documentation.

Reference: The "Install OmniStudio" section consistently points to the prerequisite tasks mentioned above. The browser requirements are listed separately from the org feature enablement, highlighting a distinction between client-side usage requirements and server-side installation prerequisites. This supports the exclusion of option E in favor of the three required org features.

The Salesforce Public Sector Solutions data model uses the Individual object as a central hub to create a unified profile for a person. The PersonAccount object, representing a constituent, has a standard lookup field (IndividualId) to the Individual object. Similarly, the Employee object, part of the Employee data model, also has a lookup field (IndividualId) to the Individual object. This architecture allows an organization to link a person's record as a constituent (PersonAccount) with their record as an employee (Employee) through a common, shared Individual record, providing a 360-degree view.

B. PersonAccount->User->Employee: This path is incomplete. It bypasses the Individual object, which is the core component for creating a unified profile in the Public Sector data model.

C. User -> Individual <- Custom employee object: This is incorrect because the question refers to the standard "Employee data model," not a custom object, and it incorrectly starts the relationship from the User object instead of the PersonAccount.

D. Contact -> Individual <- Employee: While a PersonAccount includes a Contact record that links to an Individual, the question explicitly asks about linking the PersonAccount. Option A is more direct and accurately represents the primary relationship.

---

1. Salesforce Help, Public Sector Solutions Developer Guide, "Employee Data Model": The documentation outlines the objects used to manage employee information. It specifies that the Employee object contains an IndividualId field, which is a lookup to the Individual object, linking the employee record to the unified individual profile.

Reference: Salesforce Help, Public Sector Solutions Developer Guide, "Employee Object Fields" section.

2. Salesforce Help, "Use the Individual Object to Store Data Privacy Preferences": This document explains the role of the Individual object. It states, "The Individual object provides a universal, unique ID that links all of a person’s information across Salesforce clouds... For example, you can link a person’s contact record, their person account record, and their user record to the same Individual record." This confirms the Individual object's role as the central link for PersonAccount.

Reference: Salesforce Help, "How the Individual Object Works with Other Records" section.

3. Salesforce Object Reference Guide, "Employee": The official object reference details the fields on the Employee object. It lists IndividualId as a "Lookup(Individual)" field type, confirming the direct relationship from Employee to Individual.

Reference: Salesforce Object Reference for Salesforce and Lightning Platform, "Employee" object field definitions.

4. Salesforce Object Reference Guide, "Account": The reference for the Account object, which underlies the PersonAccount, lists the IndividualId field. This field is a "Lookup(Individual)" and is populated for person accounts, establishing the PersonAccount -> Individual link.

Reference: Salesforce Object Reference for Salesforce and Lightning Platform, "Account" object field definitions.

The scenario presents two distinct security concerns: protecting application forms from bot spam and ensuring the privacy of constituent data. A comprehensive solution must address both.

Implementing CAPTCHA (D) is the standard and most direct method to prevent automated bots from submitting spam through public-facing forms on an Experience Site. This directly mitigates the risk of spamming.

Setting the external organization-wide default (OWD) for grant application objects to Private (E) is a foundational security measure. It ensures that a constituent's data is not visible to any other external user by default, which is critical for complying with privacy regulations and securing sensitive information submitted through the forms.

A. "Salesforce Spam Check" is not a specific, standard feature. The correct implementation for bot and spam protection on Experience Sites is CAPTCHA.

B. Requiring a login adds a barrier to entry for new applicants and is a business decision, not a direct technical solution for spam on a public form. CAPTCHA protects public forms without requiring a login.

C. This feature addresses checking application status after submission; it does not provide any security or protection for the initial application form itself.

1. CAPTCHA for Spam Protection (Supports D):

Salesforce Help, Add Google reCAPTCHA to Your Site. This document outlines the procedure for implementing Google reCAPTCHA on Experience Cloud sites, stating, "To protect your site against spam and abuse from 'bots,' you can add a Google reCAPTCHA widget to your login, sign-up, and forgot password pages." This principle extends to any public-facing form, such as a grant application.

2. External OWD for Data Privacy (Supports E):

Salesforce Help, External Organization-Wide Defaults. This documentation explains, "External organization-wide defaults provide separate organization-wide defaults for internal and external users... Setting the default access for external users to Private for an object ensures that a user can see only their own records." This is the primary mechanism for ensuring constituent data privacy in an Experience Site.

3. Public Sector Solutions Security Model (Supports E):

Salesforce Help, Set Up Security for Grants Management. This guide details the necessary security configurations, including, "Configure organization-wide default settings for internal and external access... For external users, set the default access to Private for Funding Award, Funding Award Requirement, Funding Request, and other objects." This explicitly recommends setting the OWD to Private for the core Grants Management objects.

The Emergency Response Management package for Public Sector Solutions includes several preconfigured dashboards to provide immediate analytical value. The Emergency Hotspots dashboard uses map-based visualizations to show the geographic concentration of emergency requests, directly addressing the need to understand where to increase focus. The Emergency Requests Overview dashboard provides a high-level, aggregate view of all incoming requests, their status, and types, which is essential for overall situational awareness and resource allocation. Both are designed for rapid deployment to accelerate an organization's response capabilities.

A. Global Emergency View: This is not a standard, preconfigured dashboard name provided within the Salesforce Emergency Response Management package.

B. Visits: While "Visits" is a standard Salesforce object, it is not the name of a preconfigured dashboard in the Emergency Response Management package for high-level analysis.

1. Salesforce Help Documentation, Public Sector Solutions, Emergency Response Management Dashboards: This official documentation explicitly lists the preconfigured dashboards available.

Section: "Emergency Response Management Dashboards"

Content: "The Emergency Response Management app includes these preconfigured dashboards: Emergency Requests Overview, Emergency Hotspots, Emergency Response Operations, and Emergency Response Team Performance." This directly confirms options C and D and shows that A and B are not included.

2. Salesforce Developer Documentation, Public Sector Solutions Developer Guide: This guide details the components and objects included in the solution.

Section: "Analytics for Emergency Response Management"

Content: The guide describes the out-of-the-box analytics, including the "Emergency Hotspots" dashboard for visualizing request density and the "Emergency Requests Overview" for a summary of request volume and status. This corroborates the purpose and existence of the correct answers.

The most fundamental step to protect sensitive data in Salesforce is to set the most restrictive access level at the organization-wide default (OWD) level. For sensitive HR data managed through the Case object, setting the OWD to 'Private' is the correct initial action. This configuration ensures that, by default, a case record is only accessible to its owner and users explicitly granted access through sharing rules. This application of the principle of least privilege is the cornerstone of securing confidential employee information within the Employee Experience Management solution.

A. Disable all approval processes on the Case object: Approval processes are for business logic and workflow automation; they do not control the fundamental visibility of records.

B. Disable the Grant Access Using Hierarchies setting on the Case object: While this is a crucial secondary step for HR confidentiality, it is only effective after the OWD is set to Private. It is not the foundational configuration.

C. Mirror the Org Chart into The Role Hierarchy: This can be detrimental to security, as the role hierarchy controls data access. A manager's position in the org chart should not automatically grant them access to a subordinate's sensitive HR cases.

1. Salesforce Help, Organization-Wide Sharing Defaults: "Of all the record access features, organization-wide defaults have the biggest impact... Setting an object to Private makes those records visible only to record owners and users above them in the role hierarchy." This establishes the OWD as the foundational security setting.

2. Salesforce Public Sector Solutions Documentation, Set Up Employee Concierge: In the "Configure Sharing Settings for Employee Concierge" section, the first instruction is: "From Setup, in the Quick Find box, enter Sharing Settings, and then select Sharing Settings. Click Edit. For the Case object, select Private." This directly confirms the required configuration for the Employee Experience solution.

3. Salesforce Architect's Handbook, Record-Level Security: The data security model is layered, with Organization-Wide Defaults being the first layer of control that is evaluated. "OWDs are the default access level that a user has to records they do not own... This is the starting point of your security model." This confirms that OWD is the primary and most critical configuration for establishing data protection.

The Public Sector Solutions (PSS) data model provides a standard junction object to establish the required many-to-many relationship between assessment indicators and regulatory codes. This object is named AssessmentIndRegulatoryCode, with the label "Assessment Indicator Regulatory Code". It connects the AssessmentIndicatorDefinition object (which stores the list of indicators) and the RegulatoryCode object. Using this standard junction object is the correct approach to leverage the pre-built PSS data model, ensuring scalability and adherence to best practices without creating redundant custom objects or relationships.

A. Create a master-detail relationship between Regulatory Code and Assessment Indicator

This creates a one-to-many relationship, which does not meet the requirement for an indicator to map to multiple codes and vice-versa.

B. Use the Regulatory Code Assessment Indicator junction object

This is incorrect because the standard junction object in the Public Sector Solutions data model is named "Assessment Indicator Regulatory Code" (AssessmentIndRegulatoryCode), not the other way around.

D. Create a lookup relationship on both objects to a junction object called Regulatory Code Map

This is incorrect as it involves creating a new custom object, which is unnecessary because a standard object already exists in the PSS data model for this specific purpose.

1. Salesforce Public Sector Solutions Developer Guide: The guide details the standard objects included in the solution. The AssessmentIndRegulatoryCode object is documented as the junction object linking AssessmentIndicatorDefinition and RegulatoryCode. (Refer to the "Public Sector Solutions Data Model" or "Object Model" section in the latest developer guide).

2. Salesforce Help - Public Sector Solutions Data Model: The official documentation outlines the key objects for Inspections Management. It specifies that AssessmentIndRegulatoryCode is the object used to associate an AssessmentIndicatorDefinition with a RegulatoryCode. (See documentation for "Set Up Inspection Management").

To effectively handle a resident's complaint and link it to a construction permit, a consultant should recommend a comprehensive process using standard Public Sector Solutions (PSS) features.

1. Log and Link the Complaint (C): The complaint should be captured as a Case record, which is the standard Salesforce object for tracking citizen issues and requests. This Case must then be linked to the relevant Permit Application record to formally "tie them back."

2. Enable Investigation (B): To investigate the complaint (e.g., verify debris), an on-site inspection is required. This necessitates configuring the Inspection Management objects, such as Visits and Assessment Indicators, to support field activities.

3. Standardize the Process (D): To ensure consistent handling, an Action Plan should be configured. This creates a repeatable template of tasks (e.g., schedule visit, conduct inspection, notify resident) that can be automatically launched from the Case or Permit, guiding the city staff through resolution.

A. Link Inspections and Visits to Permit Applications: This is an action taken during the process, not a foundational recommendation. The more critical recommendation is to first link the complaint itself (the Case) to the permit.

E. Set up Business Rules Engine (BRE) to determine Complaint validity: The Business Rules Engine is designed for complex eligibility, compliance, or fee calculations, which is overkill for validating a straightforward complaint about construction debris.

1. Salesforce Help, Public Sector Solutions Administrator Guide, Set Up Case Management for Public Sector Solutions: This guide details the use of the Case object for constituent service requests and complaints. It states, "With Case Management, your constituents can submit cases or service requests through a portal. Your caseworkers can then review the cases and take appropriate action." This supports using Cases for complaints (Option C).

2. Salesforce Help, Public Sector Solutions Administrator Guide, Set Up Inspection Management: This section explains the configuration of Visits and Inspections. It notes, "A visit is always associated with a parent record, such as a business license application or a case." This confirms the need to configure inspections (Option B) and shows they can be linked to either the permit or the case that represents the complaint.

3. Salesforce Help, Action Plans in Public Sector Solutions: This document describes the purpose of Action Plans. It states, "Use Action Plans in Public Sector Solutions to automate frequently recurring processes, such as reviewing permit applications or investigating cases." This directly supports using Action Plans to standardize the complaint handling process (Option D).

Public Sector Solutions provides a specific data model to handle this scenario. The PublicComplaint object is designed as the intake mechanism for constituents to report issues, service requests, or concerns via a public-facing portal, such as an Experience Cloud site. It supports submissions from both authenticated and anonymous (guest) users. Upon submission of a PublicComplaint record, a separate Case record can be automatically or manually created for internal staff to manage the investigation, follow-up, and resolution. This two-object approach perfectly aligns with the requirement to track the constituent's report and the internal investigation as separate records.

A. Use the Complaint Case and Case objects.

"Complaint Case" is not the correct name for the standard object provided by Public Sector Solutions for this purpose. The correct object is PublicComplaint.

B. Use record types on Case, one for the constituents and one for internal staff.

This approach uses a single object (Case) and does not meet the requirement to "separately track their investigations and any follow-up in a separate Case."

D. Use a custom object for the Complaint with a lookup relationship to Case.

While technically feasible, this approach ignores the standard, out-of-the-box functionality provided by the PublicComplaint object, which is specifically designed for this use case.

1. Salesforce Help, Public Sector Solutions, Manage Complaints and Service Requests: "Use the Public Complaint object to capture complaints and service requests from the public. When a complaint is submitted, a case is created for an agent to investigate and resolve." This documentation explicitly describes the intended use of the PublicComplaint object for intake and its relationship with the Case object for investigation.

2. Salesforce Developer Guide, Public Sector Solutions, Object Details, PublicComplaint: The developer documentation outlines the fields and purpose of the PublicComplaint object (API Name: PublicComplaint). It is described as an object to "Store information about a complaint or service request submitted by a person from the public." This confirms it is the correct standard object for the initial report.

3. Salesforce Help, Public Sector Solutions, Set Up Case Management for Public Sector Solutions: This guide details the configuration process, stating, "Public Sector Solutions uses the Case object to help you manage and track customer issues... You can also create cases from public complaints." This reinforces the intended workflow of creating a Case from a PublicComplaint.

An Integration Procedure is the most appropriate feature for this requirement. It is a declarative, server-side process designed to execute multiple actions in a single server call. It can orchestrate calls to different data sources, such as making an HTTP callout to an external system to fetch permit fees and simultaneously using a DataRaptor to retrieve discount information from a Salesforce custom object. It can then perform calculations on the aggregated data before returning the final fee amount. This aligns perfectly with the scenario's need for multi-source data retrieval and processing.

A. DataRaptor: A DataRaptor is used to retrieve, transform, or write Salesforce data. It cannot, by itself, make a callout to an external system to fetch data.

C. FlexCard: A FlexCard is a user interface component used to display contextual information and provide access to actions. It is not the tool used for the backend data orchestration and calculation logic.

D. OmniScript: An OmniScript provides a guided user path. While it can call an Integration Procedure or an HTTP action, its primary purpose is user interaction, not complex, server-side data aggregation from multiple systems. The Integration Procedure is the specialized tool for that backend logic.

1. Salesforce Help, OmniStudio Documentation, "Integration Procedures": "An Integration Procedure is a declarative, server-side process that executes multiple actions in a single server call. Integration Procedures can read and write data from Salesforce and from external systems (using REST API calls)... Use an Integration Procedure to access and transform data from third-party sources." This directly supports the use of an Integration Procedure to call an external system and process data.

2. Salesforce Help, OmniStudio Documentation, "DataRaptors": "DataRaptors are a configurable service for retrieving, transforming, and updating data." This documentation specifies their role is confined to data operations, primarily within Salesforce, and does not include orchestrating external API calls.

3. Salesforce Help, OmniStudio Documentation, "OmniStudio FlexCards": "FlexCards are cards that display contextual information and provide access to relevant tasks for a customer... They are the building blocks of the UI." This confirms FlexCards are a presentation-layer component.

4. Salesforce Trailhead, OmniStudio Architecture, "Choose the Right OmniStudio Tool": This module distinguishes the tools' purposes. It positions Integration Procedures for "bundling actions together to create a single, server-side service" and handling "data from multiple sources," while OmniScripts are for "creating a guided path for completing a business process." This architectural guidance confirms the Integration Procedure is the correct choice for the described data logic.

To deploy a digital experience for emergency response using Public Sector Solutions (PSS), several core configurations are required. First, the Emergency Response Management (ERM) for PSS Managed Package must be installed, as it contains the specific components, objects, and business logic for the emergency response use case. Second, Person Accounts must be enabled. PSS is built on a constituent-centric data model where Person Accounts are used to represent individual citizens, which is essential for managing requests and services. Third, Web-to-Case must be enabled to allow the public-facing digital experience forms to capture service and program requests from constituents and businesses and create Case records in Salesforce, which is a fundamental part of the solution's intake process.

C. Enable Email-to-Case: While a valid channel for case creation, it is not a direct prerequisite for configuring the PSS digital experience components, which primarily use web forms.

E. Install the ERM for PSS Unmanaged Package: Salesforce distributes the official ERM solution as a managed package to ensure support and upgradeability. An unmanaged package is incorrect.

1. Salesforce Help, Public Sector Solutions, "Install Emergency Response Management": This document outlines the installation process, stating, "Install the Emergency Response Management for Public Sector Solutions managed package from the Public Sector Solutions Installer." This directly supports option A.

2. Salesforce Help, Public Sector Solutions, "Prerequisites for Installing Public Sector Solutions": This guide explicitly lists enabling Person Accounts as a critical prerequisite. It states, "Before you install Public Sector Solutions, enable Person Accounts in your org." This supports option B.

3. Salesforce Help, Public Sector Solutions, "Set Up Emergency Response Management": In the post-installation steps, this guide details configuring the "Request for Assistance" functionality, which relies on web-based case submission. It instructs the administrator to, "Set up Web-to-Case to allow constituents to submit cases from your Experience Cloud site." This supports option D.

The most secure and scalable approach for this scenario involves two key steps. First, establish the most restrictive baseline security model by setting the External Organization-Wide Defaults (OWD) to 'Private' for all relevant objects (Case, Account, Grant Application). This ensures that, by default, external users cannot see any records they do not own. Second, use Sharing Sets to grant users access to specific records they need. Sharing Sets are designed for high-volume Experience Cloud sites to grant users access to records that are associated with their account or contact, which directly addresses the need for users to see their own cases and applications.

A. Set up Sharing Rules to grant authenticated users access to their Cases. Applications, and Accounts: Sharing Rules are not the optimal tool for this use case. They are designed to open up access based on record ownership or criteria, not a user's direct relationship to an account, and are less performant than Sharing Sets for large-scale external user access.

B. Set Org-Wide Defaults for External Users to Hidden for everything: "Hidden" is not a valid Organization-Wide Default setting in Salesforce. The most restrictive and appropriate setting is "Private."

1. Salesforce Help, "External Organization-Wide Defaults": "To secure your org, we recommend setting the default internal and external access to the most restrictive level—Private. You can then use other record-level security and sharing tools to grant access to users who need it." This supports setting the OWD to Private (Option D) as the foundational step.

2. Salesforce Help, "Control Access to Records Using Sharing Sets": "Sharing sets grant site users access to records that are associated with their accounts or contacts based on their user profiles... A sharing set grants access to any record associated with an account or contact that matches the user's account or contact." This directly supports using Sharing Sets (Option C) to provide the required record access.

3. Salesforce Architects, "Record-Level Security for External Users": This guide outlines the external sharing model, stating, "The external sharing model determines the baseline record access for external users... After you’ve set the org-wide defaults, you can use other record-level security features to grant access to external users. For partner and customer users, you can use sharing sets..." This confirms the two-step process of setting OWD to Private and then using Sharing Sets.

4. Public Sector Solutions Developer Guide, "Set Up Security and Sharing": While discussing the overall security model, the guide emphasizes leveraging the core platform's security features. It states, "Configure organization-wide sharing defaults to restrict access to records... For external users, such as constituents who log in to an Experience Cloud site, set the default external access to Private for all objects." This reinforces the use of Private External OWDs as a best practice within Public Sector Solutions.

The grantmaking lifecycle follows a logical and sequential process to ensure effective and transparent distribution of funds. The process begins with the Plan phase, where the grantmaker defines the funding program's goals, budget, and requirements. The subsequent Engage phase involves outreach to potential applicants and the intake of applications. After applications are submitted, the Award phase includes the review, scoring, and selection of grantees, culminating in the disbursement of funds. Finally, the Review phase covers post-award management, including monitoring grantee progress, collecting reports, and evaluating the overall impact of the grant.

A. Engage, Award, Plan, Review.

This is incorrect because planning must precede engaging with applicants; a program's framework must be established before it is opened to the public.

C. Review, Award, Engage, Plan

This order is reversed. Reviewing performance is a post-award activity, and planning is the foundational first step of the entire lifecycle.

1. Salesforce Help Documentation: "The Grantmaking Lifecycle". This document explicitly outlines the four key stages in the correct order: "Plan your funding programs and opportunities. Engage with your applicants. Award your grants. Review your grantee's performance."

2. Trailhead by Salesforce: "Grants Management for Grantmakers" module, "Explore the Grantmaking Process" unit. This unit details the grantmaking journey, starting with planning funding programs, then moving to engaging applicants, awarding grants, and finally managing the post-award process (review). This aligns directly with the Plan, Engage, Award, Review sequence.

Salesforce Public Sector Solutions (PSS) licensing often includes usage-based entitlements, particularly for transactions like license and permit applications submitted by external users. Configuring and deploying numerous OmniScript forms on an Experience Cloud site facilitates the submission of these applications by the public. Each submitted application can consume an entitlement. Therefore, enabling a high volume of application submissions through these forms directly drives the consumption of these entitlements, which in turn impacts the overall licensing cost for the organization. The cost is tied to the volume of transactions (applications processed), not the configuration of the forms themselves, but making them available is the direct enabler of that consumption.

B. The Application Object Usage Record is a mechanism for tracking consumption against purchased entitlements. Configuring this record is for monitoring purposes and does not, in itself, generate the cost.

C. Business Regulatory Authorization Type Dependencies are a standard configuration feature within the PSS data model to define prerequisites. This is core functionality and does not have a direct, separate licensing cost.

D. Record types are a standard Salesforce Platform feature used to manage different business processes. Creating record types on objects does not incur additional licensing costs.

1. Salesforce Help, Public Sector Solutions Documentation, "Track Your Public Sector Solutions Usage": This document explains the concept of usage-based entitlements in Public Sector Solutions. It states, "Public Sector Solutions uses usage-based entitlements on a number of objects... When your org exceeds a usage-based entitlement's allocated limit, you can't create records for that object." This confirms that creating application records (facilitated by OmniScript forms) is the activity that consumes entitlements and drives cost. The document specifically lists "Licenses and Permits Applications" as a tracked entitlement.

2. Salesforce Help, Public Sector Solutions Documentation, "Set Up an Experience Cloud Site for Constituents": This guide details how to use Experience Cloud sites to provide services to the public, including application submission. It outlines deploying OmniScripts and other components for external users, which is the primary channel for consuming application entitlements. The act of making these forms available for submission is the direct precursor to incurring usage-based costs.

3. Salesforce Help, Public Sector Solutions Developer Guide, "IndividualApplication": The documentation for the IndividualApplication object and related objects (like BusinessLicenseApplication) underpins the licensing and permitting data model. While the documentation itself doesn't specify pricing, it defines the objects whose record creation is tracked against the usage-based entitlements mentioned in the primary PSS documentation.

OmniScript is the recommended Salesforce Public Sector Solutions tool for creating guided, interactive experiences for constituents. It allows for the creation of a dynamic flow where a user can select their Business Type. Based on this selection, conditional logic within the OmniScript can display the specific set of associated permits and licenses required. This approach provides a user-friendly, step-by-step discovery process that can be seamlessly embedded into an Experience Cloud site, directly addressing the city's requirement to show constituents exactly what they need to apply for.

B: The Business Regulatory Authorization Type Dependency object is used to define prerequisites between two specific permits (e.g., Permit A is required before applying for Permit B), not to associate a collection of permits with a Business Type.

C: While technically feasible, creating a custom object and a FlexCard is a custom development approach. The recommended best practice is to leverage standard, out-of-the-box tools like OmniScript, which are purpose-built for guided interactions and require less custom effort.

D: This custom solution proposes using a standard list view, which provides a less intuitive and less guided user experience compared to the dynamic, interactive nature of an OmniScript.

1. Salesforce Help, Public Sector Solutions Developer Guide, OmniScript for Public Sector Solutions: "OmniScripts provide a guided path for completing a business process and are a perfect fit for public sector use cases... For example, you can create an OmniScript that guides a constituent through a permit application." This establishes OmniScript as the primary tool for guided user processes.

2. Salesforce Help, Public Sector Solutions Developer Guide, Public Sector Solutions Data Model: The documentation for the BusinessRegulatoryAuthTypeDependency object states its purpose is to "Define the dependency between two business regulatory authorization types." This confirms it is for permit-to-permit dependency, not for linking a set of permits to a business category.

3. Salesforce Help, Public Sector Solutions Administrator Guide, Set Up Guided Intake Flows with OmniScript: "Create guided intake flows with OmniScript to provide a simple, user-friendly experience for your constituents on your portal... Use the drag-and-drop editor to build the flow, and add elements for conditional questions, to show different pages based on a user's answers." This directly supports the use of OmniScript with conditional logic for this exact use case.

The Emergency Response Management (ERM) package for Public Sector Solutions provides a dedicated framework for managing volunteers. A key component is the volunteer portal, built on Experience Cloud, which allows volunteers to self-register for projects and shifts, and subsequently log the hours they have worked. The system is also designed to dynamically manage resource allocation. When a volunteer shift is canceled or a volunteer unregisters, the data model automatically updates the counts for 'registered volunteers' and 'volunteers needed' on the relevant shift records. This ensures that program managers have an accurate, real-time view of staffing levels and requirements.

A. Chatbot for volunteers: While a chatbot can be configured using Salesforce Einstein Bots, it is not an out-of-the-box feature included specifically within the ERM volunteer management package.

D. Volunteers can automatically claim reimbursements for the expenses: The standard ERM package focuses on volunteer registration, scheduling, and time tracking. It does not include a native, automated expense reimbursement feature, which would require custom development or integration.

1. Salesforce Help, Public Sector Solutions Documentation, "Manage Volunteers and Their Shifts in Emergency Response Management": This document explicitly states, "Volunteers can sign up for projects and shifts, and report the time they spend on volunteer activities." It also details the data model where Volunteer Shift records track Number of Volunteers Needed and Number of Registered Volunteers, which are updated as volunteers register or unregister, supporting the automatic update logic.

2. Salesforce Help, Public Sector Solutions Documentation, "Set Up a Volunteer Portal": This guide outlines the steps to create an Experience Cloud site for volunteers. It describes the functionality that allows users to "view and sign up for volunteer projects and shifts" and "submit the hours they've worked," directly confirming option C.

3. Salesforce Help, Public Sector Solutions Documentation, "Emergency Program Management Data Model": The data model for ERM includes objects like VolunteerProject, VolunteerShift, and VolunteerHours. The fields within the VolunteerShift object, such as DesiredNumberofVolunteersc and a rollup summary for registered volunteers, confirm the system's capability to track and update volunteer counts for shifts, as described in option B.

The core requirement is to implement a standardized, repeatable set of due diligence activities that can be tracked separately and run in parallel for each new organization (Account). The most appropriate feature for this is an Action Plan Template. A consultant would configure an Action Plan Template to define the specific tasks required for due diligence, such as "Verify Organization Details" and "Collect Statutory Documents." This template acts as a reusable blueprint. When a new organization registers, an Action Plan instance is created from this template, automatically generating the predefined tasks for that specific Account, ensuring a consistent and compliant process.

A. A Path targeted at Account: A Path is a visual tool for guiding users through the stages of a linear process. It does not create or manage a set of distinct, parallel tasks.

B. A Support Process targeted at Account: Support Processes are a feature of the Case object used to define different lifecycles for support tickets. They are not applicable to the Account object for due diligence.

C. An Action Plan targeted at Account: An Action Plan is the instance of the process created from a template for a specific record. The consultant's task is to configure the reusable blueprint, which is the Action Plan Template, not the individual instance.

1. Official Salesforce Documentation - Public Sector Solutions: Action Plans:

"Create action plan templates for tasks that your users must complete on a regular basis. For example, create a template for the tasks involved in an application review process for a business license or a grant program. When you create an action plan from a template, the tasks from the template are automatically added to the action plan."

Source: Salesforce Help, Public Sector Solutions Documentation, "Create Action Plan Templates". This explicitly states that the template is the configurable, reusable component for regular processes.

2. Official Salesforce Documentation - Public Sector Solutions: Set Up Action Plans:

"To get your users started with Action Plans, create action plan templates that are tailored to your business processes."

Source: Salesforce Help, Public Sector Solutions Documentation, "Set Up Action Plans". This confirms that the setup and configuration work performed by a consultant involves creating the templates.

3. Official Salesforce Documentation - Public Sector Solutions: How Action Plans Work:

"Action plan templates are the reusable framework from which users create action plans. In a template, you define the tasks and their deadlines."

Source: Salesforce Help, Public Sector Solutions Documentation, "How Action Plans Work". This reference clearly distinguishes the template (the configured framework) from the action plan (the instance). The consultant's configuration work is on the template.

OmniOut is the specific OmniStudio feature designed to deploy and host OmniStudio components, such as OmniScripts and FlexCards, on an external, non-Salesforce website. In this scenario, the agency can build the grant application form using an OmniScript, which provides a guided, step-by-step user experience. OmniOut then generates the necessary code to embed this OmniScript directly into the agency's existing public-facing portal. This allows constituents to complete and submit the application from the external site, with the data being seamlessly passed to Salesforce Public Sector Solutions objects using underlying DataRaptors or Integration Procedures. This approach directly meets the requirement without needing to build a custom API integration from scratch.

B. FlexCards: FlexCards are primarily used to display contextual information and launch actions, not to build complex, multi-step data entry forms like a grant application.

C. DataRaptor: DataRaptors are backend services for retrieving, transforming, and writing Salesforce data. While an OmniScript would use a DataRaptor to save the application data, DataRaptor itself does not provide the user interface or the mechanism to embed it on an external site.

D. Integration Procedure: An Integration Procedure can be exposed as a REST API endpoint. While the external portal could call this endpoint to submit data, it would require the agency to custom-build the entire application form and client-side logic on their portal. OmniOut provides a more complete, low-code solution by enabling the entire user interface to be embedded.

1. Salesforce Official Documentation, OmniStudio: "OmniOut for OmniScripts and FlexCards." The documentation states, "With OmniOut, you can run OmniScripts and FlexCards on any external web page... For example, run an OmniScript on a non-Salesforce domain to enable users to change their address without logging into your application." This directly aligns with embedding a grant application on an external government portal. (Accessed via Salesforce Help Portal, OmniStudio > OmniOut).

2. Salesforce Official Documentation, OmniStudio: "DataRaptors." The documentation defines DataRaptors as "a configurable service for retrieving, transforming, and updating data." This positions them as a data service layer, not a UI or external hosting solution. (Accessed via Salesforce Help Portal, OmniStudio > OmniStudio DataRaptors).

3. Salesforce Official Documentation, OmniStudio: "Integration Procedures." The documentation notes, "Expose Integration Procedures as REST APIs that can be called by third-party services." This confirms their role as a server-side integration point, distinct from OmniOut's function of embedding UI components externally. (Accessed via Salesforce Help Portal, OmniStudio > OmniStudio Integration Procedures).