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.

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

The page component being present does not itself grant access to Decision Explainer functionality. The administrator must also ensure that the caseworker has the required Decision Explainer access. Therefore, A is the intended answer.

Current Salesforce documentation refers to Decision Explainer Service Access when describing the permission required by internal users to work with Decision Explainer entities and review decision information. Salesforce also documents a Decision Explainer Permission Set License as the entitlement that provides access to Decision Explainer features. The terminology in the question is therefore slightly simplified, but its technical intent is unambiguous: verify that the caseworker is authorized for Decision Explainer.

OmniStudio Admin provides configuration capabilities for OmniStudio components and is excessive for an ordinary caseworker. OmniStudio User enables runtime access to OmniStudio processes but does not specifically authorize Decision Explainer logs. Rules Engine Runtime permits execution of business rules; it does not by itself grant access to the Decision Explainer interface or its underlying records.

Study Guide Reference: Public Sector Solution Product Configuration – Decision Explainer permissions, Decision Explainer Service Access, Business Rules Engine integration, and decision-log visibility.

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

Grants Management provides native Funding Request Collaboration , making Invite Collaborators the correct design rather than implementing an email-based or custom collaboration mechanism.

Salesforce allows applicants to invite other people to collaborate directly on a Funding Request. The invitation contains a secure, time-limited link. After the invitee accepts it and has the appropriate portal identity, that collaborator can participate in completing the Funding Request. Administrators enable this capability through the Grants Management settings and configure the collaborator invitation URL, expiration period, certificate, and associated email template.

Salesforce also provides a Manage Collaborators component on Funding Requests. From this component, authorized users can invite collaborators, view pending and confirmed collaborators, and remove access when necessary. The solution also contains automation for controlling the collaborator's access to the Funding Request.

This directly satisfies the requirement for application collaboration without creating a parallel data or communication model. Option A relies on email and loses the controlled application-level collaboration experience. Option B creates unnecessary custom metadata and does not provide collaboration. Option C relies on a feed rather than the purpose-built collaborator-access capability and would not independently provide secure external access.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Funding Request Collaboration; Invite Collaborators; Manage Collaborators; grants portal security.

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

The requirement maps directly to the OmniStudio component architecture. Salesforce describes OmniStudio as the no-code/low-code suite used in Public Sector to create guided, responsive constituent applications and workflows that consume Salesforce and external data. Its principal components include OmniScripts, Integration Procedures, FlexCards, and Data Mappers , historically referred to as DataRaptors.

OmniScripts create the application-form experience. They support dynamic questions, conditional sections, navigation, validation, document collection, saved sessions, and guided application processes. Salesforce specifically states that Public Sector uses OmniScripts for applications involving licenses, permits, benefits, services, and grants.

DataRaptors/Data Mappers retrieve, transform, and save application data. Integration Procedures perform server-side orchestration and connect forms to other Salesforce or external data sources. FlexCards display contextual information and actions in compact, reusable user-interface components.

Together, these capabilities support complex application structures while allowing the agency to closely reproduce its paper application process and apply Experience Cloud branding without building the entire solution in Apex or custom Lightning Web Components.

The alternatives contain either unrelated products or unnecessarily code-intensive technologies.

Study Guide Reference: Public Sector Solution Product Configuration – OmniStudio; OmniScripts; DataRaptors/Data Mappers; Integration Procedures; FlexCards; Experience Cloud application forms.

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

Customer Community is the correct license because this is an extremely high-volume business-to-consumer Experience Cloud scenario. Salesforce explicitly categorizes Customer Community users as high-volume external users and describes the license as appropriate for large populations requiring limited access to Salesforce CRM functionality.

The decisive requirement is scalability beyond 100 million users . Salesforce's Experience Cloud licensing guidance states that Customer Community or External Apps licenses can support 100+ million users , whereas role-based licenses such as Customer Community Plus, Partner Community, and Channel Account are designed for more sophisticated sharing requirements and generally operate at lower standard user scales.

Customer Community users do not participate in the normal external role hierarchy. Eliminating those role calculations is precisely what allows the high-volume user architecture to scale efficiently. That design is appropriate where constituents primarily access their own data and execute defined portal transactions.

Customer Community Plus should be selected when external users require advanced sharing, reports, dashboards, and role-based access—not simply because they use authenticated portal functionality. Partner Community and Channel Account are primarily B2B/partner-oriented models and are inappropriate for the mass constituent population described.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud architecture, external-user licensing, high-volume user design, scalability, and sharing models.

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