Explanation:

Correct Options Explanation

✅ Option C: Person Accounts. Individual applications in Grants Management are designed for scholars (individuals, not organizations). Person Accounts must be enabled because they allow Salesforce to treat an account as both a company and a person. This makes it possible to handle applications from individuals (scholars) seamlessly.

Incorrect Options Explanation

❌ Option A: Salesforce Flow. While Flows may automate grant approval processes, enabling Flow is not a prerequisite for using the Individual Application object.

❌ Option B: Product Schedule. This feature deals with product revenue and installment tracking, which is unrelated to Grants Management.

❌ Option D: Custom Object for Applications. Salesforce already provides the Individual Application object out of the box in Grants Management. No need to create a new custom object.

🔗 Reference:
Salesforce Help – Person Accounts

Explanation:

The core requirement is to automatically map and set fees for a license application based on certain criteria (e.g., type of sporting event, number of participants, duration). This is a classic use case for a rules engine that evaluates input against a table of criteria to determine an output.

Let's evaluate why the other options are incorrect and why Decision Matrices are the correct tool:

A. Workflow Field Updates:
This is a legacy Salesforce automation tool. While it could update a field, its logic capabilities are very limited. It cannot easily handle the complex, multi-condition rules required to select from a list of possible fees based on application attributes. Workflow Rules are also deprecated and should not be used for new implementations.

B. Data Matrices:
This is a distractor. "Data Matrix" is not a standard, named Business Rules Engine tool within Salesforce or Public Sector Solutions. It may be confused with Decision Matrices.

C. Process Builder:
Like Workflow, Process Builder is a declarative automation tool, but it is also a legacy tool and is being phased out in favor of Flow. More importantly, while a Process Builder could technically be built to handle this with a long series of conditional decisions, it would be an incredibly complex, fragile, and hard-to-maintain solution. It is not the best or intended tool for this specific scenario.

D. Decision Matrices:
This is the correct answer. Decision Matrices are a core component of OmniStudio (the underlying platform for Public Sector Solutions) designed specifically for this purpose.
They function like a spreadsheet or a lookup table where you define input conditions (e.g., Application Type = "Marathon" AND Participants > 1000) and the corresponding output (e.g., Fee = $500).
They can be called directly from an OmniScript or a DataRaptor to automatically determine and set the fee when an application is created or updated.
This is a centralized, easy-to-maintain, and powerful rules engine that perfectly fits the requirement of "automatically map and set the fees."

Reference:
OmniStudio Decision Matrices: These are the declarative tool of choice for complex, criteria-based calculations and assignments within the Salesforce Industries (Vlocity) platform, which powers Public Sector Solutions.
Use Case: Decision Matrices are ideal for pricing, fee assignment, eligibility determination, and routing rules. They separate the business logic (the fee rules) from the automation process, making it much easier for administrators to update fees without redesigning entire Flows or Processes.

Explanation:

✅ Option D is correct because the requirement is fundamentally about controlling the registration method for the Experience Cloud site. This is governed by a single setting. Within the Digital Experiences setup menu (Workspaces > Administration), navigating to Settings reveals the "Self-Registration" option. Disabling this option is how an administrator "Enables manual registration." When self-registration is disabled, the only way to create new experience users is for an administrator to manually create them, fulfilling the requirement.

🔴 Option A is incorrect as it directly contradicts the requirement. Enabling self-registration would allow users to sign up themselves, which is exactly what the PSO wants to prevent.

🔴 Option B is incorrect. Adding the 'Register User' action to a contact layout is not a standard Salesforce action. The correct action for an administrator to manually enable a user from a Contact record is called 'Enable Customer User'. Furthermore, this option does not address the root requirement: disabling the self-registration capability on the site itself.

🔴 Option C is incorrect and describes the result of the configuration, not the configuration itself. Adding the 'Enable Customer User' action to the contact page layout is the method for manually registering users after self-registration has been disabled. However, the primary and essential configuration step is first to disable self-registration in the Digital Experiences setup menu. Option C misses this critical first step.

Reference:
Salesforce Help article "Control Self-Registration for Experience Cloud Sites". The process involves accessing the site's administration workspace and managing the registration settings to enforce administrator-mediated user creation.

Explanation

The problem is a classic record visibility issue for external (Experience Cloud site) users.

External Users and Sharing: Salesforce's security model for external users (like the Grantseekers in Public Sector Solutions) is much more restrictive than for internal users. They generally have Private access via the External Organization-Wide Defaults (OWD), and traditional sharing mechanisms like roles and sharing rules often don't apply.

Sharing Sets are the Solution: A Sharing Set is the standard, declarative tool designed to grant Experience Cloud users access to records associated with their Account or Contact record.

Since the support team is creating the Case on the user's behalf, the Case record is likely automatically related to the external user's Contact record (via the Contact Name field) and their Account record (via the Account Name field).

The Sharing Set will use a correlation, such as User.Contact = Case.Contact or User.Account = Case.Account, to automatically grant the external user (or anyone with that Experience Cloud profile) read access to the Case records created by the internal support team.

Why Other Options Are Incorrect

A. Change the Organization-Wide Default settings for Case to Public Read/Write: Changing the internal OWD to Public Read/Write is a massive security risk, granting all internal users access to all cases, which is unnecessary and likely against compliance rules. Changing the External OWD to Public Read/Write is also a massive security risk, granting all external users access to all other external users' cases.

C. Create or modify a permission set that gives access to Cases owned by the support team: Permission Sets control Object-Level access (e.g., can they see the Case object), not Record-Level access (e.g., which Case records they can see). The external users already have object access, but lack record access.

D. Create or modify a share group for the Profile used for the Site that gives access to Cases: Share Groups are primarily used to share records owned by high-volume community users with internal users (or partner users), not to share records owned by internal users with standard external users.

Explanation:

In Salesforce Public Sector Solutions, Action Plan templates are used to define standardized processes, such as inspection forms for licensing, permitting, and inspections. Once an Action Plan template is published, it becomes locked and cannot be edited. This is a deliberate design choice to ensure consistency and integrity in processes that are actively in use, as changes could disrupt ongoing inspections or licensing workflows. The System Administrator's inability to see the "Edit" button on the Action Plan template is due to this lock on published templates.

To make changes, the administrator must either:

Clone the existing template, make modifications to the cloned version, and publish it as a new template.

Deactivate the template (if possible, depending on its usage) and create a new version with the desired changes.

Why not the other options?

A. Edit option needs to be added to Action Plan template page layout

The absence of the "Edit" button is not due to a missing button on the page layout. The lock on editing published Action Plan templates is a system-level restriction, not a page layout configuration issue. Even if the button were added to the layout, the template’s published status would prevent edits.

B. System Administrator doesn't have "Edit" permissions to Action Plan template

System Administrators typically have broad permissions, including the ability to edit most objects, unless explicitly restricted. The issue here is not a lack of permissions but the system’s restriction on editing published Action Plan templates. Even with full permissions, the "Edit" button would not appear for a published template.

D. Action Plan template changes have to be requested to Salesforce support team

Changes to Action Plan templates do not require Salesforce Support intervention. Administrators can manage templates within the platform by cloning or creating new versions, as described above. This option is incorrect as it misrepresents the self-service capabilities of Salesforce Public Sector Solutions.

Reference:

Salesforce Help: Action Plan Templates in Public Sector Solutions. This documentation explains that published Action Plan templates are locked to maintain consistency and that changes require creating a new or cloned template.

Trailhead: Public Sector Solutions: Action Plans provides insights into managing Action Plans, including the limitation on editing published templates.

Additional Notes for Exam Prep:

For the Salesforce Marketing Cloud Email Specialist exam, understanding Public Sector Solutions’ features, like Action Plans, is relevant when dealing with licensing and permitting scenarios. Be familiar with how templates function and their lifecycle (draft, published, deactivated).

If the inspection team needs changes, the consultant should guide the System Administrator to clone the template, update it, and test it in a sandbox before deploying the new version.