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.

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

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.

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

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.

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

Public Sector already includes a standard object specifically designed for this requirement: Business Regulatory Authorization Type Dependency . Salesforce states that many businesses require multiple licenses or permits and that dependency records establish the relationships and issuance sequence among those authorizations. A parent authorization must be obtained before its dependent child authorization where such a dependency is configured.

Salesforce additionally provides a standard Permits component for the Licenses and Permits Experience Cloud site. The component displays the permits required for a selected business type, including configured permit dependencies. Therefore, the agency does not need to develop a custom Permit Dependency object, custom FlexCard, or custom OmniScript merely to reproduce native functionality.

Option B consequently follows the standard Public Sector data model and minimizes custom technical debt while allowing administrators to maintain permit relationships declaratively.

The uploaded screenshot cuts off the final portion of option D. Its completed wording above was restored from a matching copy of the same item; the answer validation itself is based on Salesforce's official documentation .

Study Guide Reference: Public Sector Solution Product Configuration – Regulatory Authorization data model; Business Regulatory Authorization Type Dependency; parent and dependent permits; Permits Experience Cloud component.

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

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.

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

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.

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

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 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.

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

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 explicitly recommends setting Organization-Wide Defaults for Case to Private when configuring employee and HR-service solutions containing sensitive information. A Private OWD establishes the restrictive baseline: users don't automatically receive access to another employee's HR Case unless access is subsequently provided through ownership, queues, public groups, sharing rules, or another authorized sharing mechanism.

Salesforce's HR data-protection guidance is particularly direct. HR Cases may include payroll, benefits, leave, employee-relations, disciplinary, and other sensitive information. Salesforce recommends that such cases be accessible only to the case owner and the appropriate HR agent or HR group. It also specifically warns against mirroring the organizational chart into the Salesforce role hierarchy because managers could otherwise inherit visibility into records owned by employees beneath them.

The Employee Concierge installation similarly configures the Case object's organization-wide default to Private , reinforcing this as the standard security model for employee service records.

Option A would potentially broaden sensitive-data exposure. Option C isn't the appropriate Case security mechanism for this requirement, and disabling approval processes has no relationship to baseline record confidentiality.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Employee Experience security; HR Service Center; Case sharing; Organization-Wide Defaults; least privilege.

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