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

An approval process is the correct architecture because the requirement combines conditional approval routing with an auditable approval history. Salesforce approval processes define the criteria under which a record enters approval, specify the approval steps, identify the appropriate approvers, and preserve the state of the approval request.

The consultant can use the application's age or duration as the entry or step criterion and route qualifying records to the appropriate manager. Salesforce's approval framework tracks states such as Submitted, Pending, Approved, Rejected, Reassigned, and Recalled. The Approval History related list provides users with visibility into the record's progress and creates the audit trail required by the scenario.

A Flow that merely changes ownership doesn't constitute manager approval and doesn't inherently provide the same approval-process audit model. Chatter is a collaboration mechanism rather than a controlled regulatory approval system. An "approval escalation rule" isn't the correct Salesforce automation construct for this requirement.

Salesforce now recommends Flow Approval Processes as the modern successor for many new implementations, providing dynamic routing and detailed compliance logging; however, among the supplied answer choices, C precisely describes the required approval-process pattern.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – application approvals; approval criteria; manager routing; Approval History; regulatory auditability.

Scope, schedule, and cost constitute the classic project-management triple constraint and are the correct considerations for an Agentforce Public Sector implementation. Salesforce Trailhead explicitly identifies scope, schedule, and cost as the three interconnected project constraints. A modification to one dimension generally affects at least one of the others.

Scope defines what capabilities and requirements the implementation must deliver—for example, licensing, permitting, grants management, constituent portals, or integrations. Schedule defines when those deliverables must be completed, including statutory deadlines, procurement milestones, fiscal-year constraints, or mandated program launch dates. Cost represents the approved implementation budget, including Salesforce products, implementation resources, integration work, testing, migration, training, and operational readiness.

For a public-sector implementation, these constraints require particularly disciplined governance because agencies commonly operate under fixed budgets and formally approved scopes while also facing regulatory or legislative deadlines. Expanding scope without changing schedule usually requires additional cost or resources. Conversely, reducing the budget may require scope reduction or schedule extension.

Resources certainly affect project execution, but they are not part of the standard three-way constraint identified by Salesforce project-management guidance. Workshops and tools are implementation mechanisms rather than primary project constraints.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – implementation planning; project governance; scope management; schedule management; budget/cost management.

================

The Hierarchical View component is the standard Public Sector feature designed for precisely this requirement. Salesforce states that Hierarchical View provides users with a unified visualization of related records across up to four levels of a relationship hierarchy, eliminating the need to navigate multiple related lists and individual records.

The component supports Account as well as numerous Public Sector objects relevant to this scenario, including Visit, Inspection Assessment Indicator, Regulatory Code Violation, Violation Enforcement Action, Business License Application, Public Complaint, Regulatory Transaction Fee , and other related records. Salesforce gives a closely aligned example in which reviewers need to understand records associated with a business license application: an application leads to an inspection visit, the inspection can identify regulatory-code violations, and violations can result in enforcement actions and regulatory transaction fees. Hierarchical View presents those relationships as a connected structure rather than disconnected lists.

Custom Aura or Lightning Web Components could reproduce this functionality, but doing so would introduce unnecessary development and maintenance when Public Sector already supplies the purpose-built component. An AppExchange component creates the same unnecessary dependency.

Therefore, the lowest-customization and product-native solution is Hierarchical View .

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Hierarchical View; unified record visualization; Accounts; Visits; regulatory violations and enforcement records.

================

Salesforce requires users who configure or use Action Plans to have the appropriate Action Plans permission set . Salesforce's Public Sector Action Plans documentation explicitly identifies the required user permission as the Action Plans permission set and directs administrators to assign it through the user's Permission Set Assignments.

The scenario isolates the problem to one newly onboarded inspector while every existing inspector can access the same feature. That strongly indicates a user-specific permission assignment rather than an organization-wide configuration problem. If Person Accounts weren't enabled and were genuinely required, the impact would affect the implementation generally rather than only one inspector.

Likewise, "Enable Notes" isn't the feature permission controlling Action Plans. Action Plans have dedicated access requirements covering objects such as Action Plan, Action Plan Template, Document Checklist Item, and Recurrence Schedule, together with the Action Plans feature permission where appropriate.

A completely disabled Salesforce user would be unable to log in to Salesforce at all, not merely unable to access Action Plans. The wording indicates the inspector is successfully using Salesforce but lacks access to this particular capability.

Therefore, checking and assigning the Action Plans permission set is the precise troubleshooting action.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; user access; Action Plans Permission Set; inspection-user configuration.

================

An Integration Procedure is the correct orchestration component because this requirement combines information from different data sources: an external fee system and Salesforce custom-object data. OmniStudio Integration Procedures are declarative server-side processes designed to execute multiple data operations within a single server call.

Salesforce specifically states that Integration Procedures can retrieve, transform, and send information between Salesforce and external systems, invoke REST APIs, perform conditional processing, and combine information from multiple sources into a single response.

That architecture maps directly to this scenario. The Integration Procedure can retrieve the base permit fee from the external system, retrieve site or address information and applicable discount information from Salesforce, apply the required transformations or calculations, and return the resulting fee to the calling application process.

A Data Mapper is more suitable for straightforward Salesforce object reads, writes, and transformations. It is not the preferred component when multiple heterogeneous data sources and external REST services are involved. A FlexCard primarily presents information and actions to users. An OmniScript manages the interactive guided process, but it would normally invoke an Integration Procedure to execute this server-side integration.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; external data access; REST integration; multi-source orchestration; license and permit fee processing.

================