Free Salesforce-Accredited-Agentforce-360-for-Public-Sector-Professional Practice Test Questions (2026)

Explanation:

This question tests the recommended approach for providing constituents with digital license and permit application forms in Public Sector Solutions while minimizing customization and ongoing maintenance. Salesforce supplies a purpose-built Licenses and Permits Experience Cloud site template with preconfigured pages for applications, renewals, complaints, and inspection history. Using this dedicated template allows standard OmniScripts and FlexCards to be deployed efficiently without heavy modification of an existing Help Center site.

✅ Correct Option:

B. Create a new Applications digital experience using the Licenses and Permits Experience Site template, and deploy components such as OmniScripts and FlexCards to the new experience site.
The Licenses and Permits template includes ready-made pages (Apply for a License or Permit, Renew, My Applications, View Inspection History, etc.). Deploying OmniScripts and FlexCards onto this template leverages out-of-the-box structure, reducing custom development and long-term site maintenance compared with modifying the existing Help Center.

❌ Incorrect options:

A. Create OmniOut components and deploy them to the existing Help Center experience site.
OmniOut is intended for embedding Omnistudio components outside Salesforce experiences. Using it on the existing Help Center requires more customization and does not leverage the dedicated Licenses and Permits template, increasing maintenance.

C. Create new pages and deploy components such as OmniScripts and FlexCards within the existing Help Center experience site.
Adding new pages and components to the Help Center template forces significant customization of a site designed for service and knowledge. This increases maintenance effort compared with using the purpose-built Licenses and Permits template.

D. Create a new Applications digital experience using the Licenses and Permits Experience Site template, and deploy OmniOut components to the new experience site.
While creating a new site with the correct template is right, OmniOut is not the recommended method for deploying components inside an Experience Cloud site. Standard OmniScripts and FlexCards (or the provided Lightning web components) are the proper approach.

🔧 Reference:
→ Salesforce Help: Build a License and Permit Experience Cloud Site in Public Sector – Confirms use of the Licenses and Permits Experience Cloud site template with preconfigured pages and deployment of OmniScripts/FlexCards (or related components) for constituent applications.

Explanation

The requirement is to automatically determine the appropriate fee based on information entered for each license application.
Business Rules Engine uses decision matrices as lookup tables for matching input values to predefined outputs.
For licensing, these outputs can include application fee amounts based on authorization type or category.
An expression set can call the decision matrix and use its returned value in the fee calculation.
Workflow Field Updates and Process Builder aren't Business Rules Engine tools for this purpose.
Therefore, Decision Matrices are the appropriate tool for mapping and determining application fees.

🟢 Correct Option

C. Decision Matrices
Decision matrices are lookup tables within Business Rules Engine that match application inputs with corresponding output values. Salesforce specifically documents their use for automatically calculating application fees in Public Sector. For example, authorization category and type can be used as inputs, while the applicable base fee is returned as the output. An expression set can then use that result in the overall fee calculation. This directly matches the requirement to automatically map the correct fee to each application.

🔴 Incorrect Options

A. Workflow Field Updates
Workflow Field Updates are Salesforce automation functionality, but they aren't a Business Rules Engine tool for performing lookup-based fee determination. The scenario requires matching application information to predefined fee values. Salesforce specifically identifies decision matrices for this type of lookup and fee calculation in Public Sector.

B. Data matrices
Data matrices are not the Business Rules Engine tool described for this fee-mapping requirement. Salesforce Business Rules Engine uses decision matrices and expression sets to implement policy decisions and calculations. Decision matrices match input values to rows and return corresponding outputs, making them suitable for determining application fees.

D. Process Builder
Process Builder is not the appropriate Business Rules Engine tool for this requirement. The question specifically describes mapping application inputs to fee values through predefined rules. Salesforce documents decision matrices, together with expression sets, as the Business Rules Engine mechanism for automatically calculating application fees.

Reference
⇒ Salesforce Help — Automatically Calculate Application Fees — Confirms that Salesforce Business Rules Engine uses Decision Matrices to determine application fee amounts based on application inputs.

⇒ Salesforce Help — Business Rules Engine in Public Sector — Confirms that Business Rules Engine uses decision matrices and expression sets to automate policy decisions and calculations.

Explanation:

This question tests the correct data retention strategy when an agency has no universal requirement to keep grantee data after grant closure, but a specific grantee requires historical retention for legal proceedings. The solution must satisfy two competing needs: preserving data for legal purposes while ensuring the data is not actively used or processed in Salesforce. The correct approach removes the data from the active system while preserving it for the required legal hold.

✔️ Correct Option:

D. Export the grantee's data to retain it. Then, delete their data from Salesforce.
Exporting the data creates an offline archive that satisfies the legal retention requirement without keeping the data in an active processing environment. Deleting from Salesforce ensures the data is no longer used or processed by the system, directly addressing the request not to use/process historical data. This approach aligns with privacy principles of data minimization and storage limitation, where data is retained only as long as necessary and not actively processed. The exported archive can be maintained under legal hold protocols outside the CRM.

❌ Incorrect Options:

A. Assign the data to a specific public group and make those records inactive
Making records inactive does not prevent processing or use—users with access to that public group can still view and interact with the data. Inactive records remain in the system and are still subject to queries, reports, and potential processing. This approach fails to meet the requirement of not using or processing the historical data.

B. Export the grantee's data to retain it.
Exporting alone addresses the retention requirement but does not address the "not use/process" requirement. The data would remain in Salesforce and continue to be accessible and processable by the system. The question explicitly requires adherence to the request not to use or process the historical data, making this incomplete.

C. Keep the data in Salesforce and make it invisible to the users and system to restrict the processing of the data.
Making data "invisible" is not a supported Salesforce capability. While field-level security and record access can restrict user visibility, the system itself still processes the data for indexing, queries, and backups. There is no mechanism to make records completely invisible to the platform while keeping them in the org. This option is technically unfeasible.

🔧 Reference:
→ Salesforce Legacy Privacy Center: Satisfy Customer Requests and Data Privacy Laws — Documents retention policies and the "Right to be Forgotten" functionality, confirming that data can be archived or deleted to meet privacy requirements and limit processing.

Explanation:

The requirement is to show each approver an actionable, visual summary of open approval work immediately when they log in. The solution therefore needs CRM Analytics access for every team member, a dashboard rather than a single report, and a Lightning Home page assignment that targets the relevant Approver profile.

✔️ Correct Option:

✔️ D. Provide CRM Analytics licenses to all team members, create a custom Approvals dashboard using CRM Analytics for Public Sector and add this to a custom Home Page assigned to the Approver profile.
CRM Analytics for Public Sector provides dashboards that help agencies analyze operational work, including permits, grants, cases, and related approval activities. A custom Approvals dashboard can show each approver’s open applications and the elapsed time since an application entered the approval process. Every team member needs the appropriate CRM Analytics license to access the analytics content. Embedding the dashboard on a Lightning Home page assigned to the Approver profile ensures it appears when approvers sign in and open Salesforce.

❌ Incorrect Options:

❌ A. Create a custom Approvals dashboard using standard Salesforce Reports and Dashboards and add this to a custom Home Page assigned to the Approver profile.
This option correctly uses a dashboard and assigns the Home page through a profile, but it does not use CRM Analytics for Public Sector. The scenario asks for approval insights that include workload and pending-duration analysis for Public Sector processes. CRM Analytics provides the advanced analytics capability and interactive dashboard experience intended for these operational insights. Standard reports and dashboards are useful for basic reporting but are not the best-fit Public Sector analytics solution described here.

❌ B. Create a custom Approvals report using standard Salesforce Reports and Dashboards and add this to a custom Home Page assigned to the Approver role.
A report alone is less suitable than a dashboard for showing an at-a-glance summary of each approver’s pending work and elapsed approval time at login. More importantly, Lightning Home page assignments are based on the organization, an app, or an app-and-profile combination; they are not assigned directly by role. This option also omits CRM Analytics for Public Sector, which is the specified analytics solution for the required approval insights.

❌ C. Provide CRM Analytics licenses to all team members, create a custom Approvals report using CRM Analytics for Public Sector and add this to a custom Home Page assigned to the Approver role.
Providing CRM Analytics licenses is necessary, but this option has two design issues. First, the requirement calls for a visual, consolidated login-time summary, so a CRM Analytics dashboard is more appropriate than a report. Second, a Lightning Home page cannot be targeted directly to an Approver role. Salesforce supports Home page assignment by app and profile combinations, so the page should be assigned to the Approver profile.

🔧 Reference:
→ Salesforce Trailhead — Get Started with CRM Analytics
— Confirms that CRM Analytics for Public Sector uses dashboards to provide operational insights for public sector agencies.

→ Salesforce Help — Assign Custom Home Pages to Specific Apps and Profiles
— Confirms that Lightning Home pages are assigned by app and profile combinations, not directly by user role.

Explanation

This question tests how to choose the right analytics tool for trend reporting on a metric that was never tracked. Because case duration must be compared against historical performance, the solution should calculate it from existing case data using prebuilt capabilities, rather than depend on new fields that only capture future cases.

✅ D. Public Sector Case Analytics App, leveraging CRM Analytics' case duration formula.
The Public Sector Case Analytics app is a prebuilt CRM Analytics solution that already includes case duration calculations, so no new fields or custom logic are required. It works from existing case data, allowing executives to compare current resolution times with historical performance and follow trends over time. This delivers ongoing reporting with minimal customization, which is exactly what the scenario requires.

❌ A. Standard Salesforce Report using the standard Case report type, with a newly created custom field to track case duration for new cases.
A newly created custom field only records duration for cases created after it exists, so historical performance could not be compared. It also adds customization the scenario wants to minimize. A standard report can display the field, but the missing history and added build effort make this option unsuitable for trend analysis against past results.

❌ B. Public Sector Case Analytics App, with a newly created custom field to track case duration for new cases.
Although the Public Sector Case Analytics app is appropriate, adding a custom field to track duration for new cases is unnecessary customization. The app already provides case duration calculations, and a new field would capture only future cases, leaving historical comparison incomplete. The extra field adds effort without improving the trend reporting the executives need.

❌ C. Standard Salesforce Report using the standard Case report type, with a custom formula to calculate case duration.
A custom formula could calculate duration from existing case dates, but it still requires building and maintaining customization. Standard reports also offer limited trend visualization and ongoing analysis compared with a prebuilt analytics app. This makes it less suitable than a solution that already includes case duration metrics for executive trend reporting.

🔧 Reference
🔗 Case Metrics Questions, Public Sector Case Analytics Custom Wizard Step 4 of 6 – Salesforce Help → confirms the app includes a case duration calculation, with optional business hours support.

🔗 Set Up and Configure CRM Analytics – Salesforce Trailhead → confirms the Case Analytics dashboard shows case duration by status and case processing times.

Explanation

The question tests the data prerequisites for creating the Analytics for Licensing, Permits, and Inspections app.
Salesforce requires at least one record in one of several supported Public Sector objects.
The Visit object is one of the objects that can satisfy this requirement.
If the org has no records in any required object, app creation produces an error.
Therefore, the absence of Visit records can be the cause when the other required data is also absent.
The assigned permission sets alone do not guarantee successful app creation.

🟢 Correct Option

B. There are no Visit records.
Salesforce identifies Visit as one of the supported objects that can provide the minimum data required to create the Analytics for Licensing, Permits, and Inspections app. An org must have at least one record in at least one supported object, including Visit. Therefore, if the org lacks Visit records and also lacks records in the other qualifying objects, the app creation process can return an error despite users having the correct permission sets.

🔴 Incorrect Options

A. There are no Violation records.
Violation is not listed by Salesforce as one of the objects that can satisfy the minimum data requirement for creating this Analytics app. The documented qualifying objects include Business License Application, Individual Application, Public Complaint, Regulatory Transaction Fee, and Visit. Therefore, the absence of Violation records does not explain the documented creation error.

🔴 C. There are no active Action Plan Templates.
Salesforce's documented data requirement for creating the Analytics for Licensing, Permits, and Inspections app does not identify active Action Plan Templates as a prerequisite. The error is associated with having no records in any of the specified qualifying objects. Therefore, missing active Action Plan Templates is not the documented cause of this error.

🔴 D. Person Accounts have not been enabled.
Person Accounts are not identified in Salesforce's documented data requirements for creating this Analytics app. The requirement focuses on having at least one record in a supported object, such as Visit, Business License Application, Individual Application, Public Complaint, or Regulatory Transaction Fee. Therefore, enabling Person Accounts is not the prerequisite described for this error.

Reference
⇒ Data Requirements for License, Permit, and Inspections Analytics — Confirms that the org must have at least one record in a supported object, including Visit, to create the Analytics app.

Explanation:

This question tests the access model in Public Sector Solutions, where feature access is controlled through a combination of permission set licenses and permission sets. The scenario describes a single user who cannot access a feature that works for everyone else, which points to a user-specific assignment issue rather than an org-wide configuration problem.

✔️ Correct Option:

C. Action Plans Permission Set has not been assigned to the new inspector.
In Public Sector Solutions, users need both the appropriate permission set license and the corresponding permission set to use features like Action Plans . Since all other inspectors can access Action Plans, the org-level licensing is clearly provisioned. The new inspector is the only variable, and the most probable cause is that the required permission set was not assigned to their user record during onboarding.

❌ Incorrect Options:

A. Person Account Models have not been enabled on the org.
Person Accounts are an org-wide configuration setting. If this were the cause, no inspector would be able to access Action Plans, not just the new hire. The scenario specifically states that all other inspectors work without problems, ruling out org-wide settings.

B. The Salesforce user for the new inspector is disabled.
A disabled Salesforce user cannot log in to Salesforce at all. The question states the inspector "cannot access the Action Plans feature," implying they have some level of system access. If the user were disabled, the problem would be broader than just Action Plans.

D. The 'Enable Notes' permission has not been selected for the new inspector.
The "Enable Notes" permission controls access to the Notes feature, not Action Plans. These are separate features with separate permission requirements. Missing Notes access would not prevent a user from accessing Action Plans functionality.

🔧 Reference:
→ Salesforce Help: Set Up User Access Faster with New Standard Permission Sets — Confirms that Public Sector Solutions uses permission sets linked to permission set licenses to grant feature access.

→ Salesforce Help: View and Assign Permission Sets in Public Sector — Documents that users need both the appropriate permission set and permission set license, and that assigning the permission set automatically assigns the included license .

Explanation:

This question tests your knowledge of testing and simulation capabilities within the Business Rules Engine (BRE) in Public Sector Solutions. Expression Sets take inputs (such as application criteria, revenue, or project size), perform calculations or lookup evaluations against Decision Matrices, and return an output (such as calculated fee amounts). Built directly into the Expression Set Builder in BRE is a native Simulate tool. This allows business analysts and administrators to enter sample input variables and execute real-time test runs to verify logic, formulas, and fee calculations before activating and publishing the rule for live end users.

✅ Correct Option:

✅ C. By utilizing the expression sets in BRE module:
The Expression Set Builder inside the Business Rules Engine contains built-in simulation and testing functionality. Business users can quickly enter test payload parameters directly into the interface and run simulations to view step-by-step calculation results, verifying complex fee rules against multiple sample scenarios without writing code or deploying external test scripts.

❌ Incorrect options:

❌ A. By utilizing the integration procedures:
OmniStudio Integration Procedures execute back-end data processing and can call BRE components, but they do not provide business users with a simple, visual simulation environment for testing and verifying business decision rules independently.

❌ B. By utilizing the flows:
While Salesforce Flows can execute BRE rules via action elements, testing decision logic purely inside Flow Builder requires full flow debug runs and does not isolate or validate BRE calculation matrices and expression steps natively.

❌ D. By utilizing the combination of data raptors and integration procedures:
DataRaptors (Data Mappers) extract and transform data, while Integration Procedures handle orchestration. While they facilitate data transfer, they do not serve as the native tool for testing, simulating, and validating complex business policy calculations evaluated by the Business Rules Engine.

🔧 Reference:
→ Salesforce Help: Simulate an Expression Set in Business Rules Engine confirms using the built-in simulator in Expression Sets to test and verify sample inputs before live deployment.

Explanation:

This question tests collaboration capabilities in Salesforce Grants Management for Public Sector Solutions. The agency needs both external grantseeker stakeholders and internal government employees to participate in the same funding request application securely during submission and review, which requires the Funding Request collaboration feature.

✔️ Correct Option:

✔️ D. Configure Invite Collaborators for Funding Request Applications.
Funding Request Collaboration enables grantseekers to invite internal stakeholders to work together on an application through the grants portal. Invited collaborators receive a secure, time-limited invitation and, after accepting it, can help complete the Funding Request Application. The feature also supports government grant managers and other internal employees who need to collaborate during review. Salesforce shares the Funding Request and related records with authorized collaborators through a public group, providing controlled access while preserving application-level collaboration.

❌ Incorrect Options:

❌ A. Handle funding request collaboration through email and log activity on Applications.
Email can support informal communication, and logged activities can preserve a basic correspondence history. However, email does not provide secure, record-level collaboration on the Funding Request Application itself. It does not allow invited grantseeker stakeholders to enter the grants portal and jointly complete the application, nor does it automatically provide the controlled record sharing required for collaborators. The built-in collaboration feature is more secure, traceable, and appropriate for this requirement.

❌ B. Add a " Requires Collaboration " custom field to the Funding Request object.
A custom field can flag that a Funding Request requires collaboration, but it does not enable any collaboration behavior. It cannot invite stakeholders, create portal access, share the Funding Request with authorized users, or allow collaborators to edit the application. The agency needs a feature that grants controlled access and supports the collaborative application process. Invite Collaborators is the Grants Management capability that performs those functions.

❌ C. Collaborate internally and externally through the Funding Request Application Feed.
A record feed can support posts, comments, and updates where Chatter is enabled, but it does not provide the external collaborator-invitation workflow required for grantseekers’ internal stakeholders. It also does not automatically create the secure, time-limited invitation and related record sharing needed to let external collaborators participate in the grant application. Funding Request Collaboration is designed specifically to invite, authorize, and manage external application collaborators.

🔧 Reference:
→ Salesforce Help — Enable Funding Request Collaboration
— Confirms that Funding Request Collaboration lets applicants invite collaborators through the grants portal and shares the Funding Request and related records with authorized collaborators.

→ Salesforce Help — Add or Remove Funding Request Collaborators
— Confirms that users can use Manage Collaborators and Invite Collaborators to send secure, time-sensitive invitations for Funding Request applications.

Explanation:

This question tests the ability to choose a self-service Knowledge solution that reduces call center volume while minimizing implementation and maintenance costs for a public sector agency. The key constraints are: constituents must find answers before starting the application process, the solution must be public-facing, and the approach should be cost-effective to build and maintain. The correct answer balances accessibility with low administrative overhead.

✔️ Correct Option:

C. Implement Salesforce Knowledge, and publish articles to an unauthenticated Experience site page for constituents.
Salesforce Knowledge supports a Public Knowledge Base channel that makes articles available to unauthenticated guest users in Experience Cloud sites. This allows constituents to search and read permit and license guidance without logging in, directly addressing the self-service goal. Unauthenticated Experience sites require minimal configuration—no user license provisioning or complex authentication setup—making this the lowest-cost, lowest-maintenance option that still delivers public access.

❌ Incorrect Options:

A. Implement Salesforce Knowledge, and publish articles to the Bobahaven public website CMS via outbound API calls.
This requires custom integration work to push articles to an external CMS. Outbound API calls add development effort, ongoing maintenance, and potential sync failures. It solves the public accessibility requirement but increases implementation complexity and cost significantly compared to a native Experience site solution.

B. Implement Salesforce Knowledge, and publish articles to the Bobahaven public website via Lightning Out.
Lightning Out embeds Lightning components into external pages, but it requires custom development and careful authentication handling. For displaying Knowledge articles, this is unnecessarily complex. The added development and maintenance burden contradicts the requirement to reduce costs.

D. Implement Salesforce Knowledge, and publish articles to an authenticated Experience site page for constituents.
Authenticated access requires constituents to log in before viewing articles. This creates a barrier that discourages self-service, potentially increasing call center volume rather than reducing it. It also introduces user provisioning and authentication management overhead, raising both implementation and maintenance costs.

🔧 Reference:
→ Salesforce Help – No Articles Found in Experience Cloud Site Workspaces
Confirms that the Public Knowledge Base channel (IsVisibleInPkb) makes articles available in Experience Cloud Sites to unauthenticated users with the Guest User Profile.

→ Trailhead – Configure Article and Field Visibility
Documents that articles marked "Visible in Public Knowledge Base" are seen by readers without being authenticated, supporting self-service for public audiences.