Salesforce Accredited Agentforce 360 for Public Sector Professional AP-222 Exam Questions

Page: 1 / 14
Total 106 questions
Question 1

A government agency has implemented an eSignature solution and has chosen DocuSign as the vendor. As part of the non-functional requirements, the system needs to poll the status of signed envelopes.

What is the best way to achieve this requirement?



Answer : B

Salesforce provides the ContractEnvelopeStatusScheduler Apex class specifically for polling DocuSign envelope statuses in the supported eSignature integration. Salesforce documentation explicitly states that this class can be scheduled to poll DocuSign for envelopes submitted through the eSignature process.

The scheduled job queries envelope status and updates Salesforce so contract and document records reflect states such as sent, completed, or voided. Salesforce notes that when scheduled through the Salesforce UI, the job can run hourly. It can also be scheduled through Apex at shorter intervals, subject to DocuSign's minimum polling interval requirements. DocuSign requires at least 15 minutes between successive polling calls. Salesforce's recent support guidance also confirms that ContractEnvelopeStatusScheduler remains the scheduled job responsible for retrieving envelope-state updates and discusses asynchronous handling when many envelopes require updates simultaneously. Using Salesforce's provided scheduler is preferable to building a separate REST polling implementation because it follows the supported Industries/DocuSign integration architecture. The other scheduler class names do not correspond to the documented component.

Study Guide Reference: DocuSign Integration; ContractEnvelopeStatusScheduler; eSignature Envelope Status; Scheduled Apex; Contract Lifecycle Management.


Question 2

A government-supported agency that helps constituents track the status of their claims is using Agentforce Public Sector. For claim assessors to review and process claims, it is crucial to see the applications' Decision Explanation Logs.

Which component can be added to see the history of Decision Explanations for a claim?



Answer : A

The Decision Explainer Log History component is specifically designed to display historical explanations generated by Decision Explainer for application-related decisions. Salesforce instructs administrators to add this component to the relevant Lightning record page so reviewers can examine how previous Business Rules Engine decisions were calculated.

Each entry includes the date and time of the decision, the Expression Set name, and the Expression Set version that executed. Reviewers can open an individual log entry and inspect the variables, values, and formulas used to calculate the result. This is especially important in claim, benefit, eligibility, prioritization, and regulatory processes where the agency must explain why an automated decision produced a particular outcome. Decision Explainer works in conjunction with Business Rules Engine and provides insight into why a rule generated a specific result. Salesforce identifies Decision Explainer as part of the BRE architecture for transparent automated decision-making. Record History is intended for tracking changes to fields, while a generic audit or log-history component does not provide Business Rules Engine reasoning. The dedicated Decision Explainer Log History component therefore provides the application-level explainability required by claim assessors.

Study Guide Reference: Decision Explainer; Decision Explainer Log History; Business Rules Engine; Expression Sets; Decision Logs; Application Review.


Question 3

A customer wants to view multi-level data related to an Account, such as all the inspections performed and the regulatory violations found. They want to see this on the Account page layout.

What solution should the technical consultant use?



Answer : C

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 Reference: Hierarchical View; Account Unified View; Visits; Regulatory Code Violations; Enforcement Actions; Public Sector Record Relationships.


Question 4

A customer wants to implement a customer community. Authenticated users will be able to log cases, manage their account and contact information, and apply/view their grant applications.

What two security settings should be configured to ensure the community is secure and no extra information is available to the authenticated community users?



Answer : B, C

A secure external-user sharing model starts with Private external organization-wide defaults. Salesforce explicitly recommends configuring external OWD as Private whenever possible so authenticated Experience Cloud users cannot see records that they do not own or that have not otherwise been shared with them.

After establishing this restrictive baseline, Sharing Sets provide the controlled mechanism for granting external users access to the particular Accounts, Cases, Contacts, applications, and other records associated with their own Account or Contact relationships. Salesforce specifically documents this pattern for external and high-volume community users. This design follows least privilege: nothing is exposed by default, and the site user receives only the application and service records required for their own interaction with the agency. Traditional sharing rules can be useful for external users with roles, but they are not the universal mechanism for high-volume Experience Cloud users. Sharing Sets are purpose-built for these relationship-based external access scenarios. Hidden is not an available organization-wide default record-access level. Salesforce documents external access values such as Private, Public Read Only, Public Read/Write, and Controlled by Parent where applicable.

Study Guide Reference: Experience Cloud Security; External Organization-Wide Defaults; Sharing Sets; Customer Community; Grants Application Security.


Question 5

What are the two key document types that a consultant might be asked to produce for Public Sector Solutions implementation?



Answer : A, D

User Stories and a Functional Requirements Specification (FRS) are key implementation artifacts because they translate business objectives into requirements that can be designed, configured, tested, and accepted.

User Stories describe required behavior from the perspective of a particular persona or stakeholder. They help implementation teams break large public-sector processes into manageable requirements with clear outcomes and acceptance criteria. For example, a permitting implementation can contain separate stories for applicants, intake officers, inspectors, supervisors, and licensing administrators. The Functional Requirements Specification provides a more consolidated description of what the solution must accomplish. It documents functional processes, business rules, data requirements, integrations, security considerations, roles, and expected system behavior so that the implementation team has a controlled reference for solution design and validation. This aligns directly with Salesforce's official Agentforce Public Sector exam objectives. The exam guide expects consultants to document business needs and customer outcomes and, given a customer scenario, map and document the business process, personas, and requirements. A Marketing Plan concerns external promotion rather than solution requirements. A Budget Plan is part of project and financial governance but is not one of the two functional implementation documents identified in this context.

Study Guide Reference: Requirements Gathering; User Stories; Functional Requirements Specification; Personas; Business Process Mapping; Solution Design Documentation.


Question 6

Foodvania has adopted Agentforce Public Sector to get relief to small businesses experiencing hardship due to the pandemic. Foodvania would like the recipients to apply for relief in a self-service portal, allowing for the upload of supporting documentation and the capability to check the status of their application.

What should the consultant recommend using?



Answer : D

Grants Management provides the complete grantseeker portal capability required for this scenario. Salesforce describes Grants Management as enabling organizations to launch a portal where grantseekers can discover funding opportunities, apply for funding, view application status, and submit ongoing progress information for awarded grants.

The portal is implemented through Experience Cloud using the Grantee Portal template. Salesforce states that this preconfigured template provides a place where applicants can view available Funding Programs, submit applications, and manage their applications after submission. The Grants Management workflow also supports application materials and attachments, allowing supporting documentation to be incorporated into the funding-request process. Although Grants Management uses the Outbound Funds Module data model underneath its grantmaking functionality, Salesforce distinguishes the products functionally. Grants Management provides enhanced portal capabilities, application workflows, self-registration, application mapping, review workspaces, Action Plans, and other grantmaker functionality beyond the basic Outbound Funds foundation. Foodvania therefore does not need to design a separate relief portal around the underlying Outbound Funds Module. Grants Management supplies the packaged portal experience required for external recipients to apply, provide supporting information, and monitor application status.

Study Guide Reference: Grants Management; Grantee Portal; Experience Cloud; Funding Programs; Funding Requests; Grantseeker Application Management.


Question 7

The Department of Disaster Assistance is implementing Grants Management using Agentforce Public Sector. One of the pain points in the current process is that every grant application reviewer follows a different business process to review the applications received. A solution has been engaged to standardize this process using the Public Sector Solutions toolkit.

What should be the best solution to achieve this task?



Answer : C

Action Plans provide the standard Salesforce mechanism for converting a repeatable review or due-diligence procedure into a structured sequence of tasks and document requirements. Salesforce Grants Management specifically supports completing grantseeker due diligence by using Action Plans, Verification Checks, and Tax Status Search.

For a repeatable process, the administrator creates and publishes an Action Plan Template that defines the required activities. Reviewers then generate an Action Plan for the relevant grantseeker Account and follow the same standardized set of tasks. Salesforce's documented Grants Management process provides an example in which a published due-diligence Action Plan Template is instantiated directly from an Account record to track the organization's requirements. Action Plans also work with Document Checklist Items, making them particularly suitable where reviewers must collect prescribed documents in addition to completing tasks. Salesforce provides dedicated Action Plans and Document Checklist permissions for Grants Management users. A Screen Flow or OmniScript could implement a custom guided process, but doing so would duplicate functionality that Action Plans already provide declaratively. Written guidance alone would not enforce consistent operational execution.

Study Guide Reference: Grants Management; Action Plans; Action Plan Templates; Due Diligence; Document Checklist Items; Verification Checks.


Page:    1 / 14   
Total 106 questions