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

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.

This requirement calls for three cooperating layers: a guided application form to capture applicant information, a structured lookup model for eligibility criteria, and executable rule logic to evaluate and prioritize each application. Those capabilities are provided by OmniScript, Decision Matrix, and Expression Set .

Salesforce identifies Decision Matrices and Expression Sets as the two core elements of Business Rules Engine. A Decision Matrix stores policy criteria as structured input and output values, while an Expression Set executes calculations, invokes matrix lookups, and returns the resulting decision. Salesforce specifically states that BRE can determine whether applicants qualify for government programs, small-business loans, licenses, and other public-sector services.

The application front end should be created with OmniScript Designer . Salesforce documents the same architecture for eligibility-driven Public Sector workflows: an OmniScript captures applicant inputs, an Expression Set evaluates those values, and a Decision Matrix contains the eligibility thresholds or criteria.

Web-to-Lead creates Lead records and isn't a grant eligibility framework. Web-to-Case creates Cases and likewise doesn't provide structured application assessment or prioritization logic.

This combination gives the agency a maintainable, policy-driven system in which eligibility rules can change without rebuilding the constituent application.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScript Application Forms; Business Rules Engine; Decision Matrices; Expression Sets; automated eligibility and prioritization.

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

The inspection checklist belongs to the actual onsite Visit , not directly to the Business License Application. Consequently, the Action Plan Template must target the Visit object. In the terminology used by this exam item, the inspection-oriented template type is Visit Execution , making B the correct selection.

The underlying Salesforce design is explicit. An inspection Action Plan Template groups assessment tasks and additional visit activities, such as signature capture, into a repeatable inspection process. Salesforce documents that the target object for an inspection Action Plan Template is Visit . Assessment Task Definitions provide the regulatory-compliance checklist, while Signature Tasks allow signatures to be collected during the visit.

A terminology update is important for current implementations: current Salesforce documentation uses Assessment Execution as the Action Plan Type for Public Sector inspection templates rather than the older Visit Execution terminology appearing in this question. The architectural answer remains unchanged—an inspection template is associated with the Visit .

Targeting Business License Application would incorrectly attach the execution checklist to the application rather than the physical inspection event.

Study Guide Reference: Public Sector Solution Product Configuration – Inspection Management; Action Plan Templates; Assessment Execution/Visit Execution; Visit target object; Assessment Tasks; Signature Tasks.

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

A Sharing Set is the appropriate Experience Cloud sharing mechanism when external users need access to records associated with their account or contact but don't own those records themselves.

Salesforce states that a sharing set grants Experience Cloud site users access to records by mapping the user's Account or Contact relationship to a corresponding Account or Contact lookup on the target record. Salesforce gives Cases as a specific example: administrators can grant site users access to all Cases associated with the Account identified on the user's Contact record.

That matches this scenario precisely. The internal support team creates the Case, so the external constituent isn't necessarily its owner. A Sharing Set can expose the appropriate Cases to the authenticated external user based on the associated Account or Contact while keeping unrelated constituent Cases inaccessible.

Changing Case OWD to Public Read/Write would be excessively permissive and violate least-privilege principles. A permission set provides object- and field-level authorization but doesn't by itself grant access to specific records restricted by the Salesforce sharing model. Share Groups solve the opposite direction of high-volume sharing: they primarily give internal users access to records owned by high-volume external site users.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud sharing; Sharing Sets; Cases; Account/Contact access mappings; external OWD and least-privilege record access.

The secure Experience Cloud design follows a restrict-first, selectively-share model. Salesforce recommends setting external organization-wide defaults to Private wherever possible , ensuring authenticated external users receive no automatic access to records they do not own or that have not explicitly been shared with them. External OWD therefore establishes the least-privilege baseline required by the scenario.

After establishing that restrictive baseline, Sharing Sets provide authenticated Experience Cloud users access to records associated with their own Account or Contact. Salesforce states that Sharing Sets use access mappings between the external user's Account/Contact and the target record. For example, a user can receive access to Cases associated with the Account identified through their Contact. Sharing Sets support Accounts, Cases, Business License Applications, custom objects, and numerous Public Sector objects.

This mechanism is particularly important for high-volume Customer Community users because conventional role-based sharing isn't the appropriate scalability model. Salesforce specifically recommends Sharing Sets for Customer Community users when access should follow Account or Contact relationships.

Option C is invalid because Hidden isn't an external OWD access level. Option A is less appropriate than Sharing Sets for the account/contact-relative community access model described.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud Security; External OWD; Private access; Sharing Sets; least-privilege external record access.

The decisive requirement is pixel-perfect control over the digital experience . Salesforce specifically positions the Build Your Own (LWR) Experience Cloud template for organizations that need high-performance, highly customized experiences using Lightning Web Components. Salesforce states that the template enables developers to build pixel-perfect pages and create Lightning Web Components and themes that precisely match an organization's brand.

Lightning Web Runtime is optimized for performance because Lightning Web Components execute using browser-native standards, resulting in lightweight components and efficient rendering. LWR also includes performance capabilities such as HTTP caching and publish-time optimizations.

The Licenses and Permits template is excellent when the priority is rapid deployment and minimal customization. It provides preconfigured application, renewal, permit, complaint, inspection-history, and account-management pages. However, that was not the dominant requirement in this scenario. The sponsor has explicitly elevated pixel-perfect branded UX above minimizing implementation effort.

Help Center is designed primarily for public knowledge and support self-service. BYO Aura supports customization but does not provide the performance-oriented modern LWR architecture that Salesforce recommends for sophisticated custom digital experiences.

Therefore, BYO LWR with custom Lightning Web Components best satisfies the specified UX requirement.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud architecture; Build Your Own LWR; Lightning Web Components; branding and digital experience design.

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

Cloning an Action Plan Template creates a separate template configuration; it doesn't automatically redirect existing inspection configuration to the cloned version. Therefore, if the "Business Re-Opening" inspection continues to generate work based on the previous template, the configuration that identifies which Action Plan Template applies to that inspection must be updated. This makes C the intended configuration correction.

Salesforce's current Public Sector inspection architecture maintains the same fundamental principle: an inspection visit must be explicitly associated with the intended published Action Plan Template . Salesforce documents Action Plan Templates as reusable definitions containing assessment tasks, signature tasks, and other activities. When creating the inspection workflow, the appropriate template must be associated with the Visit so that the corresponding Action Plan and assessment indicators are generated.

Merely cloning the template doesn't alter existing references. Option A is unnecessary because creating a new template doesn't inherently require cloning the Inspection Type. Option D is also irrelevant; record identity, rather than display-name similarity, governs the relationship.

The terminology and association workflow have evolved in newer Public Sector releases, but the configuration principle tested by this item remains: the inspection must reference the new template rather than the previous template record .

Study Guide Reference: Public Sector Solution Product Configuration – Inspection Types; Action Plan Templates; Inspection Visits; template associations and version management.

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

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.

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

The verified configuration sequence is B, C, and E . Salesforce's Public Sector documentation explicitly instructs administrators to turn on document checklists , assign the required permissions to users who process documents, and configure Document Types for the information extracted from submitted documents.

Document Checklist must first be enabled through Document Checklist Settings. The intake officer then requires the appropriate permission-set licensing and object access so that only authorized personnel can work with Received Documents, Document Checklist Items, extracted information, and the relevant application records. Salesforce's Intelligent Document Automation user-setup guidance specifically requires assigning Document Checklist and Intelligent Document Workspace access to document-processing users.

Finally, a Document Type must be created to define the type of incoming document—in this case, a Business License Application. Salesforce lists creating a Document Type as a foundational IDA setup task.

Option D is incorrect because Document Types are configured through the dedicated Document Type functionality, not under Notes and Attachments.

Verified correction: the uploaded screenshot marks A, C, E , but Salesforce's documented configuration requirements support B, C, E . There is no equivalent generic "Enable Intelligent Document Automation" step that replaces enabling Document Checklist.

Study Guide Reference: Public Sector Solution Product Configuration – Intelligent Document Automation; Document Checklist Settings; Document Types; user permissions; intake officer access.

Action Plans are intended for exactly this type of repeatable licensing workflow. Salesforce identifies Business License Application as a supported target object for Action Plan Templates, allowing the agency to define standardized reviewer activities that are instantiated whenever the plan is applied to a specific application.

Salesforce also supports Document Checklist Items within action-plan-based document-processing workflows. Document checklist items identify the specific documents that applicants or staff must supply, such as a driver's license. When a document checklist item is included in a published Action Plan Template, it can be propagated to Action Plans created from that template, creating consistent document requirements.

Therefore, option A accurately combines the correct target record—Business License Application—with document tracking for the required identity-document image.

The other statements are overly restrictive. Salesforce supports Action Plan task dependencies in applicable Public Sector implementations, including prerequisite and successor task relationships, so dependent execution can be modeled declaratively. Action Plans also use ordinary task records, and Salesforce supports ad hoc task creation when configured, so staff can supplement standardized plans when case-specific work is necessary.

This gives the agency both governance and flexibility: required standard tasks come from the template, while exceptional application-specific work can still be accommodated.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; Action Plan Templates; Business License Applications; Tasks; task dependencies; Document Checklist Items.

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