In Workday, allowance plans include a No Override configuration option that prevents users from manually changing the plan amount during staffing or compensation events. When this checkbox is selected, the plan amount is strictly controlled by the plan default or plan profile value.

Even if a recruiter has appropriate security and the candidate is eligible for the allowance, the presence of No Override enforces compensation governance and prevents deviations from defined policy.

Ineligibility would prevent the plan from appearing at all, and multiple plan profiles would cause defaulting issues—not override restrictions. If the plan were not included in the compensation package, it would not be visible.

Therefore, the recruiter cannot change the amount because the No Override checkbox is selected, making option A correct.

By default, Workday allows only one one-time payment per event when the Enable Multiple One-Time Payments tenant setting is not enabled . This behavior ensures strict control over one-time payment submissions and prevents multiple payments from being entered within the same transaction.

The Enable Multiple One-Time Payments setting in Edit Tenant Setup – HCM > Compensation explicitly removes this restriction and allows users to submit multiple one-time payments with the same reason and effective date. Since the business requirement is to limit submissions to a single payment , this setting must remain disabled .

Security configuration and business process rules do not control the number of one-time payment rows allowed in an event. They only manage access and approval flow.

Therefore, to enforce a single one-time payment per event, administrators must not enable the Multiple One-Time Payments setting , making option B correct.

In Workday HCM, changes made to security policies , including business process security policies , follow a two-step lifecycle: save and activate . When you edit a business process security policy—such as granting a security group permission to initiate a business process event—those changes are initially saved only . At this stage, the changes exist in the tenant but are not yet active or enforced .

Workday requires administrators to explicitly run the Activate Pending Security Policy Changes task to make any saved security updates effective. This design ensures controlled deployment of security changes and allows administrators to review, bundle, and activate multiple security updates at once. Until activation occurs, users will not experience any change in access or behavior.

Option B is incorrect because Workday does not automatically activate security policy changes. Option A is incorrect because saving a security policy does not generate an error; it simply leaves the changes inactive. Option D is incorrect because Security Evaluation Moments are system-defined events used by Workday to re-evaluate security, but they are not created automatically as a result of editing a policy.

From a Workday Pro HCM best-practice standpoint, administrators should always validate security updates by confirming that pending changes are activated and tested. Failing to activate pending changes is a common reason why expected access updates do not take effect.

Therefore, without further action, the correct and Workday-verified status is that your changes are saved, but not in effect until they are activated.

In Workday HCM, business process security controls which security groups can participate in specific steps within a business process definition. Each step type—such as approval, review, or To Do—requires explicit permission for a security group to be eligible for selection. If a security group does not appear as an option when configuring a review step , it means the group has not been granted permission to act on that type of step.

To resolve this issue, you must update Who Can Do Action Steps in the Business Process . This section of the business process security policy defines which security groups are authorized to perform step-level actions , including review, approve, or to-do actions. Once the appropriate security group is added here and the changes are activated, the group becomes available for selection on the review step.

The other options do not address this requirement. Policy Restrictions control conditional logic and constraints, not step eligibility. Who Can Start the Business Process governs initiation permissions only and does not affect step assignment. Who Can Do Actions on Entire Business Process grants high-level actions such as cancel or rescind but does not authorize participation in individual steps like reviews.

From a Workday Pro HCM best-practice perspective, configuring Who Can Do Action Steps in the Business Process ensures precise control over step participation while maintaining separation of duties. After updating this section, administrators must remember to run Activate Pending Security Policy Changes for the update to take effect.

Therefore, the correct and Workday-verified answer is Who Can Do Action Steps in the Business Process .

Workday provides the Rollout Compensation Plans to Employees task to efficiently assign newly created compensation plans to employees who meet defined eligibility criteria. This task evaluates the eligibility rule attached to the plan and assigns the plan to all qualifying employees in bulk.

Manual approaches such as Request Compensation Change or Change Job events are inefficient and not scalable. The View Compensation Plan Rollout Process task is informational and does not perform assignments.

Using the rollout task ensures consistency, reduces administrative effort, and aligns with Workday best practices for plan deployment.

Therefore, option D is the correct answer.

When configuring Business Process Notifications in Workday, administrators can define the recipient based on a specific Workday Account . This allows precise targeting of individuals or security groups (e.g., HR Partner, Manager, or specific role-based accounts) who should receive the notification.

Option D is correct because “Recipient based on Workday Account” ensures the system routes the notification to the appropriate user or group dynamically, based on the context of the business event. This is essential for process transparency and timely action.

Option A ( Sender based on Workday Account ) is incorrect — the sender is system-defined (“Workday Notification”), not configurable by user account.

Option B ( On exit ) and Option C ( Trigger on In Progress ) are not valid notification configuration options; triggers are defined by process status changes such as “Awaiting Action,” “Completed,” or “Denied.”

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Business Process Notifications and Recipient Configuration.”

In Position Management, a position can be made temporarily unavailable for staffing without permanently closing or deleting the position. The task designed for this purpose is Manage Position Freeze. A position freeze prevents the position from being filled while preserving the position record, restrictions, and future availability for planning purposes. This is useful when hiring is paused for budget, approval, or timing reasons but the organization does not want to remove the position from the structure. Edit Position Restrictions is used to change allowed staffing values such as job profile, location, worker type, time type, or worker subtype; it does not freeze staffing availability. Edit Position changes position details, but it is not the specific task for temporarily blocking hiring. Close Position is a stronger and more permanent action that removes the position from availability because the position is no longer needed. The scenario clearly says temporarily unavailable to fill, which matches a freeze, not a close. Therefore, Manage Position Freeze is correct. Reference topics: Staffing, Position Management, Position Restrictions, Position Status, and Manage Position Freeze.

In Workday, configurable compensation bases allow organizations to control how compensation plans relate to one another and to enforce limits or proportions within a total compensation structure. The Manage Basis Total option is specifically designed to impose constraints on how much certain plan types can contribute relative to the overall compensation basis.

In this scenario, the business requirement is to ensure that salary plans do not exceed 50% of the total compensation for Indian employees. This requirement is achieved by enabling Manage Basis Total on the Total Cost (India) compensation basis and setting a maximum percentage of 50 for salary plans . This configuration enforces the rule automatically during compensation proposals and validations.

Changing the ranking of the compensation basis has no impact on percentage enforcement; rankings only determine precedence when multiple bases apply. Fixed compensation bases do not support proportional controls and would remove flexibility. Removing retirement plans would alter the total compensation calculation but would not guarantee the 50% salary cap.

Therefore, configuring Manage Basis Total with a salary plan maximum of 50% is the correct and Workday-recommended solution to enforce this business rule, making option B the correct answer.

The correct answers are B , D , and E .

User-based security groups are groups in which membership is manually assigned to individual users. They are highly flexible and used primarily for administrative or elevated-access purposes.

(B) These groups can be either constrained or unconstrained . Constrained groups limit data access (for example, access only to workers in a particular supervisory org), while unconstrained groups provide broad system-wide visibility.

(D) These groups are commonly used for system administrators, payroll admins, or HR system owners , who require full access across tenants.

(E) Once a user is assigned to a user-based group, they automatically inherit access to all domains and business processes that the security group has permissions for.

Option A is incorrect because user-based groups are not always unconstrained; and C is incorrect because assigning users does not initiate a business process —it’s a configuration action managed through the Maintain Security Group Members task.

In Workday, when updating allowance plan target amounts, administrators must carefully manage how the change impacts employees who are assigned override amounts . Overrides represent intentional deviations from the plan default, and preserving those differences is often a business requirement.

The Set Up Allowance Plan Adjustment task provides specific options for handling overrides. The option Adjust by Same Amounts for Employees Using Override increases each employee’s allowance by the same delta as the change to the plan default. In this scenario, the default increases from $150 to $200, a difference of $50 . Employees with override amounts will also receive a $50 increase, thereby preserving their original variance from the default.

Selecting Adjust to New Defaults would eliminate the override difference by resetting employees to the new default amount, which contradicts the requirement. Removing or re-rolling out the plan introduces unnecessary disruption and risk.

Therefore, the correct approach is to use the Set Up Allowance Plan Adjustment task and select Adjust by Same Amounts for Employees Using Override , making option D correct.