AP-222 Practice Questions

Salesforce's DocuSign integration provides exactly the three capabilities identified in C, D, and E . Salesforce Contracts uses DocuSign to support electronic-signature workflows without requiring the implementing agency to create the core signing infrastructure through custom code.

Official Salesforce documentation specifies that the integration can send a contract document for review and signatures , track the signed contract document and update the contract record status , and automatically invalidate a contract document that is pending signatures when a newer contract document supersedes it .

The distinction between A and C is important. Invalidating a superseded document is a native lifecycle capability of the integration; the agency doesn't need to build a separate Salesforce Approval Process merely to accomplish that action. Therefore, C is correct while A introduces unnecessary automation.

Option B is also incorrect. Updating document content during the review/signing operation isn't listed as one of the standard DocuSign contract-signature functions represented by this integration. Contract content should be finalized through the appropriate document-generation and review process before execution.

Together, C, D, and E cover the core end-to-end electronic-signature lifecycle: issue the document for signature, maintain its validity relative to newer versions, and synchronize completed-signature status back to Salesforce.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; DocuSign Integration; eSignature; contract-document lifecycle and status tracking.

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

The three foundational configuration records are Business Type, Regulatory Authorization Type, and Regulatory Authority . Salesforce's regulatory authorization model defines Regulatory Authority as the government agency or department responsible for issuing and enforcing licenses and permits. Regulatory Authorization Type represents the specific license or permit, while Business Type identifies the category of business and activities that require regulatory authorization.

After these components exist, Public Sector uses the Business Regulatory Authorization Type junction object to map a Business Type to the applicable Regulatory Authorization Type. This establishes which licenses or permits are required for a given business activity.

A Business Profile is used to capture information about the applicant's business or individual during application processing, but it is not one of the three foundational authorization-definition records asked for here. Inspection Type belongs to inspection configuration and therefore is not necessary simply to define the license authorization.

Salesforce's configuration sequence explicitly includes creation of Regulatory Authorities, Regulatory Authorization Types, and Business Types as core elements of regulatory authorization setup.

Study Guide Reference: Public Sector Solution Product Configuration – Regulatory Authorization Model; Regulatory Authority; Regulatory Authorization Type; Business Type; Business Regulatory Authorization Type.

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

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 three controls address separate security layers: authentication, automated abuse protection, and record-level access .

Setting grant application pages to Requires Login restricts application workflows to authenticated Experience Cloud users. Salesforce documents the Page Access property for Experience Cloud pages and supports setting pages containing OmniScripts to Requires Login when workflows should only be available to authenticated users.

CAPTCHA or reCAPTCHA provides bot mitigation. Salesforce explicitly uses reCAPTCHA with Experience Cloud application-style forms to confirm that applications are submitted by humans rather than automated bots and recommends it for preventing misuse and spam.

Finally, external organization-wide defaults should be Private for sensitive grant application data. Salesforce's external-user security guidance recommends keeping external OWD settings Private wherever possible so authenticated external users don't automatically gain access to records belonging to other constituents. Additional sharing mechanisms can then selectively expose only the records each user is authorized to access.

A public application-reference search would create unnecessary information-disclosure risk. "Salesforce Spam Check" isn't the appropriate Experience Cloud control represented by this architecture.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud security; authentication; OmniScripts; CAPTCHA/reCAPTCHA; external OWD; privacy and record sharing.

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

Salesforce's official Grants Management installation prerequisites directly support B, C, and E . Grants Management requires the appropriate Grants Management licensing together with Customer Community Plus Login licenses for the external grantseeker experience. Salesforce also requires Lightning Experience and Chatter to be enabled.

Therefore, because the agency's employees currently operate in Salesforce Classic, they must move to Lightning Experience to use the supported Grants Management experience. Chatter must also be enabled because the package depends on Salesforce collaboration functionality. For the external grant portal, Customer Community Plus provides the supported external-user licensing required by the managed-package implementation.

The distinction between options B and D is significant. Although Customer Community is appropriate for many high-volume constituent portals, the Grants Management managed-package prerequisites specifically identify Customer Community Plus Login licensing. This is therefore a product-specific requirement, not merely a generic Experience Cloud licensing choice.

Web-to-Lead concerns conversion of public web submissions into Lead records and has no role in installing or enabling Grants Management.

Salesforce additionally lists Digital Experiences and My Domain among the overall prerequisites, although those choices are not provided in this question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Grants Management installation; Experience Cloud; Customer Community Plus; Chatter; Lightning Experience.

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

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.