Free Salesforce AP-222 Practice Exam with Questions & Answers | Set: 2

Salesforce defines Expression Sets and Decision Matrices as the key components of Business Rules Engine and explicitly establishes their relationship. Expression Sets perform a sequence of calculations using matrix lookups, user-defined variables, constants, conditional logic, and other BRE elements. During execution, an Expression Set can call a Decision Matrix , which stores business rules as a structured table of input and output values.

A Decision Matrix does not itself perform the sequence of calculations described in option A. Instead, it accepts input values, locates the table row that satisfies those values, and returns the corresponding output. That behavior makes option C reversed: matching inputs to rows is the responsibility of the Decision Matrix, not the Expression Set.

Option D is also technically incorrect. Salesforce documents that Expression Sets and Decision Matrices can receive JSON input from OmniScripts and return JSON output , not XML input.

This architecture is particularly effective for Public Sector licensing because frequently changing regulatory criteria, fee schedules, eligibility conditions, and authorization rules can be maintained declaratively in Decision Matrices while Expression Sets orchestrate the calculations and matrix lookups.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Decision Matrices; matrix lookups; JSON integration with OmniScripts.

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

An unauthenticated Experience Cloud site backed by Salesforce Knowledge is the most efficient architecture for publishing frequently requested licensing and permitting information to the general public. Salesforce supports Knowledge articles in Experience Cloud and allows appropriately configured guest users to access publicly available articles without authenticating. This directly supports constituent self-service while reducing repetitive contact-center inquiries.

This approach also minimizes implementation and maintenance overhead because the agency can maintain its authoritative articles directly in Salesforce Knowledge and expose them through the Experience Cloud presentation layer. Salesforce specifically notes that an Experience Cloud site can function as a public knowledge base for unauthenticated users without requiring community licenses simply for public article access.

Option A introduces an unnecessary CMS integration and outbound API synchronization layer. Option B similarly adds unnecessary integration complexity through Lightning Out. Option D forces constituents to authenticate merely to read general application-process information, adding friction and potentially requiring additional license considerations.

The architectural best practice is therefore to keep public informational content openly accessible while reserving authentication for personalized records, applications, and protected constituent data.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud, Salesforce Knowledge, constituent self-service, guest-user access, and public information delivery.

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

Salesforce Entitlement Management and Milestones provide the correct mechanism for tracking SLA-based support response requirements. An entitlement process defines the service timeline, while milestones represent required time-dependent steps such as first response or resolution. Salesforce supports entitlement processes for support records such as Cases , and milestones can generate warning actions before an SLA is violated.

The word proactively is decisive. Salesforce distinguishes three milestone action categories: success, warning, and violation. Warning actions execute when a milestone is approaching violation, allowing email alerts, tasks, field updates, or other escalation actions to occur before the target is missed.

Therefore, A provides both the supported record architecture and the required proactive behavior. Option B waits until the SLA is already breached and thus fails the proactive requirement.

Options C and D incorrectly imply that standard entitlement processes can simply be placed directly on arbitrary Public Sector application records. Salesforce's supported Milestone objects include Cases, Work Orders, and Incidents; standard Business License Application records aren't listed as direct Milestone targets.

The appropriate pattern is therefore to manage the response/escalation process through Cases associated with the underlying application context and apply Entitlements and Milestones to those Cases.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – constituent service; Cases; Entitlements; Milestones; SLA warning actions and proactive escalation.

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

Decision Explainer provides transparency into calculations and decisions produced by Business Rules Engine. For the Public Sector curriculum version represented by this question, Salesforce explicitly identifies Decision Explainer use cases that include individual and business application fees, unemployment benefits, and education loan eligibility checks . Therefore, among the available options, A and B correspond to supported Public Sector Decision Explainer scenarios. Salesforce's Public Sector Developer Guide specifically lists these examples when describing how Decision Explainer exposes the reasoning behind Expression Set calculations.

The architecture is based on Business Rules Engine executing an Expression Set, potentially calling Decision Matrices containing policy criteria, and Decision Explainer recording the inputs, calculations, intermediate values, and resulting decision. Reviewers can then inspect why a claimant qualified, failed eligibility requirements, or received a particular calculated amount.

Person Loans and Car Loan are not identified Public Sector Decision Explainer examples in this curriculum. They represent generic lending concepts rather than the documented Public Sector scenarios.

A versioning point is relevant: newer Salesforce Help currently uses housing loan eligibility checks in its example list, while the Salesforce developer documentation associated with the exam-era content uses education loan eligibility checks.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Decision Explainer; Business Rules Engine; Expression Sets; benefits eligibility and application-fee calculations.

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

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.

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

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.

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

Expression Sets use resources such as variables and constants to hold values used during calculations and rule execution. When an administrator creates or adds a resource in an Expression Set version, the resource is assigned an appropriate data type. Salesforce officially lists Currency as a supported Expression Set resource data type, together with Text, Number, Percent, Date, Date & Time, and Boolean.

Therefore, the administrator should configure the value through Add Resource in the Expression Set , making option C correct. A Currency resource supports numerical comparison operators including equals, not equals, less than, greater than, and their inclusive variants, making it suitable for licensing fee calculations.

Decision tables can also contain currency-compatible fields in supported Business Rules Engine scenarios, but the question asks specifically where the administrator establishes the data type for a resource within an Expression Set . That configuration occurs in the resource definition rather than through OmniScript options.

Salesforce explains that variables and constants are resources that hold dynamic or fixed values and are used as inputs, outputs, and intermediate values throughout expression-set execution.

Process Builder entry criteria are unrelated to Business Rules Engine resource typing.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Resource Manager; variables and constants; Currency data type; licensing fee calculations.

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

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.

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

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.

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