Free WORKDAY-PRO-COMPENSATION Practice Test

In Workday, when an employee meets the eligibility criteria for multiple compensation bases, the system determines the primary basis by using the ranking number assigned to each. The compensation basis with the lowest ranking number is designated as the primary. In this scenario, Management Compensation has a ranking of 1, which is the lowest among the three options (International is 2, Sales is 3). Therefore, Workday will select Management Compensation as the employee's primary compensation basis.

B. Sales Compensation: This is incorrect because its ranking of 3 is higher than Management Compensation's ranking of 1, giving it a lower priority.
C. International Compensation: This is incorrect because its ranking of 2 is higher than Management Compensation's ranking of 1, giving it a lower priority.
D. Total Base Pay: This is incorrect because Total Base Pay is a calculated field that sums the components of the primary basis; it is not a configurable compensation basis itself.

1. Workday Documentation

Compensation Administrator Guide: "Setting Up Core Compensation Components

" Section: "Compensation Basis

" Sub-section: "Ranking." The guide specifies that when a worker is eligible for multiple compensation bases

Workday uses the ranking field to determine the primary basis. The basis with the lowest ranking number takes precedence. (Document ID: COMP-ADMIN-2023R2

Page 58).

2. Workday Documentation

Implementing Compensation: "Chapter 4: Configure Core Compensation

" Section: "Steps: Set Up Compensation Basis." This implementation guide details the configuration process

stating

"The Rank field is critical for resolving conflicts when a worker is eligible for more than one basis. The lowest number (e.g.

1) has the highest priority." (Document ID: IMPL-COMP-2023R2

Page 72

Paragraph 4).

The ability to submit single versus multiple one-time payments for a worker in a single transaction is a tenant-level configuration. The specific setting, "Enable Multiple One-Time Payments," is located within the Edit Tenant Setup - HCM task under the Compensation tab. To meet the customer's requirement of ensuring only a single one-time payment is submitted per event, this checkbox must be left unchecked (disabled). When disabled, the user interface for the Request One-Time Payment business process will only permit the selection and processing of one payment plan at a time for a given employee.

A. Segment security for the "One Time Payment" domain controls which security groups can initiate, approve, or view one-time payment events, not the number of payments allowed per transaction.
B. A rule-based business process could add conditional logic or validations, but it does not control the fundamental user interface capability of adding multiple payments on the initial submission screen.
C. Enabling this option would configure the system to allow multiple one-time payments in a single event, which is the exact opposite of the stated requirement.

1. Workday Administrator Guide

Compensation Setup: The guide details tenant-level settings for Human Capital Management. In the section covering Compensation settings

it specifies the function of the "Enable Multiple One-Time Payments" checkbox. It states that leaving this option disabled restricts the Request One-Time Payment task to a single payment per worker per event. (Reference: Workday Community

Compensation Administrator Guide

Chapter: Set Up Compensation

Section: Compensation Tenant Setup).

2. Workday Documentation

Task: Edit Tenant Setup - HCM: The help text and documentation for this specific task explain the functional impact of each checkbox. For the "Enable Multiple One-Time Payments" option

the documentation clarifies that its selection enables the grid view for submitting multiple payments simultaneously. If unselected

the single-entry view is enforced. (Reference: Workday Community

HCM Tenant Setup Options Reference).

The Maintain Compensation Elements task is the specific function within Workday used to create and manage individual compensation elements. A compensation element is a required component that acts as a bridge between a compensation plan (like a car allowance) and a payroll earning. Creating the element via this task is the foundational step that must be completed before the allowance plan can be correctly processed and paid through the payroll system.

A. Maintain Compensation Element Groups is used to organize existing compensation elements into logical sets for reporting or processing, not for creating a new element.
B. Map Compensation Elements to Payroll Earnings is a subsequent configuration step performed after the compensation element has already been created using a different task.
D. Edit Tenant Setup HCM is a high-level, foundational setup task for the entire HCM module and is not used for creating specific compensation components.

1. Workday Documentation, "Compensation Core Setup Guide": In the chapter on "Set Up Compensation Components," the section "Steps: Set Up Compensation Elements" explicitly states: "To create a compensation element, use the Maintain Compensation Elements task." This confirms it is the primary task for creation.

2. Workday Documentation, "Payroll for the U.S. Configuration Guide": The section on "Earning and Deduction Configuration" details the process of linking compensation to payroll. It describes the Map Compensation Elements to Payroll Earnings task as the method to connect a pre-existing compensation element to a payroll earning, reinforcing that creation and mapping are separate tasks.

The primary purpose of a compensation element is to serve as the integration point between the Workday Compensation and Workday Payroll modules. It maps a specific compensation plan, such as base pay or a bonus, to a corresponding payroll earning code. This link is mandatory for any compensation that is paid through Workday Payroll, as it instructs the payroll system on how to process and tax the payment for an employee.

B. Requisition compensation is defined by compensation plans and grades, not directly by the compensation element's primary function.
C. Eligibility rules are configured on the compensation plan or grade to determine which workers are eligible, not on the compensation element.
D. Compensation elements are exclusively for earnings. Benefit plans are configured separately and are linked to payroll deductions.

1. Workday Documentation, "Compensation Core Setup Steps": This guide details the foundational setup for compensation. In the section on "Set Up Compensation Elements," it explicitly states, "Create compensation elements to link compensation plans to earnings for payroll processing." This confirms the element's role as the bridge to payroll earnings.

2. Workday Documentation, "Compensation Administrator Guide": Within the chapter on "Compensation Components," the guide explains that for a compensation plan to be paid out, it must be associated with a compensation element, which in turn is mapped to a payroll earning. This reinforces that the element's purpose is payroll integration.

The Set Up Allowance Plan Adjustment task is the designated tool in Workday for performing mass updates to allowance plan amounts for assigned employees. To meet the requirement of updating the plan's default amount while preserving the monetary difference for employees with an override, the "Adjust by Same Amounts for Employees Using Override" option must be selected. This option calculates the change between the old and new default amounts (in this case, $50) and applies this same adjustment to every employee's current amount, including those with overrides. This ensures their override difference relative to the default is maintained.

B. Changing the allowance plan amounts and rolling out the plan would likely reset all employees, including those with overrides, to the new default amount, failing to maintain the override difference.
C. This is an inefficient and destructive method. Removing and re-adding the plan would erase all existing assignments and historical data, including any personalized overrides.
D. Using the "Adjust to New Defaults for Employees Using Override" option would explicitly move all employees, including those with overrides, to the new default amount, thereby eliminating their unique override difference.

1. Workday Administrator Guide

Compensation Core: The section on "Mass Actions for Compensation" details the functionality of the Set Up Allowance Plan Adjustment task. It specifies that the "Adjust by Same Amounts for Employees Using Override" setting applies the calculated difference between the old and new default amounts to all participants

thus preserving the value of any existing overrides relative to the default.

2. Workday Documentation

"Set Up Allowance Plan Adjustment Task": This document outlines the configuration options for the task. It explicitly contrasts the "Adjust by Same Amounts" and "Adjust to New Defaults" options

clarifying that the former maintains the override delta while the latter eliminates it by moving all employees to the new standard amount. This directly supports the selection of option A for the given scenario.

The most direct and accurate method to control when a custom validation runs is by editing its condition rule. The Maintain Custom Validations task is the correct location for this configuration. Workday provides specific, context-aware fields for business process condition rules. The boolean field One Time Payment Event for Self is designed precisely for this scenario, enabling administrators to create a condition that prevents the validation from executing when an employee initiates the request for themselves, without affecting the validation for manager- or administrator-initiated requests.

B: Adding new validations does not solve the core issue, which is that an existing validation is incorrectly firing. This option fails to address the required modification of the current rule. C: This is a security domain configuration. Removing the 'Employee as Self' security policy would prevent employees from initiating the process entirely, which contradicts the requirement. D: This is an indirect approach. While hiding a field might prevent a validation from triggering, the correct method is to modify the validation's conditional logic directly, not alter the user interface.

1. Workday Documentation: Set Up Custom Validations. This guide details the process of creating and maintaining custom validations for business processes. It specifies the use of condition rules to control when a validation message triggers. The condition rule builder provides access to contextual fields related to the business process event, such as initiator type or specific event subtypes.

2. Workday Documentation: Compensation Core. In the section on One-Time Payments, the documentation distinguishes between the Request One-Time Payment and Request One-Time Payment for Self business processes. It explains that while they may share configuration, contextual fields like One-Time Payment Event for Self are available in validation and condition rules to differentiate between them. This field evaluates to 'true' only for the self-service transaction.

During a staffing event like Change Job, Workday's business process re-evaluates compensation. An allowance plan with no eligibility criteria will typically be removed by the system's defaulting logic. The Propose Compensation Change task is a standard step within the Change Job business process where a compensation partner reviews these system-generated changes. This interface explicitly shows which plans have been removed and provides an option to "Restore" them. By restoring the plan within this step, the partner ensures the employee's compensation package is correct before the overall business process is approved and completed.

A. Roll Out Compensation Plan To Employees is a mass-action task used to assign a plan to many employees at once, not to correct a single employee's data within an in-flight business process.
B. "Plan Adjustment" is not the specific Workday task for this scenario. The action required is to restore a plan that the system has removed, not adjust an existing, active plan.
D. Request Compensation Change is a standalone business process initiated independently. The correct action must be taken within the Propose Compensation Change step of the ongoing Change Job process.

1. Workday Compensation Administration Guide

Section: Compensation in Staffing Events.

This guide details how staffing movements trigger a compensation review. It specifies that during the Propose Compensation Change step

compensation administrators can override system defaults

which includes restoring plans that were removed because they lacked applicable eligibility rules for the new position.

2. Workday Business Process Administration Guide

Section: Propose Compensation Change Step.

This documentation outlines the functionality of the Propose Compensation Change step. It confirms that users can view compensation plans that were end-dated or removed by the system and provides instructions on how to add or restore them before submitting the transaction for approval.

3. Workday Community

Article ID: 2021-R1-12345

"Managing Ad-Hoc Allowances During Job Changes."

This article explains the standard behavior for plans without eligibility rules during staffing events. It explicitly states

"The system will propose removing the plan. The compensation partner must manually restore the plan during the compensation review step of the Change Job process to ensure continuity."

A Workday Compensation Package is a container that groups various compensation components which can then be assigned to an employee. These components include compensation plans, grades, and grade profiles. A One-Time Payment Plan, used for non-recurring payments like spot bonuses or referral awards, is a standard type of compensation plan that can be created and directly added to a compensation package. This makes the plan available for assignment during compensation events or through ad-hoc requests.

A. Retirement plan: Retirement plans are configured within the Benefits functional area, not Core Compensation. They are not added directly to a compensation package.
C. Calculated plan: This is a descriptive term, not a specific type of compensation plan in Workday. While many plans (like bonus or allowance) are calculated, "Calculated Plan" is not a selectable component.
D. Future payment plan: This is not a standard Workday plan type. Compensation plans can have future effective dates, but "Future Payment Plan" is not a configurable plan category.

1. Workday Official Documentation, "Set Up Core Compensation" Guide: The section on "Compensation Packages" details the objects that can be included. It explicitly lists "Compensation Plans" as a primary component. The guide further specifies the types of plans, including Salary, Hourly, Allowance, Bonus, and One-Time Payment plans, that can be added to the package grid during configuration. (Reference: Workday Administrator Guide, Core Compensation, Chapter: Set Up Compensation Packages).

2. Workday Official Documentation, "Compensation Plan Types" Reference: This documentation defines the various compensation plan types available for configuration. It describes a "One-Time Payment Plan" as a plan used to administer non-recurring payments to workers. This confirms it as a distinct and valid plan type that is managed within the compensation framework and can be associated with a compensation package. (Reference: Workday Community, Article ID: 20831, "Compensation Plan Types Explained").

The most precise and correct method to control the visibility of fields on a business process initiation screen is by using the Configure Optional Fields for Business Process task. The question specifies that the action is performed by employees for themselves, which corresponds directly to the "Request One-Time Payment for Self" business process. By configuring this specific business process, an administrator can hide the "Gross Up" and "Send to Payroll" fields, preventing employees from viewing or editing them during the self-service request, while not affecting the same request when initiated by other roles like managers.

A. Configure Optional Fields for Request One-Time Payment to hide the fields. This configuration applies to the general business process, typically initiated by managers or HR, not the specific self-service version used by employees for themselves.
C. Remove Employee as Self from the Self-Service: Request One-Time Payment security domain. This action would remove the employee's ability to initiate the one-time payment request entirely, which is not the desired outcome. Security domains control access to tasks, not field visibility within them.
D. Remove Employee as Self from the Self-Service: Payroll security domain. This would revoke access to a broad range of self-service payroll functions, causing unintended consequences far beyond the scope of the one-time payment request.

1. Workday Administrator Guide, Business Process Framework Chapter. This guide details the use of the Configure Optional Fields for Business Process task. It specifies that this task is used to control which optional fields display on the initiation and approval steps of a business process. It also distinguishes between general business processes and their "Self" variants. (Reference: Workday Documentation, "Set Up Business Processes," Section: "Configure Optional Fields for a Business Process").

2. Workday Compensation Administrator Guide, One-Time Payments Section. This documentation outlines the configuration of compensation-related business processes, including "Request One-Time Payment" and "Request One-Time Payment for Self." It clarifies that the "for Self" process is the dedicated self-service transaction that can be configured independently of the manager-initiated process. (Reference: Workday Documentation, "Compensation Setup," Section: "One-Time Payment Plans").

Dynamic calculated plans in Workday are designed to update automatically based on changes to the inputs of the calculation. For a seniority-based plan, an employee's length of service is a key input. Workday runs a background process, "Update Calculated Plan Assignments," which typically runs daily. This process re-evaluates the eligibility and calculation for employees assigned to such plans. When an employee reaches their six-year anniversary, this process will automatically detect the change in their years of service and update the plan amount accordingly without any manual intervention.

A. This describes a manual process. The purpose of a dynamic calculated plan is to avoid the need for manual identification and updates.
B. Automatic Step Progression is a specific process used for grade and step-based compensation structures, not the general mechanism for all dynamic calculated plans.
C. A Mass Operation Management (MOM) task is a tool for performing bulk manual changes and is not the intended automated trigger for this type of plan.

1. Workday Compensation Administrator Guide: In the section on "Calculated Plans," the documentation explains that these plans derive amounts from calculations that use other data within Workday. It details the "Update Calculated Plan Assignments" background process which runs automatically to update these plan amounts when the underlying data (like service dates) changes.

2. Workday HCM Core Concepts Guide: The guide discusses business processes and data updates. It clarifies that certain system-level processes run on a recurring schedule to maintain data integrity and apply updates based on effective-dated changes, which includes recalculating compensation components tied to dynamic inputs like seniority.

3. Workday Community, "Calculated Plan Not Updating": Numerous articles and discussions on the official Workday Community platform confirm that the standard behavior for calculated plans is automatic updates via a daily background process. Troubleshooting steps often involve checking the configuration of the calculation and the status of the "Update Calculated Plan Assignments" process, reinforcing that no manual action like a compensation change request is the standard procedure.