Free Practice Questions for Salesforce AP-222 Exam

Salesforce Entitlement Management applies service-level processes to supported service records, particularly Cases. An Entitlement Process defines the service timeline, while Milestones represent required service steps such as response or resolution deadlines. Salesforce confirms that entitlement processes for this pattern run on Cases and can enforce milestone-based service levels.

The requirement is explicitly proactive management. Milestone Warning Actions are therefore essential because they execute when a milestone is approaching violation. Salesforce supports actions such as email alerts, tasks, field updates, flows, and outbound messages before an SLA deadline is missed. Violation Actions, by contrast, execute after the milestone has already been breached. Bobahaven can use Cases to operationally track applications requiring service intervention, associate them with the appropriate entitlement process, and configure milestones representing expected approval-response times. Warning actions can alert owners or supervisors while enough time remains to intervene. The alternatives that trigger escalation only after an SLA breach are reactive rather than preventive. Furthermore, standard entitlement processes are designed around supported service records such as Cases rather than being attached directly to Public Sector application objects in the manner proposed by the other options.

Study Guide References: Service Cloud Cases; Entitlements; Entitlement Processes; Milestones; Warning Actions; SLA Management and Escalation.

Business Rules Engine provides three principal rule-building components represented by these options: Decision Matrices, Decision Tables, and Expression Sets.

A Decision Matrix is a structured lookup table that matches supplied input values to a row and returns the corresponding output. It is well suited to deterministic mappings such as fee schedules, eligibility thresholds, and prioritization categories. A Decision Table is a more flexible lookup mechanism that can read rules from Salesforce records, custom objects, custom metadata, or CSV-based sources and evaluate multiple inputs to return one or more applicable outputs. An Expression Set is the calculation and orchestration layer. Expression Sets can contain variables, constants, conditions, calculations, aggregations, and lookup steps and can call Decision Matrices or Decision Tables as part of a broader business rule. Salesforce describes the main BRE architecture as Expression Sets together with lookup tables, where Decision Matrices and Decision Tables comprise the lookup-table capabilities. Decision Trees and Expression Maps are not identified as core Business Rules Engine modules in this architecture.

Study Guide References: Business Rules Engine; Decision Matrices; Decision Tables; Expression Sets; Lookup Tables; Automated Policy Decisions.

Action Plans provide the standard Public Sector mechanism for organizing, assigning, tracking, and completing repeatable groups of activities. Salesforce describes Action Plans as collections of tasks or checklist items that support repeatable business processes, with individual tasks capable of carrying an owner, priority, and deadline. This structure allows multiple reviewers, inspectors, caseworkers, and other employees to collaborate while retaining visibility into work status and accountability.

For inspections specifically, Public Sector uses Action Plan Templates to define the tasks required for a particular type of inspection visit. Templates can include assessment task definitions, required activities, task sequencing, and signature tasks. Published templates can then generate standardized action plans for individual visits, producing consistent inspection execution across teams. OmniStudio is suited to guided user interactions and integration orchestration, Business Rules Engine evaluates declarative decision logic, and Data Mappers/DataRaptors handle data transformation and persistence. None serves primarily as the collaborative task-management framework for inspection execution. Action Plans directly satisfy both requirements: automated creation of repeatable inspection work and coordinated execution by internal teams.

Study Guide References: Action Plans; Action Plan Templates; Inspection Visits; Assessment Tasks; Public Sector Inspections.

The Analytics for Licenses, Permits, and Inspections template performs a data compatibility check before creating the analytics application. Salesforce requires the Public Sector org to contain source records from the LPI operational data model so that the template can build its datasets and dashboards.

Salesforce ' s current data-requirements documentation identifies Visit as one of the supported source objects used by LPI analytics, along with Business License Application, Individual Application, Public Complaint, and Regulatory Transaction Fee. If the org lacks qualifying source data, the template returns an error during application creation and instructs the administrator to add the required data before trying again. Among the choices, missing Visit data is the relevant operational-data problem associated with the inspection portion of the analytics application. Visits represent actual inspection activity and are therefore central to metrics such as inspections performed, inspection volume, and related operational trends. Violation records, active Action Plan Templates, and Person Account enablement are not listed as the prerequisite represented by this compatibility-check scenario.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Data Requirements; Visit Object; Analytics Compatibility Check.

Public Sector ' s inspection and complaint capabilities are designed to maintain operational traceability from a reported concern through investigation and regulatory follow-up. Salesforce supports Public Complaint records for constituent-reported issues and allows an agency to create visits directly from complaints so inspectors can investigate concerns onsite. The complaint can also surface related visits, regulatory code violations, enforcement actions, and supporting documentation.

Consequently, the agency should configure the standard Inspections and Visits framework and associate the resulting inspection activity with the relevant permit application. Salesforce describes Public Sector inspections as the mechanism for evaluating regulatory compliance through onsite visits, standardized assessment questions, recorded findings, violations, and enforcement activity. Cases can provide the managed investigation or service record associated with the reported issue and can participate in the broader Public Sector complaint and investigative data model alongside Business License Applications, Public Complaints, Visits, and regulatory records. Linking the appropriate case and field-inspection activity to the existing permit preserves the context required by reviewers and enforcement personnel. Business Rules Engine is intended for structured rule evaluation rather than determining whether a complaint is inherently valid. Action Plans can organize repeatable work but are not the essential linkage requested here.

Study Guide References: Public Complaints; Cases; Inspections; Visits; Permit Applications; Licensing, Permitting and Inspections Data Model.

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 References: Experience Cloud Security; External Organization-Wide Defaults; Sharing Sets; Customer Community; Grants Application Security.

Salesforce Knowledge combined with a publicly accessible Experience Cloud page provides the lowest-complexity self-service architecture for general licensing and permitting guidance. Constituents can read FAQs, process descriptions, prerequisites, required-document guidance, and other published Knowledge content before beginning an application, which directly reduces repetitive contact-center requests.

Salesforce explicitly supports an Experience Cloud site acting as a public Knowledge base for unauthenticated users. Guest users can access publicly available Experience Cloud pages and read Knowledge articles without requiring external-user licenses. This approach also aligns with the Public Sector Licenses and Permits digital experience, where Experience Cloud is used to give constituents access to licensing and permitting processes. Salesforce ' s Public Sector site template provides preconfigured experiences for assessing license requirements, applying, renewing, filing complaints, and viewing inspection information. Authentication is unnecessary for general information that is intentionally public. Requiring login creates additional friction before the constituent has even begun an application. Lightning Out or outbound API synchronization to a separate CMS introduces additional implementation and maintenance work because content must be integrated into another presentation layer.

Study Guide References: Salesforce Knowledge; Experience Cloud; Guest User Access; Licenses and Permits Site; Constituent Self-Service.

Salesforce ' s DocuSign integration provides a packaged electronic-signature lifecycle for contract documents. Salesforce explicitly documents that the integration can send a contract document for review and signatures, track the signed document and update the contract record status, and automatically invalidate a pending signature document when a newer contract document supersedes it.

These features maintain transactional integrity throughout the signature process. Sending the document initiates the controlled signature workflow. Status tracking keeps Salesforce synchronized with the state of the DocuSign envelope and enables the contract record to reflect completion. Automatic invalidation prevents a signer from executing an outdated document version after a newer authoritative version is generated. An additional Salesforce approval process is not required simply to invalidate the superseded signature document because that behavior is already part of the supported eSignature lifecycle. Similarly, changing contract contents during the signing process is not one of the standard DocuSign capabilities represented here. Document changes should occur through the controlled document revision and regeneration process before a new signature request is issued.

Study Guide References: DocuSign Integration; Electronic Signatures; Contract Documents; Signature Tracking; Superseded Document Invalidation.

A Screen Flow provides the most flexible declarative experience for simplifying Visit creation. Instead of requiring users to navigate through related lists and manually populate every field, the flow can present only the fields required for the specific inspection process, prepopulate known values, apply validation, derive contextual values from the originating application, and create the Visit record automatically.

Salesforce ' s standard inspection documentation confirms that Visits are normally created from the Visits related list on a license application or public complaint and require information such as location, account, context, visit type, schedule, and inspector. A Screen Flow can streamline that sequence into a guided interaction launched directly from the application page. Flow is particularly appropriate because the requirement is user-interface simplification and record creation rather than custom programmatic processing. The flow can receive the application ' s record ID as context, retrieve related information, display the appropriate input controls, and create the Visit. Moving a related list does not eliminate manual data entry. A predefined action can prepopulate static or predictable fields, but a Screen Flow provides significantly greater control over conditional fields, validation, lookups, and multi-step creation logic.

Study Guide References: Inspection Management; Visit Creation; Salesforce Flow; Screen Flow; Business License Application; Individual Application.