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

Explanation:

This question tests knowledge of the mandatory pre-installation checks required before installing the OmniStudio managed package in a Salesforce org. System administrators must prepare both the browser environment and specific org settings to avoid installation failures. Official Salesforce documentation outlines clear prerequisites covering browser compatibility, email deliverability, and enabling the Orders feature. These steps ensure the org meets technical and functional requirements for a successful first-time OmniStudio package installation.

✅ Correct Option:

B. Ensure the email deliverability access level is set to " All email "
OmniStudio relies on the EmailMessage object during installation testing. Setting Deliverability Access Level to “All email” in Setup allows the package to send and process emails correctly, preventing installation blocks related to email functionality.

D. Confirm browser settings meet published minimum requirements
OmniStudio requires the same browser standards as Salesforce (supported browsers, JavaScript enabled, minimum 4 GB RAM). Verifying these settings ensures the installation process and subsequent designer tools run without compatibility issues.

E. Enable Orders
The Orders feature must be enabled in Setup before installing OmniStudio. This setting activates required standard objects and functionality that the package depends on during installation and runtime.

❌ Incorrect options:

A. Enable Assets
Enabling Assets is not listed among the pre-installation requirements for the OmniStudio package. While Assets may be used in some industries solutions, it is not a mandatory check for package installation itself.

C. Enable Person Accounts
Person Accounts is an optional feature used in specific use cases (such as certain public-sector or financial processes). It is not required or mentioned in the official OmniStudio package preparation steps.

🔧 Reference:
→ Prepare to Install the Omnistudio Package – Confirms browser minimum requirements, Enable Orders, and Deliverability set to “All email” as required pre-install steps.

Explanation

The requirement is for a standardized checklist that inspectors complete during an onsite inspection.
In Public Sector, the Visit represents the actual onsite inspection activity.
An inspection action plan can contain assessment tasks that inspectors complete during the visit.
Assessment task definitions can expose regulatory-code requirements that inspectors must evaluate.
Signature tasks can also be added to capture signatures from the relevant participants.
Therefore, the template should be associated with the Visit rather than the Business License Application.

🟢 Correct Option

B. Action Plan Template with Type = "Visit Execution", Target Object = "Visit"
This configuration associates the inspection checklist directly with the Visit, which represents the onsite inspection. The template can contain assessment tasks for evaluating regulatory requirements and signature tasks for capturing required signatures. Salesforce documentation specifically describes creating inspection action plan templates with Visit as the target and adding assessment and signature tasks. This makes the Visit the appropriate record for executing the inspection activities described in the scenario.

🔴 Incorrect Options

A. Action Plan Template with Type = "Industries", Target Object = "Visit"
Although Visit is the appropriate target object, the template type is incorrect for this inspection scenario. Salesforce's inspection configuration uses an assessment/visit-execution action plan approach for inspection tasks. The generic Industries type does not represent the inspection execution configuration required for the checklist and signature activities.

C. Action Plan Template with Type = "Visit Execution", Target Object = "Business License Application"
The Business License Application provides the licensing context, but the requirement is to execute the inspection onsite. The inspection checklist and signatures need to be associated with the Visit that represents that onsite activity. Targeting the application therefore does not match the required Visit-based inspection execution model.

D. Action Plan Template with Type = "Industries", Target Object = "Business License Application"
This option uses both an unsuitable template type and the wrong target for the described onsite inspection. The application can be used to initiate or create a Visit, but the inspection activities, checklist, and signatures are executed through the Visit record. Therefore, this configuration does not satisfy the requirement.

Reference
⇒ Create Action Plan Templates for Inspection Visits in Public Sector — Salesforce confirms that inspection action plan templates use Visit as the target and support assessment and signature tasks.

⇒ Create an Action Plan Template for a Dynamic Assessment — Salesforce documents assessment execution templates and signature tasks for onsite Visit-based assessments.

Explanation:

This question tests the correct approach to digitizing emergency response operations using Agentforce Public Sector tools. The scenario requires a public-facing portal for citizens to submit simple emergency requests. The solution should minimize custom development by leveraging prebuilt Public Sector components specifically designed for emergency response use cases, including portal templates and request flows.

✔️ Correct Option:

A. Build a digital experience site using pre-configured emergency response management (ERM) specific template
Public Sector Solutions includes pre-configured Experience Cloud templates tailored to specific government journeys, including Emergency Response. Using this template provides ready-made components and layouts designed for constituent emergency submissions, eliminating the need to build portal infrastructure from scratch. This approach aligns with Salesforce's low-code strategy for public sector implementations.

B. Leverage prebuilt Emergency Service Request flow
Agentforce Public Sector provides out-of-the-box workflows and flows for emergency program delivery. An Emergency Service Request flow is purpose-built to capture essential information from citizens submitting emergency requests. Using this prebuilt flow reduces development effort, ensures consistency with Public Sector data models, and accelerates deployment.

❌ Incorrect Options:

C. Create a custom Case Record Type and leverage a prebuilt Contact Support Form
This approach relies on custom configuration (creating a new Case Record Type) rather than leveraging prebuilt Emergency Response components. While the Contact Support Form is a standard template, it is designed for general support requests, not emergency response scenarios. The requirement specifically calls for a simple emergency request mechanism, which the ERM template and Emergency Service Request flow address more directly.

D. Build a digital experience site using the Help Center template based on the agency's requirement
The Help Center template is designed for knowledge base and general customer support use cases, not emergency response. Building on this template would require significant customization to meet emergency-specific requirements. The pre-configured ERM template provides the appropriate starting point with components already aligned to emergency response needs.

🔧 Reference:
→ Emergency Response Management - Salesforce — Confirms that Salesforce provides Emergency Response Management solution with prebuilt capabilities for public sector agencies to manage constituent emergency requests.

→ Set Up Emergency Program Management Sites - Salesforce Help — Documents how to set up an Experience Builder site using the Emergency Response template to serve constituents during emergencies.

Explanation:

This question tests your knowledge of securing Salesforce Customer Community access in Public Sector Solutions. External security in Salesforce relies on a "least privilege" baseline established via Organization-Wide Defaults (OWD). Setting External OWD to "Private" ensures external users see zero records by default. To grant High-Volume Community users access to records linked to their contact or account (like Cases, Grants, and Applications) without exposing extra records, administrators use Sharing Sets. Sharing Sets map lookup/master-detail relationships on target objects directly to the logged-in user's contact or account record.

✅ Correct Option:

✅ B. Set up Sharing Sets to grant authenticated users access to their Cases, Applications, and Accounts:
Sharing Sets are designed specifically for High-Volume Community License users (Customer Community). They automatically grant access to related records—such as Cases, Accounts, Contacts, and Grant Applications—by matching user fields (like User.Contact.AccountId) to object lookup fields, granting efficient access without broad sharing overhead or risk of data leakage.

✅ C. Set Org-Wide Defaults for External Users to Private for everything:
Setting External Organization-Wide Defaults (OWD) to "Private" enforces strict data security by revoking implicit read access for all external portal users. This creates a baseline "zero access" architecture, ensuring authenticated users can only view records explicitly shared with them through targeted mechanisms like Sharing Sets.

❌ Incorrect options:

❌ A. Set up Sharing Rules to grant authenticated users access to their Cases, Applications, and Accounts:
Standard Sharing Rules rely on roles and public groups, which are not supported for high-volume Customer Community license types. Relying on sharing rules for customer community users leads to architectural failure, as individual roles are not assigned to basic community users.

❌ D. Set Org-Wide Defaults for External Users to Hidden for everything:
"Hidden" is not a valid Organization-Wide Default setting in Salesforce. The strictest available baseline visibility level for standard and custom objects in Salesforce external security settings is "Private."

🔧 Reference:
→ Salesforce Help: Configure Sharing Sets for External Users confirms using Sharing Sets alongside Private External Org-Wide Defaults to secure portal data access.

Explanation

This question tests knowledge of what the Volunteer Management capability in the Emergency Response Management package actually delivers. It centers on organizing volunteer projects and shifts, keeping staffing counts accurate, and tracking volunteer participation. Financial or conversational features are not part of it.

✅ A. Automatically update the number of registered volunteers and volunteers needed when shifts are canceled.
Emergency Response Management includes automation that keeps volunteer counts accurate as plans change. When a shift is canceled, the number of registered volunteers and the number of volunteers still needed are updated automatically. This helps coordinators see staffing gaps immediately, without manual recounting, so they can recruit replacements quickly during an active response and keep critical shifts properly covered at all times.

✅ C. Volunteers can sign up for volunteer projects and can report time spent on volunteer activities.
The package provides volunteer-facing functionality that supports the full volunteering cycle. Volunteers can sign up for volunteer projects and shifts that fit their availability, then report the time they spent on volunteer activities afterward. This gives the public sector entity a reliable record of participation and hours, which supports coordination, recognition, and reporting on the overall response effort and future planning.

❌ B. Volunteers can automatically claim reimbursements for the expenses.
Automatic expense reimbursement is not part of the Volunteer Management capabilities in the Emergency Response package. The feature focuses on organizing projects, shifts, volunteer registration, and time reporting. Reimbursement of expenses is a financial process handled outside this feature, so volunteers cannot claim costs automatically through it, which makes this option incorrect.

❌ D. Chatbot for volunteers.
A chatbot for volunteers is not a listed feature of Volunteer Management in this package. The capability centers on managing volunteer projects, shifts, sign-ups, and hours rather than conversational assistance. Although chatbots can be built separately with other Salesforce tools, they are not delivered as part of this package, so this option does not match.

🔧 Reference
🔗 Configure Volunteer Management – Salesforce Help → covers the Volunteer Management features available in Emergency Response Management.

Explanation:

This question tests knowledge of the standard component provided in Public Sector Solutions (Agentforce Public Sector) for displaying nested, multi-level related records on a Lightning record page. Customers often need to see connected data such as inspections (Visits), regulatory code violations, and enforcement actions directly on the Account page without navigating multiple related lists. The Hierarchical View component is designed exactly for this purpose and supports Account along with inspection-related objects.

✅ Correct Option:

C. Use a Hierarchical View component
The Hierarchical View is a Lightning Web Component that displays up to four levels of related records in a single unified, cascading view. It can be added to the Account Lightning record page and configured to show inspections (Visits), Regulatory Code Violations, and Violation Enforcement Actions, giving users complete context without switching tabs or pages.

❌ Incorrect options:

A. Use an AppExchange component
An AppExchange solution is not required. Salesforce provides a native Hierarchical View component specifically for this multi-level data display need in Public Sector Solutions.

B. Use an Aura Lightning component
Aura components are an older framework. The recommended and documented solution for hierarchical multi-level related data in Public Sector is the Hierarchical View Lightning Web Component, not a custom Aura component.

D. Use a Lightning Web component
While the Hierarchical View is itself a Lightning Web Component, the correct specific answer is the Hierarchical View component. Simply stating “a Lightning Web component” is too generic and does not identify the standard solution provided for this use case.

🔧 Reference:
→ Salesforce Help: Give Reviewers a Unified View of a Business or Applicant’s Records – Confirms the Hierarchical View component displays multi-level related records (including inspections, regulatory code violations, and enforcement actions) on Account and related pages.

Explanation

The requirement covers multiple areas: enhanced data protection, security monitoring, auditing, and compliance.
A single basic auditing feature cannot provide all these capabilities across the Salesforce implementation.
Salesforce Shield is an add-on suite designed specifically for enhanced security, compliance, and governance.
It includes Platform Encryption for protecting sensitive data at rest.
Event Monitoring provides detailed information about user activity, while Field Audit Trail supports long-term audit history.
Therefore, Salesforce Shield is the appropriate add-on for this compliance-focused use case.

🟢 Correct Option

C. Salesforce Shield
Salesforce Shield provides the combination of security and auditing capabilities required by the scenario. Its components include Shield Platform Encryption for protecting sensitive data at rest, Event Monitoring for detailed security and usage activity, and Field Audit Trail for extended data-change history. These capabilities support regulatory compliance, governance, and security monitoring across Salesforce. Because the agency needs enhanced protection and auditable controls rather than one isolated feature, Salesforce Shield is the appropriate add-on.

🔴 Incorrect Options

A. Setup Audit Trail
Setup Audit Trail records changes made to Salesforce configuration by administrators. It is useful for monitoring setup changes, but it does not provide the broader combination of encryption, event monitoring, and extended field auditing required here. Salesforce identifies Shield as the add-on for enhanced security, monitoring, and compliance capabilities.

B. Classic Encryption
Classic Encryption does not provide the comprehensive security and auditing capabilities described in the scenario. Salesforce Shield includes Platform Encryption, Event Monitoring, and Field Audit Trail, providing broader protection and compliance functionality. Therefore, Classic Encryption alone would not satisfy the agency's requirement for enhanced data protection and auditing.

D. Field History Tracking
Field History Tracking records changes to selected fields and provides basic auditing, but it does not provide encryption or detailed user activity monitoring. Salesforce Shield extends auditing through Field Audit Trail and adds Platform Encryption and Event Monitoring. Since the requirement spans security, data protection, and auditing, Field History Tracking alone is insufficient.

Reference
⇒ Salesforce Help — Salesforce Shield — Confirms that Shield provides Platform Encryption, Event Monitoring, Field Audit Trail, and Data Detect for enhanced security, compliance, and governance.

⇒ Salesforce Help — Protect Sensitive Data with Salesforce Shield — Confirms Shield's security, encryption, monitoring, and compliance capabilities for Public Sector implementations.

Explanation:

This question tests the key documentation deliverables a consultant typically produces during a Public Sector Solutions implementation. These documents serve different but complementary purposes: one captures requirements from the user's perspective, while the other formally specifies system behavior for development. Both are standard consulting artifacts in government technology projects.

✔️ Correct Option:

A. User Stories
User Stories are short, value-focused descriptions written from the end user's perspective, typically structured as "As a [role], I want [goal], so that [benefit]." In Salesforce implementations, user stories populate the product backlog and drive sprint planning. Consultants facilitate their creation during discovery workshops and backlog grooming sessions with stakeholders. They are essential for Agile delivery and ensure development aligns with constituent and agency needs.

D. Functional requirements specification (FRS)
An FRS is a formal document that details how the system should behave, including specific functional requirements, process flows, and system interactions. It complements user stories by providing the detailed "how" for complex implementations. In Public Sector Solutions projects, FRS documents help bridge the gap between business needs and technical configuration, supporting testing, UAT, and compliance verification.

❌ Incorrect Options:

B. Marketing Plan
A Marketing Plan is a business strategy document focused on promoting products or services, not a technical implementation deliverable. It is irrelevant to Salesforce Public Sector Solutions projects, which involve configuring government service delivery systems rather than marketing activities.

C. Budget Plan
A Budget Plan relates to financial planning and cost allocation for a project or program. While project budgets exist, they are not typically a "key document type" a consultant produces as an implementation deliverable in the same category as requirements specifications or user stories.

🔧 Reference:
→ Document requirements and storefront construction - Trailhead — Confirms that FSD (Functional Specification Document) and user stories are core documentation artifacts in Salesforce implementations.

Explanation:

This question tests the prebuilt Lightning components provided for Public Sector inspection visits. These components are added to a Visit Lightning record page so inspectors can quickly begin and end visits, review essential inspection information, and move between tasks, notes, and record details.

✔️ Correct Option:

✔️ A. Inspection Details
The Inspection Details Lightning component displays key fields from the Visit record, allowing an inspector to review essential information without navigating away from the inspection page. Depending on configuration, it can show the location name, scheduled time, person to visit, address, and inspection type. This gives the inspector immediate access to the operational details needed to prepare for and perform a restaurant compliance inspection efficiently.

✔️ D. Inspection Action
The built-in component is named Inspection Actions and provides the Start Visit and End Visit controls, along with the elapsed inspection time. It helps inspectors record the beginning and completion of an on-site compliance visit directly from the Visit record page. Capturing these actions and duration supports consistent inspection execution, improves field-work tracking, and helps the agency maintain an accurate record of the visit lifecycle.

✔️ E. Inspection Tab Container
The Inspection Tab Container component organizes inspection information into convenient tabs, including Tasks, Notes, and Details. It can also display a progress ring to show completion progress for the inspection. Inspectors can use the Tasks tab to complete checklists or assessments, the Notes tab to review or add visit notes, and the Details tab to view related visit and constituent information in one focused workspace.

❌ Incorrect Options:

❌ B. Inspection Dynamic Dashboards
Inspection Dynamic Dashboards is not one of the three built-in Lightning components provided for the Visit Lightning record page. Salesforce dashboards can be configured to present inspection metrics, compliance trends, workload, or violation data, but they are separate reporting features. They do not provide the operational visit-page capabilities for starting a visit, displaying visit details, and navigating inspection tasks and notes during field work.

❌ C. Inspection Calendar
Inspection Calendar is not a built-in Lightning component for conducting an inspection visit. Salesforce can associate visits with calendar events, allowing agencies to schedule inspections and check inspector availability. However, calendar scheduling is different from the Lightning components placed on a Visit record page. The required inspection-specific components are Inspection Details, Inspection Actions, and Inspection Tab Container.

🔧 Reference:
→ Customize the Visit Lightning Record Page
— Confirms that Public Sector provides the Inspection Actions, Inspection Details, and Inspection Tab Container Lightning components for efficient inspection visits.

→ Conduct an Inspection by Using the Desktop App
— Confirms that inspectors use Start Visit, Tasks, Notes, and Details while conducting an inspection.

Explanation

This question tests which Permission Set License gives constituents access to volunteer sign-up in a Public Sector digital experience. Volunteer capabilities are tied to a specific license, so the choice must match the volunteer-facing functionality rather than a general public sector or emergency license.

✅ C. Volunteer Management for Community.
Volunteer Management for Community is the Permission Set License designed for external users who take part in volunteer programs. Assigning it to a volunteer gives them access to the volunteer functionality in the digital experience, including signing up for volunteer projects. It fits the requirement because it is specific to community-facing volunteer activity, unlike broader public sector or emergency licenses.

❌ A. Community Response for Public Sector.
Community Response for Public Sector is not the license assigned to volunteers for sign-up. It relates to the broader community response solution used by the agency to organize projects and opportunities, not to individual volunteer access. Assigning it would not provide the volunteer-specific permissions needed for constituents to register for volunteer projects.

❌ B. Public Sector for Community.
Public Sector for Community is not the correct license for volunteer sign-up. It sounds like a general community license, but it does not target volunteer management functionality. Volunteers need the license tied specifically to volunteer activities, so a broad public sector option would leave them without the access required to sign up for projects.

❌ D. Emergency Response for Public Sector.
Emergency Response for Public Sector relates to emergency program management, such as incident coordination and response for the agency. It is not the license that lets volunteers sign up for projects. Although volunteers may support emergency efforts, their sign-up access comes from the volunteer-specific license, not from the emergency response option.

🔧 Reference
🔗 Experience Cloud Sites for Public Sector – Salesforce Help → confirms Public Sector Experience Cloud sites are where constituents engage with programs and services.