Pass the Salesforce Accredited Professional Certification AP-222 Questions and answers with CertsForce

Decision Matrices are the appropriate Business Rules Engine component when a licensing process must map a combination of defined inputs to a corresponding result such as an application fee. Salesforce defines a Decision Matrix as a lookup table containing user-defined input and output columns. At runtime, the matrix evaluates supplied input values, finds the matching row, and returns the configured output.

For a sporting-event licensing process, the inputs can represent attributes such as license type, event classification, location, capacity, duration, or other fee-determining criteria. The output column can contain the applicable fee. An Expression Set or OmniStudio process can invoke the matrix during application processing and use the returned amount to populate or calculate the application ' s fee. This design keeps regulatory fee schedules outside procedural automation. When the government agency changes a fee or threshold, administrators can update the Decision Matrix rather than modifying Flow, Process Builder, or custom code. Workflow Field Updates and Process Builder are general automation mechanisms and do not provide the structured multi-input lookup model that Business Rules Engine provides.

Study Guide References: Business Rules Engine; Decision Matrices; Licensing Fee Configuration; Expression Sets; Declarative Regulatory Calculations.

Access to Action Plans requires the appropriate Action Plans permission set. Salesforce ' s Public Sector configuration documentation explicitly lists the Action Plans permission set as required for users who set up or use Action Plans.

The same requirement applies to Dynamic Assessments. Salesforce identifies Action Plans among the permission sets that must be assigned to users who conduct dynamic assessments, alongside Dynamic Assessment Access, Industries Assessment, OmniStudio User, and use-case-specific permissions such as Public Sector Access and Industries Visit. The scenario strongly indicates a user-specific access issue: existing inspectors can use Action Plans, while the newly onboarded inspector cannot. That makes an org-wide configuration problem such as Person Accounts highly unlikely. The appropriate troubleshooting step is therefore to compare the new inspector ' s permission-set assignments with those of a functioning inspector. The Enable Notes setting is unrelated to Action Plan feature entitlement. A disabled Salesforce user would prevent the user from accessing Salesforce altogether rather than selectively blocking only the Action Plans feature. Assigning the Action Plans permission set grants the required feature access, after which object-level and field-level permissions should also be validated for the objects used in the inspector ' s process.

Study Guide References: Action Plans; Action Plans Permission Set; Dynamic Assessment Access; Inspector Permissions; Public Sector User Access Configuration.

Decision Explainer provides the explainability framework required to expose how Business Rules Engine calculations and determinations were reached. After a prioritization Expression Set and its supporting Decision Matrix have been configured, the rule must be integrated with Decision Explainer so that execution metadata and decision details are captured. Salesforce specifically states that integrating Business Rules Engine with Decision Explainer makes business rules available so Public Sector reviewers can access decision logs.

The Decision Explainer Log History component must then be added to the appropriate application Lightning record pages. This component displays each decision ' s timestamp, Expression Set name, and version, and allows reviewers to inspect variables, values, and formulas that contributed to the determination. Finally, reviewers require the appropriate Decision Explainer access. Salesforce identifies Decision Explainer Service Access as the permission needed to use Decision Explainer entities. A custom Screen Flow or Apex trigger is unnecessary because the platform already provides native logging, explainability entities, and the Lightning component.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Decision Explainer; Decision Explainer Log History; Public Sector User Access.

An Action Plan Template targeted at Account is the appropriate configuration because Grants Management due diligence is performed against the grantseeking organization represented by the Account record. Salesforce explicitly recommends using Action Plans on Accounts to define due-diligence steps, required tasks, and documentation that must be collected and verified.

The Action Plan Template acts as the reusable blueprint. It can include Tasks for activities such as validating organization details and Document Checklist Items for collecting statutory or financial documentation. When the template is published, grant managers can instantiate separate Action Plans against an Account, allowing multiple due-diligence processes to proceed in parallel while retaining their own tasks, ownership, deadlines, and verification records. Salesforce specifically supports Account as the target object when creating Grants Management due-diligence Action Plan Templates. An individual Action Plan is an execution instance rather than the reusable configuration requested in the scenario. Path is designed to guide records through stages, and Support Processes control Case status values; neither provides the structured task-and-document framework required for organizational due diligence.

Study Guide References: Grants Management; Due Diligence; Action Plan Templates; Accounts; Tasks; Document Checklist Items; Verification Checks.

Public Sector provides a standard Business Regulatory Authorization Type Dependency model specifically for representing prerequisite and dependent licenses or permits. The administrator defines the first required authorization as the Parent Business Regulatory Authorization Type and the subsequent authorization as the Dependent Business Regulatory Authorization Type.

This configuration allows the agency to model relationships such as a business license that must be obtained before a fire permit, operating permit, or other dependent authorization. The standard data model should be used instead of recreating dependency logic with custom objects or hard-coded OmniScript conditions. Salesforce also provides the Permit component for displaying permits associated with a particular business type. In the Licenses and Permits Experience Cloud experience, constituents can view the licenses and permits required for their business type together with dependency information. This approach minimizes custom development and ensures that changes to permit dependencies are maintained declaratively in regulatory configuration data rather than embedded in presentation logic. It also keeps the Experience Cloud implementation aligned with the standard Public Sector regulatory data model.

Study Guide References: Business Regulatory Authorization Type; Authorization Dependencies; Business Types; Permit Requirements; Licenses and Permits Experience Cloud.

Administrator users responsible for creating and managing Public Sector analytics require both the CRM Analytics platform-level administrator capability and the Public Sector-specific analytics administrator capability.

CRM Analytics Plus Admin supplies the permissions required to administer CRM Analytics, including creation and management of templated analytics applications. Salesforce describes this prebuilt permission set as providing the administrative permissions for CRM Analytics Plus and associated application-management functionality. The administrator must also receive the Public Sector analytics administrator permission set represented in the options by CRMA for Public Sector Admin. Current Salesforce documentation identifies this Public Sector-specific administrative permission as TCRM for Public Sector Admin. Salesforce ' s setup procedure explicitly instructs administrators to assign CRM Analytics Plus Admin AND TCRM for Public Sector Admin to users who create and manage Public Sector analytics applications. The combination separates platform administration from industry-template access. CRM Analytics Plus Admin alone does not provide the full Public Sector-specific entitlement required by the LPI application, while the industry permission alone does not supply the necessary CRM Analytics platform administration rights.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Admin Permissions; CRM Analytics Plus Admin; Public Sector Analytics Admin.

Dynamic Assessments use categories to organize Assessment Questions so that different subsets of questions can participate in conditional assessment paths. This directly supports the restaurant scenario, where specific questions need to apply to take-away businesses, dining establishments, or businesses operating under both models.

Salesforce ' s Dynamic Assessments setup sequence explicitly directs administrators to create categories for similar types of assessment questions, create the assessment questions themselves, and then add those questions to Omni Assessment Tasks. The resulting form is used in an OmniScript, where conditional logic controls which questions are shown for a particular assessment scenario. The distinction between the objects is important. An Assessment Task Definition or Omni Assessment Task represents a broader group of questions or work to be performed. An Action Plan organizes the overall repeatable inspection workflow. Assessment Indicator Definitions are used heavily in regulatory inspection assessment models, but they are not the object on which this Dynamic Assessment question categorization is being configured. By categorizing the individual Assessment Question records, the agency can reuse a broader assessment while selectively presenting only the questions relevant to the type of food outlet being inspected.

Study Guide References: Dynamic Assessments; Assessment Questions; Question Categories; Omni Assessment Tasks; OmniScripts; Conditional Assessment Logic.

The standard Hierarchical View component is specifically designed to display multi-level related Public Sector records in a single structured view. Salesforce describes Hierarchical View as a Lightning web component that presents cascading relationships and allows users to avoid repeatedly navigating through individual related lists and record tabs. It can display up to four levels of related records.

For an Account, Salesforce provides a directly relevant configuration pattern. The first level can display Business License Applications, the second level associated Visits, the third level Regulatory Code Violations, and the fourth level Violation Enforcement Actions. This precisely matches a scenario in which reviewers want to start from an Account and understand its inspection and compliance history. The component supports standard Public Sector objects including Account, Visit, Inspection Assessment Indicator, Regulatory Code Violation, Violation Enforcement Action, and several other regulatory objects. It can therefore provide the requested multi-level visibility without requiring a custom UI component. Although Hierarchical View is technically implemented as a Lightning web component, the appropriate configuration choice is the named Hierarchical View component, because Salesforce supplies and supports it specifically for this use case. Building a generic custom LWC, Aura component, or installing an AppExchange component would add unnecessary development and maintenance.

Study Guide References: Hierarchical View; Account Unified View; Visits; Regulatory Code Violations; Enforcement Actions; Public Sector Record Relationships.

Business Rules Engine separates reusable lookup logic from procedural rule execution. Decision Matrices contain business-rule lookup tables with defined input and output columns. When supplied with input values, the matrix searches for the applicable row and returns its configured output. Salesforce describes Decision Matrices as useful for implementing complex rules in a systematic and readable manner.

Expression Sets orchestrate more sophisticated decision logic. They can execute calculations, conditional branches, aggregations, constants, variables, and matrix lookups. An Expression Set can therefore call a Decision Matrix at the appropriate point in a licensing or eligibility process and use the returned value in subsequent calculations or decisions. Salesforce specifically documents Expression Sets calling Decision Matrices and consuming the output corresponding to the matching matrix row. This architecture allows policy data and procedural calculations to be maintained independently. For example, a licensing fee table can be maintained in a Decision Matrix while an Expression Set calculates intermediate values, invokes the matrix, and produces the final fee. The other options reverse these functions or mischaracterize the data interface. Decision Matrices do not perform the broader sequence of calculations attributed to Expression Sets.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Licensing Business Rules; Declarative Decision Automation.

Public Sector provides a dedicated Public Complaint object for recording concerns submitted by constituents and a separate Case object for managing the organization ' s investigation and response. This separation aligns directly with the requirement to distinguish external complaint intake from internal casework.

Salesforce ' s complaint-management architecture uses the Public Complaint record to capture the reported incident, reporter information, and associated supporting details. Public Sector can then create a separate Case related to that complaint so case managers can prioritize the matter, assign caseworkers, investigate the concern, and track follow-up activity. Salesforce ' s investigative case-management documentation also identifies the Public Complaint as the intake record created when a constituent submits a concern and supports subsequent case creation and proceedings based on that complaint. Using Case record types for both external intake and internal investigation would collapse two distinct business concepts into one object. A custom complaint object is unnecessary because Public Sector already provides the appropriate standard industry object and its relationships.

Study Guide References: Complaints Management; Public Complaint; Investigative Case Management; Case; Experience Cloud Complaint Intake; Constituent Reporting.