AP-222 Questions and Answers

Salesforce directly documents Action Plans on Accounts as the mechanism for standardizing grantmaking due-diligence processes. An Action Plan Template acts as a reusable blueprint that defines the activities reviewers must complete consistently for each grantseeking organization.

Salesforce's Grants Management documentation explicitly states that organizations can use Action Plans on Accounts to define due diligence steps, related tasks, and documents to collect . Tasks can represent actions such as requesting tax documentation, verifying organizational eligibility, or completing financial reviews. Document Checklist Items identify supporting documents that must be obtained and reviewed.

This architecture directly addresses the problem in the scenario: reviewers currently follow different processes. A published Action Plan Template converts an informal procedure into a repeatable Salesforce-controlled workflow, improving consistency, traceability, accountability, and reviewer productivity.

A Screen Flow or OmniScript could technically guide a user through steps, but both would duplicate functionality already supplied by Action Plans. Merely supplying procedural documentation also provides no technical enforcement, assignment, due-date management, or document checklist tracking.

Therefore, Action Plans represent the product-native and lowest-customization implementation.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Due Diligence; Action Plans; Action Plan Templates; Tasks; Document Checklist Items.

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

Public Sector uses business accounts to represent businesses and Person Accounts to represent individual constituents . Salesforce explicitly states that Person Accounts should represent people applying for licenses, permits, programs, benefits, grants, and government services, while business accounts represent organizations or businesses.

Because the agency has explicitly selected a phased implementation—business constituents first and private constituents later—the appropriate implementation is to establish the Business Account and Contact model for the first release and introduce Person Accounts when the individual-constituent phase is implemented.

Salesforce supports enabling Person Accounts in an existing Public Sector organization. However, the decision requires appropriate planning because Salesforce warns that Person Accounts can't be turned off after they're enabled . Administrators should therefore evaluate and test the implications before activation.

Household Accounts aren't the standard constituent model for Public Sector license and permit applications. Person Accounts are specifically integrated with Individual Applications, Cases, public complaints, and Public Sector constituent experiences. Therefore, C and D use the wrong individual data model. Option A unnecessarily implements the second-phase architecture immediately despite the government's explicit phased rollout.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Public Sector data model; Business Accounts; Contacts; Person Accounts; phased implementation strategy.

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

Public Complaint and Case are the native Public Sector objects designed for this separation of external reporting from internal investigation. A Public Complaint records the concern submitted by a constituent, including health, safety, behavior, or well-being issues. Salesforce supports Public Complaint intake and subsequently allows staff to create a separate Case associated with the complaint when investigation or ongoing case management is required.

This architecture satisfies an important data-model requirement: the initial complaint and the internal investigative Case remain separate records but are related. Salesforce also provides the ComplaintCase junction object internally to associate complaints and Cases; this does not mean that "Complaint Case" is the principal constituent-facing object, making option D incorrect.

Using two Case record types would collapse two different Public Sector concepts into the generic Case object and discard purpose-built complaint functionality. Creating a custom complaint object would likewise duplicate capabilities already supplied by the Public Sector data model and increase maintenance.

The Public Complaint model also supports scenarios where a reporting party doesn't need to be treated as the subject of the investigative Case, which is particularly appropriate for anonymously submitted public concerns.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Public Complaints; ComplaintCase; Case Management; constituent complaint intake and investigations.

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

Intelligent Form Reader is the appropriate capability because it is specifically designed to extract structured information from uploaded documents through optical character recognition and then use that extracted information to create, update, or verify Salesforce record data. Salesforce documentation explicitly describes a validation scenario in which a person's birth date stored in Salesforce is compared against the birth date extracted from a scanned passport. This directly matches the requirement in the question.

For identity documents such as driver's licenses and passports, Intelligent Form Reader can use document types, extraction templates, field mappings, and Amazon Textract capabilities to identify values such as date of birth. The extracted field can then be mapped to the corresponding Salesforce field and used as part of an automated verification process.

Content, Attachments, and Files provide mechanisms for storing or associating documents, but none independently performs OCR-based extraction and validation of document data. They can participate in document storage, but they do not satisfy the stated automation requirement.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Intelligent Form Reader; document extraction, OCR, document types, field mappings, and identity-document verification.

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

The Public Sector Case Analytics App is specifically designed to analyze public-sector service cases and provides prebuilt dashboards and metrics for measuring organizational effectiveness, caseworker performance, service trends, and operational outcomes. This makes it preferable to creating a custom Salesforce reporting implementation.

More importantly, Salesforce documents exactly how the template handles case duration when an organization does not already maintain its own duration field. During Public Sector Case Analytics configuration, administrators can identify an existing duration field if one exists. If no case-duration field is tracked, CRM Analytics uses its own formula , calculating duration from the case opened and closed dates. For cases that remain open, the calculation uses the current date.

Consequently, Bobahaven does not need to introduce a custom duration field merely to obtain trend reporting. Options A and B add unnecessary data-model customization and would primarily benefit future records unless additional historical transformation were implemented. Option C similarly creates a custom reporting solution despite the presence of a purpose-built analytics template.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; CRM Analytics for Public Sector; Public Sector Case Analytics; case-duration metrics and prebuilt analytics dashboards.

CRM Analytics for Public Sector is the purpose-built analytics solution described by Salesforce for gaining intelligent operational insights from Public Sector data through preconfigured analytics applications and dashboards.

Salesforce specifically provides an Analytics for Licenses, Permits, and Inspections template. The application is designed to help licensing and permitting agencies evaluate departmental productivity and constituent satisfaction. Its prebuilt dashboards include Compliance Insights, Executive Summary, Department Summary, and Account Insights. These dashboards analyze Public Sector operational data without requiring the city to design a complete analytics model from scratch.

Standard Salesforce Reports and Dashboards can report on licensing records, but they don't provide the same purpose-built CRM Analytics data preparation and preconfigured analytical experience. Salesforce Einstein represents a broader AI capability rather than the specific analytics application requested.

Salesforce now also provides Tableau Next dashboards for Public Sector in supported editions, but the question specifically asks which listed product supplies the established prebuilt Public Sector analytics templates. Among the supplied answers, that remains CRM Analytics for Public Sector .

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Compliance Insights; Executive Summary; Department Summary.

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

For the managed-package OmniStudio architecture represented by this question, OmniStudio Tracking Service is specifically designed to capture user interactions and component-performance information so that consultants can identify inefficient steps in a business process.

Salesforce describes Tracking Service as an event-tracking service that records details of actions performed by users. A documented example is tracking how long users take to complete individual steps in an OmniScript specifically to identify process improvements . The service receives interaction events from OmniScripts, FlexCards, Integration Procedures, and other supported components and stores tracking details such as elapsed time, timestamps, event types, session information, and contextual data.

This makes it directly applicable after go-live: the consultant can determine where constituents or employees spend excessive time, abandon processes, encounter errors, or experience inefficient navigation.

Event Monitoring is a broader Salesforce security and activity-monitoring capability and does not provide the same OmniStudio process-level interaction analytics. Roll-up libraries and generic field tracking don't measure OmniScript process efficiency.

A release distinction is important: Salesforce's standard OmniStudio runtime doesn't implement the legacy Tracking Service , while OmniStudio for Managed Packages does. Salesforce currently provides OmniAnalytics and related analytics capabilities for modern OmniStudio environments. The question uses the managed-package-era feature terminology, for which A is correct.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – OmniStudio Tracking Service; OmniAnalytics; process optimization; user-interaction tracking.

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

Public Sector Inspection Management provides the native framework for investigating regulatory complaints through Visits, inspections, and Action Plans . Salesforce explains that agencies perform inspections both for license and permit applications and when members of the public report compliance concerns. Visit records identify the location, account, inspector, purpose, and regulatory context of an inspection.

The Visit can be created from a license or permit application and linked through its context to the applicable application, thereby preserving the connection between the investigation and the underlying construction authorization. Salesforce's current documentation explicitly supports creating Visits from application records and associating them with inspection types.

Action Plans provide the repeatable task framework used by inspectors. They contain assessment tasks, signatures, checklists, and other required inspection work so that investigators follow a standardized process. Salesforce also documents Action Plan usage for Public Complaint investigations.

Business Rules Engine is unnecessary merely to determine whether a complaint is valid, and directly linking generic Case records is not the core LPI complaint-and-inspection architecture.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Public Complaints; Visits; Permit Applications; Action Plans; regulatory compliance investigations.

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

Person Accounts must be enabled when the Public Sector implementation needs to represent individual constituents as applicants through the person-oriented Public Sector data model. The Individual Application object is designed to capture an individual's application for a government program, benefit, grant, license, permit, or similar service. The applicant therefore needs an appropriate person record with which the Individual Application can be associated.

Public Sector uses Person Accounts to represent constituents acting as individuals rather than organizations. A Person Account combines Account and Contact characteristics into a single person-centric record and integrates with Public Sector objects such as Individual Application, Case, and Public Complaint. This makes it the appropriate foundation for a grants program targeted at individual scholars.

Salesforce Flow is an automation technology and may participate in the implementation, but enabling Flow is not the prerequisite that establishes the individual-applicant data model. A custom Application object is unnecessary because Public Sector already provides Individual Application. Product Schedule is associated with product and revenue scheduling and has no functional relationship to grant applicants.

An important implementation consideration is that Person Accounts cannot simply be disabled after they are enabled , so agencies should validate their constituent data architecture before activation.

The uploaded Set 3 item likewise identifies Person Accounts as the required feature.

Study Guide Reference: Public Sector Solution Product Configuration – Person Accounts; Individual Applications; constituent data model; Grants Management for individual applicants.

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

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.

The appropriate relationship is PersonAccount → Individual ← Employee . Salesforce's Employee data model uses the Individual object as the common privacy and identity relationship point connecting employee information to other person-centric representations.

Salesforce documentation states that Employee records are related to Individual records and that an Individual connects employee data with privacy and consent information. The Work.com data-model documentation further explains that when another Salesforce solution represents a person through a Person Account, the Person Account can be linked to the Employee through the Individual record—specifically, PersonAccount > Individual <</b> Employee .

This arrangement is particularly appropriate when Public Sector represents an individual constituent as a Person Account while the Employee data model separately maintains an Employee record. The Individual object provides the linking layer rather than requiring the Person Account to connect directly to User or Employee.

Option B is a valid pattern for solutions that represent people through Contacts, but it does not satisfy the scenario's explicit Person Account requirement. Option D incorrectly routes the relationship through User, while option A does not even use the standard Employee object.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Public Sector person data model; Employee data model; Person Accounts; Individual; Employee relationships.

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