Workday Pro HCM Core Exam Questions

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.

The correct answers are C -- Position Management and D -- Job Management.

In Workday, supervisory organizations can only use one of two delivered staffing models:

Position Management: Each position is a distinct entity that must be created and approved before hiring. It supports detailed tracking of vacancies and headcount.

Job Management: Hiring is managed at the job level, allowing multiple workers to be hired under a single job requisition without individual position control.

Workday does not deliver ''Headcount Management'' or ''Customer Defined Staffing Models'' as valid options. The staffing model is selected when creating or editing a supervisory organization and determines how headcount, hiring, and reporting are managed.

When a security group initiates a business process, what the group can do during that initiation is controlled through business process security for the relevant business process type. In this case, the Manager security group should be able to initiate Termination but only update limited termination information, specifically termination dates and reasons. That is a business process security configuration requirement, not a general domain-reporting issue. The appropriate configuration is to locate the Termination business process type and adjust the security permissions accordingly so that the Manager group has only the correct initiating action and section-level access. The consolidated template option is incorrect because the requirement is not about consolidating approval tasks. Domain security can control access to data broadly, but this question concerns what fields or sections can be used during a specific Termination initiation flow. View Security for Securable Item can help analyze a field's security, but it is not the configuration task that grants or restricts the Termination initiation experience. Therefore, the Termination business process type security configuration is correct. Reference topics: Security, Business Process Security, Initiating Action, Termination, and section-level permissions.

In Workday, period salary plans are specifically designed to support countries where employees are legally entitled to additional salary payments, such as a 13th or 14th month salary. These plans allow organizations to define compensation based on a number of salary periods, rather than assuming a standard 12-month structure.

By configuring a period salary plan with an additional month, Workday can correctly calculate and distribute base pay across the required number of periods while still maintaining accurate annualized compensation values. This approach ensures compliance with local legislation while preserving consistent reporting and budgeting.

Percent-based merit plans are used for increases and do not address structural pay requirements. Allowance plans are not considered base pay and are not appropriate for statutory salary obligations. One-time payment plans are ad hoc and do not satisfy recurring legislative requirements.

Period salary plans integrate seamlessly with payroll, compensation bases, and grade profiles, making them the correct and compliant solution for legislated additional pay months.

Therefore, option A is the correct answer.

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.