Free Salesforce Accredited Agentforce 360 for Public Sector Professional Practice Test Questions

Explanation:

This scenario requires a server-side process that can simultaneously check an external system for permit fees and query a Salesforce custom object for address-based discounts in a single transaction. The question tests knowledge of which OmniStudio component orchestrates multiple data sources and server-side actions. Integration Procedures are designed exactly for this purpose: calling external APIs via HTTP actions while retrieving Salesforce data via Data Mapper actions, all in one server round trip.

✔️ Correct Option:

B. Integration Procedure.
An Integration Procedure is a declarative, server-side process that executes multiple actions in a single server call. It can simultaneously make an HTTP call to the external permit fee system and run a Data Mapper Extract against the custom object storing address-based discounts. This eliminates round trips and enables the combined fee calculation to be performed server-side before returning results to the user interface.

❌ Incorrect Options:

A. FlexCard.
FlexCards are UI components designed to display contextual information on record pages. While a FlexCard can use an Integration Procedure as its data source, it cannot itself orchestrate external API calls or complex multi-source data retrieval. It is a presentation layer, not a processing engine.

C. DataRaptor.
DataRaptors (now called Data Mappers) are specialized tools for reading, transforming, or writing Salesforce data. They handle specific data operations but cannot call external systems via HTTP or orchestrate multiple actions in a sequence. A DataRaptor alone cannot meet the dual requirement of external API call plus Salesforce query.

D. OmniScript.
OmniScripts are guided, step-by-step user interaction flows for collecting information and completing business processes. They are client-side guided experiences, not server-side data orchestration engines. While an OmniScript can call an Integration Procedure to perform backend work, the OmniScript itself is not the feature that handles external integrations and multi-source data retrieval.

🔧 Reference:
🔗 Get to Know Omnistudio Integration Procedures – Salesforce Trailhead → Confirms Integration Procedures handle multiple data sources (Salesforce and external) and execute multiple actions in a single server call.

🔗 Get Started with Integration Procedure Designer – Salesforce Trailhead → Confirms Integration Procedures are built with drag-and-drop elements to define server-side logic and data integration declaratively.

Explanation:

This question tests understanding of OmniStudio FlexCard use cases. FlexCards are declarative UI components that display contextual information and provide quick actions without custom code. The question asks for two valid use cases, requiring differentiation between FlexCards and other OmniStudio tools like OmniScripts.

✔️ Correct Options:

B. A widget to aggregate complex data models for quick-glance information.
FlexCards are designed to summarize contextual information at a glance and can display data from multiple sources simultaneously. They help solve data fragmentation by providing a unified view of customer information from Salesforce objects, external APIs, and legacy systems. This makes them ideal for aggregating complex data models into a single, scannable card.

D. A homepage widget to quickly launch common processes.
FlexCards serve as the beginning and ending points for customer transactions and provide access to relevant tasks for displayed data. They can include action buttons that launch OmniScripts, Integration Procedures, or other processes directly from the card. This makes them effective as homepage widgets for initiating common workflows.

❌ Incorrect Options:

A. A widget to ask multiple pages of questions in the application form.
This describes an OmniScript, not a FlexCard. OmniScripts are guided, multi-step processes for collecting information and completing business processes, while FlexCards are primarily for displaying contextual information and quick actions.

C. A widget to perform in-line edits and calculations within a table quickly.
FlexCards display data but are not designed for complex in-line editing or calculations within tables. While they can include input elements, their primary purpose is information display and action launching, not spreadsheet-like editing functionality.

🔧 Reference:
🔗 Discover the Key Capabilities of Flexcards – Salesforce Trailhead → Confirms FlexCards summarize contextual information at a glance, display data from multiple sources, and serve as launching points for customer transactions.

🔗 Get to Know Omnistudio Flexcards – Salesforce Trailhead → Confirms FlexCards help with scattered customer data by combining data from multiple sources and displaying contextual actionable information with buttons that trigger processes.

Explanation

This question tests the lifecycle and modification rules for Action Plan templates in Public Sector.
An Action Plan template defines the tasks and steps used to guide an inspection or other business process.
After an Action Plan template is published, its definition becomes locked and cannot be edited directly.
This behavior prevents changes to an active template from unexpectedly affecting existing action plans.
Therefore, the missing Edit button is expected behavior rather than a page-layout or permission issue.
To make changes, the appropriate approach is to create or use a new template version.

🟢 D. Once published, an Action Plan template cannot be changed.
Published Action Plan templates are locked from direct modification. Salesforce prevents changes to the template after publication because the template may already be used to generate Action Plans for inspections and other processes. This protects the consistency of existing records and prevents changes to an active template from unexpectedly altering the tasks or steps associated with previously created Action Plans. Therefore, the absence of the Edit action after publication is expected behavior rather than a permission problem.

🔴 A. Edit option needs to be added to Action Plan template page layout
The Edit action is not missing because it needs to be added to the page layout. The restriction is related to the lifecycle state of the Action Plan template. Once the template is published, Salesforce prevents direct editing, so adding an Edit action to the layout would not resolve the issue.

🔴 B. Action Plan template changes have to be requested to Salesforce support team
Published Action Plan templates do not require a Salesforce Support request simply because they cannot be edited. The limitation is part of the standard template behavior. Administrators should manage the template through the supported configuration process rather than requesting Salesforce Support to modify a published template.

🔴 C. System Administrator doesn ' t have " Edit " permissions to Action Plan template
The missing Edit action is not caused by the System Administrator lacking object permissions. The key restriction is that the Action Plan template has already been published. Salesforce locks published templates from modification, so granting additional Edit permissions would not make the Edit action available for that published template.

Reference
⇒ Salesforce Help — Action Plan Templates — Explains the Action Plan template lifecycle and the restrictions that apply after a template is published.

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

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

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 .