Free and Premium Salesforce AP-222 Dumps Questions Answers

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.

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

VS Code and Salesforce DX provide the supported development and deployment tooling for OmniStudio Lightning Web Components associated with DataPacks. Salesforce explicitly states that administrators and developers use Visual Studio Code with Salesforce DX and the Salesforce CLI to manage, develop, and deploy OmniStudio Lightning Web Components between development, sandbox, and production organizations.

This distinction matters because an OmniStudio DataPack can include configuration metadata as well as generated or supporting Lightning Web Component artifacts. When LWC deployment is required, a Salesforce DX project provides the metadata structure, authentication, source management, and deployment commands needed to transfer the components reliably between environments.

VS Code by itself is only the development environment; it does not constitute the complete Salesforce deployment mechanism. Salesforce DX provides the Salesforce-specific project model and deployment capabilities, making option B incomplete. Standard Change Sets aren't the recommended deployment mechanism for these OmniStudio LWC assets, while the ANT Migration Tool represents an older Metadata API deployment approach and isn't the prescribed toolchain for this requirement.

Therefore, the complete supported combination identified by Salesforce is Visual Studio Code together with Salesforce DX.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio deployment, DataPacks, Lightning Web Components, VS Code, Salesforce DX/SF CLI.

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

An approval process is the correct architecture because the requirement combines conditional approval routing with an auditable approval history. Salesforce approval processes define the criteria under which a record enters approval, specify the approval steps, identify the appropriate approvers, and preserve the state of the approval request.

The consultant can use the application's age or duration as the entry or step criterion and route qualifying records to the appropriate manager. Salesforce's approval framework tracks states such as Submitted, Pending, Approved, Rejected, Reassigned, and Recalled. The Approval History related list provides users with visibility into the record's progress and creates the audit trail required by the scenario.

A Flow that merely changes ownership doesn't constitute manager approval and doesn't inherently provide the same approval-process audit model. Chatter is a collaboration mechanism rather than a controlled regulatory approval system. An "approval escalation rule" isn't the correct Salesforce automation construct for this requirement.

Salesforce now recommends Flow Approval Processes as the modern successor for many new implementations, providing dynamic routing and detailed compliance logging; however, among the supplied answer choices, C precisely describes the required approval-process pattern.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – application approvals; approval criteria; manager routing; Approval History; regulatory auditability.

The lifecycle begins with Plan , where the grantmaker defines the funding program, objectives, eligibility, funding availability, and program structure. The organization then Engages prospective grantseekers by publishing and communicating the funding opportunity. Eligible grantseekers subsequently Apply , after which the grantmaker conducts the formal Review process and determines which applications receive an Award . The award then enters the Manage stage, covering requirements, disbursements, progress reporting, compliance, and performance monitoring, followed by formal Close Out .

This sequence aligns with Salesforce's Grants Management architecture. Salesforce Trailhead describes the lifecycle operationally: the grantmaker creates and publishes Funding Programs, a grantseeker applies by creating a Funding Request, verification and reviews occur, requirements are processed, and successful applications proceed to disbursement and continuing management.

Salesforce's Grantmaking material likewise separates application decisions from the subsequent Funding Award, then uses the award as the central record for post-award disbursements, requirements, expenditure tracking, progress reporting, and eventual completion.

Options C and D put lifecycle stages in an illogical order. Option A is structurally invalid because it places Apply before planning and repeats Apply.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management lifecycle; Funding Programs; applications; reviews; awards; post-award management; closeout.

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

Intelligent Form Reader is the appropriate capability because it is specifically designed to extract structured information from uploaded documents through optical character recognition and then use that extracted information to create, update, or verify Salesforce record data. Salesforce documentation explicitly describes a validation scenario in which a person's birth date stored in Salesforce is compared against the birth date extracted from a scanned passport. This directly matches the requirement in the question.

For identity documents such as driver's licenses and passports, Intelligent Form Reader can use document types, extraction templates, field mappings, and Amazon Textract capabilities to identify values such as date of birth. The extracted field can then be mapped to the corresponding Salesforce field and used as part of an automated verification process.

Content, Attachments, and Files provide mechanisms for storing or associating documents, but none independently performs OCR-based extraction and validation of document data. They can participate in document storage, but they do not satisfy the stated automation requirement.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Intelligent Form Reader; document extraction, OCR, document types, field mappings, and identity-document verification.

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

Grants Management is the appropriate product because it includes the grantseeker portal experience required for external applicants to discover funding opportunities, apply online, supply application information, and manage their applications.

Salesforce describes the Grants Management managed package as providing program management, financial commitments, relationship management, and a grantee portal . The portal is specifically intended to improve the applicant/grantee experience while allowing grantmakers to manage the complete funding lifecycle.

Salesforce's portal setup documentation explains that the Grantee Portal Experience Cloud template provides a location where people can review available Funding Programs, apply to programs, and manage their applications. Grants Management also supports enhanced application flows, organization self-registration, application mapping, collaboration, and other functions beyond the lightweight funding-management capabilities of Outbound Funds Module.

This matches Foodvania's requirement for a constituent-facing relief application experience with supporting documentation and ongoing application management.

Outbound Funds Module supplies the underlying funding data model and can manage Funding Programs, Funding Requests, reviews, and disbursements. However, Grants Management provides the richer preconfigured portal and application experience targeted by the scenario. Therefore, it is unnecessary to combine the products as option A suggests simply to obtain the applicant-facing capabilities described.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management; Grantee/Grants Portal; Funding Programs; Funding Requests; application management and constituent self-service.

The Licenses and Permits Experience Cloud template should be used because Salesforce supplies it specifically for constituent licensing and permitting experiences. It includes preconfigured pages for applying for licenses or permits, renewing authorizations, viewing applications and licenses, reviewing inspection history, filing complaints, and identifying permit requirements.

Using this purpose-built template significantly reduces custom implementation and long-term maintenance compared with retrofitting a generic Help Center site. Salesforce also provides OmniStudio-driven application capabilities that can be placed directly into Experience Cloud, including dynamic application forms built with OmniScripts and supporting components.

Option C could technically be implemented, but it would require the agency to manually recreate capabilities that Salesforce already supplies through the dedicated template. That contradicts the requirement to minimize customization and maintenance.

OmniOut is intended for scenarios where OmniStudio experiences must run outside Salesforce-hosted environments. Since the requested constituent application experience is being implemented directly on Experience Cloud, OmniOut adds unnecessary architecture and deployment complexity. Therefore, neither A nor D represents the most maintainable design.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Licenses and Permits Experience Cloud Site; Experience Cloud templates; OmniScripts; FlexCards; reuse of preconfigured Public Sector components.

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

Partner Central is specifically designed for partner relationship management and channel-sales workflows. Salesforce documents Partner Central as a responsive Experience Cloud template intended to help organizations recruit, build, and grow partner networks while supporting channel sales and marketing activities. Its standard capabilities include lead distribution, deal registration, partner recruitment and onboarding, marketing campaigns, enablement, pipeline management, and related reporting.

Those capabilities correspond directly to the scenario. The external associates function as channel partners, and the agency needs a collaborative portal for onboarding those partners and managing sales-style workflows around licensing activities.

Customer Account Portal is designed primarily for customers managing their own account information and accessing customer-oriented services. Help Center is focused on support and self-service knowledge experiences rather than partner sales processes. Aloha is a legacy template and is no longer the preferred architecture for a new implementation.

Salesforce also requires appropriate partner licensing for Partner Central functionality and explicitly associates the template with Partner Community and related partner-oriented licenses.

Study Guide Reference: Public Sector Solution Product Configuration – Experience Cloud templates, Partner Central, partner onboarding, lead distribution, deal registration, and channel collaboration.

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

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.

Categories for Dynamic Assessment questions are configured on the Assessment Question object. Salesforce explicitly instructs administrators to create categories by navigating to the Assessment Question object's Category picklist field and adding the required values.

Categories create logical groupings of assessment questions so that designers can efficiently locate and select the correct questions for different assessment contexts. Salesforce provides examples such as Fire Safety Inspection, Roof Inspection, Electrical Inspection, Solar Permit, and Public Safety Complaint. The same architecture applies here: categories could represent Take-Away, Dining, or another relevant inspection context and then be assigned to the specific questions to which each category applies.

The critical clue is that categorization applies to specific questions . Assessment Indicator Definitions represent predefined compliance indicators used primarily in the traditional inspection model; they aren't the object on which Dynamic Assessment question-category picklist values are maintained. Assessment Task Definitions group work performed during inspection execution but don't define the category metadata of individual Dynamic Assessment questions.

Action Plans organize repeatable tasks and assessment activities and are therefore also at the wrong layer.

Salesforce additionally supports Question Sets for grouping questions by context, but the question asks specifically where new categories are created.

Study Guide Reference: Public Sector Solution Product Configuration – Dynamic Assessments; Assessment Question; Category picklist; inspection question organization.

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

Salesforce requires users who configure or use Action Plans to have the appropriate Action Plans permission set . Salesforce's Public Sector Action Plans documentation explicitly identifies the required user permission as the Action Plans permission set and directs administrators to assign it through the user's Permission Set Assignments.

The scenario isolates the problem to one newly onboarded inspector while every existing inspector can access the same feature. That strongly indicates a user-specific permission assignment rather than an organization-wide configuration problem. If Person Accounts weren't enabled and were genuinely required, the impact would affect the implementation generally rather than only one inspector.

Likewise, "Enable Notes" isn't the feature permission controlling Action Plans. Action Plans have dedicated access requirements covering objects such as Action Plan, Action Plan Template, Document Checklist Item, and Recurrence Schedule, together with the Action Plans feature permission where appropriate.

A completely disabled Salesforce user would be unable to log in to Salesforce at all, not merely unable to access Action Plans. The wording indicates the inspector is successfully using Salesforce but lacks access to this particular capability.

Therefore, checking and assigning the Action Plans permission set is the precise troubleshooting action.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; user access; Action Plans Permission Set; inspection-user configuration.

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

The lowest-customization Public Sector architecture is to reuse the prebuilt Emergency Service Request flow and deploy the constituent experience through the preconfigured Emergency Response Management digital-experience template .

Emergency Response Management is designed to accelerate deployment of emergency programs and constituent-service workflows. Its digital experience provides the public-facing channel through which citizens and businesses can obtain emergency information and submit requests for assistance or services. Using the purpose-built template prevents the agency from recreating emergency-specific navigation, pages, and constituent processes from a generic Experience Cloud template.

The Emergency Service Request flow provides the intake layer. It captures the basic information needed for an emergency request and creates the corresponding Salesforce records through the configured Emergency Response architecture. This provides a declarative alternative to developing a custom request workflow.

A Help Center template is primarily designed for knowledge and customer-support self-service and would require additional configuration to reproduce Emergency Response functionality. Creating a custom Case record type and relying on a generic Contact Support Form similarly duplicates functionality already supplied by the solution and introduces unnecessary technical debt.

The Set 3 source shows C and D as the selected combination for this item.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Emergency Response Management; Emergency Service Requests; Experience Cloud; preconfigured emergency-response digital experiences.

The requirement is straightforward operational reporting rather than advanced analytical modeling, so standard Salesforce Reports and Dashboards provide the lowest-cost and lowest-complexity solution. A custom dashboard can consolidate multiple approval metrics—pending application count, aging, application duration, and longest-pending items—into a single visual view.

The second requirement is that approvers see the information when they log in . Salesforce supports adding Dashboard and Report Chart components directly to a Lightning Home page through Lightning App Builder. A customized Home page can then be activated for the appropriate user context, including assignment by profile.

That makes A superior to B. A dashboard provides the requested summary , whereas a report primarily presents rows of data. More importantly, Lightning Home page activation supports profile-based assignment; a role isn't the appropriate activation mechanism expressed in option B.

CRM Analytics would be technically capable of presenting approval analytics, but it introduces additional licensing, datasets, configuration, and operational overhead without providing a material advantage for the relatively simple requirement. Salesforce already supplies native approval user-interface capabilities and Home page support for approval work.

Therefore, a standard custom Approvals dashboard placed on an Approver-profile Home page satisfies the requirement while minimizing customization and cost.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Reports and Dashboards; Lightning Home Pages; approval monitoring; user-profile page assignment.

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

Decision Explainer is specifically designed to expose why Business Rules Engine produced a particular calculation or eligibility determination. Salesforce describes Decision Explainer as a collection of setup objects that provides transparency into business-rule calculations and supports agencies in explaining decisions to constituents.

When grant eligibility is calculated through Expression Sets and related Business Rules Engine components, Decision Explainer can retain the relevant decision context. Reviewers can inspect the Expression Set used, input values, calculations, and the resulting outcome. This is exactly what is needed when an applicant challenges a declined eligibility determination: the authority needs the reasoning associated with the actual application record , rather than attempting to reproduce the calculation separately.

Debug logs are primarily technical diagnostics. They may show execution details but aren't the business-facing explainability mechanism designed for caseworkers or reviewers and don't provide the same structured decision history. Testing representative datasets validates rules before deployment but doesn't explain why the particular constituent's submitted application was rejected. "Selection Explainer" is not the appropriate Salesforce Public Sector feature.

Decision Explainer therefore supports both operational transparency and governance by making automated eligibility and calculation outcomes understandable and reviewable.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Decision Explainer; Business Rules Engine; eligibility determinations; Explainability Action Logs; auditability.

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

An Aggregate Group is the Business Rules Engine construct designed to repeat prior Expression Set logic for multiple input-value sets and then consolidate the resulting values. This matches a licensing scenario where one application contains multiple permits and the system must calculate a fee for each permit and then produce the total.

Salesforce explains that an Aggregate Group runs the preceding steps once for each input set and then applies aggregation logic to the results. Inside the Aggregate Group, the Aggregate step must be the first element and can perform SUM, AVG, MAX, or MIN calculations. Aggregate steps cannot exist independently outside an Aggregate Group.

Accordingly, the consultant first places an Aggregate Group at the appropriate point in the Expression Set and then adds an Aggregate step configured with the SUM function. If the rule calculates each selected permit's fee independently, SUM consolidates those calculated fee values into the total application fee.

A custom Lightning Component is unnecessary because Business Rules Engine already provides aggregation declaratively. Permission sets may be required to execute or administer BRE, but they don't implement the fee-calculation logic requested in the question.

Therefore, B and D represent the functional configuration required to support multiple selected permits and aggregate their calculated fees.

Study Guide Reference: Public Sector Solution Product Configuration – Business Rules Engine; Expression Sets; Aggregate Groups; Aggregate step; SUM function; multi-permit fee calculations.

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

Agentforce Public Sector already provides the Regulatory Code Assessment Indicator junction object to relate regulatory codes to Assessment Indicator Definitions. Consequently, a custom junction object or custom master-detail relationship is unnecessary.

Salesforce describes Assessment Indicator Definitions as the conditions inspectors evaluate when determining whether a business or site complies with regulatory requirements. After defining an assessment indicator, administrators relate it to its applicable regulatory code through the Regulatory Code Assessment Indicator related list.

Salesforce's documentation on Public Sector junction objects further confirms that Regulatory Code Assessment Indicator relates Regulatory Code and Assessment Indicator Definition , mapping the compliance standard to the measure used during an inspection. This is inherently a many-to-many requirement: one regulatory code may have multiple assessment indicators, and an assessment indicator can be associated where applicable within the regulatory framework.

Option A unnecessarily creates custom architecture for functionality already supplied by the Public Sector data model. Option B uses an incorrect object name. Option C imposes an inappropriate direct master-detail relationship rather than using the standard junction model.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Regulatory Compliance data model; Assessment Indicator Definition; Regulatory Code Assessment Indicator; inspection configuration.

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

The native Public Sector design combines an OmniScript application form with Business Rules Engine . Salesforce explicitly documents this architecture for automatically calculating processing fees associated with business license applications. Business Rules Engine uses Decision Matrices and Expression Sets to determine fee amounts from multiple input criteria, while the OmniScript captures those constituent inputs.

For example, a Decision Matrix can contain base-fee values indexed by authorization type, industry category, location, revenue band, or another applicable parameter. An Expression Set invokes one or more matrices, performs any additional arithmetic, and returns a calculated currency amount. Salesforce documents that Expression Sets and Decision Matrices accept JSON input from and return JSON output to OmniScripts.

The integration is direct: Salesforce explains that an Expression Set Action can be added to the OmniScript so that, when the applicant supplies the required information, the Business Rules Engine processes those values and returns the appropriate license fee.

Triggered Flow could calculate values, but it would duplicate a purpose-built policy calculation engine. Integration Procedures are appropriate for data orchestration and external integrations, not for replacing BRE as the authoritative fee-policy engine. A generic Flow application also bypasses the Public Sector OmniScript application architecture.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScripts; Business Rules Engine; Expression Sets; Decision Matrices; automated application fee calculation.

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

The required combination is Web-to-Case, Person Accounts, and the Emergency Response Management for Public Sector managed package . This question reflects the ERM deployment architecture in which the agency provides an external digital destination for constituents and organizations to submit emergency-related requests while Public Sector components manage those requests internally.

Person Accounts provide the appropriate Salesforce representation for individual constituents who are not operating as business accounts. Web-to-Case supplies a standard intake mechanism through which web-submitted constituent requests can become Salesforce cases. The managed ERM package supplies the purpose-built emergency-response functionality; the unmanaged-package alternative is therefore incorrect.

Current Salesforce documentation describes Emergency Program Management as an Agentforce Public Sector capability for exposing emergency program information, incident updates, permits, assistance programs, and constituent requests through an Experience Cloud site. Salesforce also identifies Emergency Program Management as a specific Public Sector implementation area in the current Agentforce Public Sector portfolio.

Email-to-Case processes inbound email into cases but does not satisfy the specified web-based constituent experience prerequisite.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Emergency Response Management; Person Accounts; constituent digital intake.

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

The product-native, low-code solution is to use Salesforce's DocuSign integration together with the supplied generic DocuSign OmniScript rather than designing Apex-based envelope handling.

Salesforce currently documents the sample OmniScript under the exact technical name GenericDocuSign/sendEsignature . It sends one or more documents associated with standard objects such as Opportunity, Order, or Quote—and supported custom objects—to DocuSign for electronic signature. The user selects the recipients and documents, reviews the routing order, and sends the envelope directly through the guided OmniScript.

Salesforce also provides a Send for eSignature (Generic) action that launches this OmniScript, minimizing custom development and allowing the signed-document status to be tracked using Generic DocuSign Envelope functionality.

Therefore, option C represents the intended answer. The option's GenericDocuSign/sendSignature wording reflects older/abbreviated exam terminology; Salesforce's current documented component is GenericDocuSign/sendEsignature. Option A refers to an "ObtainSignature" process rather than the send-for-signature flow needed when agreements must be transmitted to external grantseekers. Options B and D introduce the separate managed-package/Flow architecture when the supplied OmniScript capability already solves the requirement with less custom implementation.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – DocuSign integration; electronic signatures; GenericDocuSign/sendEsignature; OmniStudio document workflow.

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

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.

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

An OmniScript plus Decision Matrix provides the correct declarative architecture. OmniScript captures the constituent's answers through a guided, dynamic digital form, while the Decision Matrix stores the changeable business criteria used to determine which license type corresponds to those inputs.

Salesforce describes a Decision Matrix as a table containing input and output values. When invoked, the matrix identifies the row matching the supplied inputs and returns the corresponding output. Because thresholds and policy values are stored declaratively in matrix rows, administrators can update city/county conditions, revenue bands, building-size thresholds, and resulting license recommendations without rewriting Apex.

Salesforce also provides direct integration between OmniScripts and Decision Matrices. An OmniScript can pass selected input values to the matrix and capture the returned result in its JSON structure. This is analogous to Salesforce's documented Public Sector pattern in which constituent inputs from an OmniScript are evaluated against Business Rules Engine criteria to produce eligibility or fee results.

OmniChannel is a work-routing capability, not a public questionnaire framework. Einstein AI isn't appropriate for deterministic regulatory rules. LWC plus Apex could work but creates unnecessary code and maintenance.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScripts; Business Rules Engine; Decision Matrices; declarative eligibility and recommendation logic.

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

An Integration Procedure is the appropriate OmniStudio component when a solution must retrieve, combine, transform, and calculate data from multiple sources without custom Apex. Integration Procedures execute server-side and can orchestrate multiple data-access and transformation operations before returning a consolidated response to a FlexCard, OmniScript, Lightning component, or another consumer.

Salesforce defines OmniStudio Integration Procedures as components that can read and write data between Salesforce and external systems , while Data Mappers handle Salesforce data retrieval, transformation, and persistence. Integration Procedures can invoke multiple Data Mappers, conditional actions, calculations, HTTP actions, and other services within one declarative process.

That orchestration capability is particularly important when the records being aggregated aren't connected through one simple Salesforce relationship. The Integration Procedure can independently query each required data set, calculate or transform the results, merge the outputs into a JSON response, and provide the resulting data to the presentation widget.

SOQL is a query language, not a standalone declarative OmniStudio orchestration component. Apex could implement the requirement but introduces unnecessary custom code. MuleSoft is appropriate for enterprise integration scenarios but is excessive when the required aggregation can be handled natively through OmniStudio.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; Integration Procedures; Data Mappers/DataRaptors; server-side orchestration; data aggregation and transformation.

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

The appropriate relationship is PersonAccount → Individual ← Employee . Salesforce's Employee data model uses the Individual object as the common privacy and identity relationship point connecting employee information to other person-centric representations.

Salesforce documentation states that Employee records are related to Individual records and that an Individual connects employee data with privacy and consent information. The Work.com data-model documentation further explains that when another Salesforce solution represents a person through a Person Account, the Person Account can be linked to the Employee through the Individual record—specifically, PersonAccount > Individual < Employee .

This arrangement is particularly appropriate when Public Sector represents an individual constituent as a Person Account while the Employee data model separately maintains an Employee record. The Individual object provides the linking layer rather than requiring the Person Account to connect directly to User or Employee.

Option B is a valid pattern for solutions that represent people through Contacts, but it does not satisfy the scenario's explicit Person Account requirement. Option D incorrectly routes the relationship through User, while option A does not even use the standard Employee object.

Study Guide Reference: Agentforce Public Sector – Product-Specific Systems Knowledge; Public Sector person data model; Employee data model; Person Accounts; Individual; Employee relationships.

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

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.

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

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.

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