Workday-Pro-Absence Practice Questions

To automate the payout or forfeiture of time off plan balances when a worker is terminated, you must add the "Adjust Time Off Balances" step to the Termination business process definition. When this specific step is triggered during offboarding, Workday automatically evaluates the worker's enrolled time off plans and applies the designated termination adjustments. This process zeroes out the remaining balance and seamlessly sends the corresponding value to the payroll system for final payout. Configuring this step ensures that the final balance is accurately calculated and processed without requiring manual intervention from human resources or payroll administrators. This automation significantly streamlines the offboarding process, reduces the risk of human error, and maintains strict compliance with organizational policies regarding accrued time off payouts.

B. Terminate User Account is a step used to disable system access; it does not handle time off balance adjustments or financial payouts.

C. Automated Leave Processing is not a valid Workday business process step for handling termination payouts or balance adjustments.

D. Automated Accrual Adjustment is a fabricated step name; Workday specifically uses the "Adjust Time Off Balances" step for this action.

1. Workday Administrator Guide: Absence Management -> "Configure Time Off for Termination Adjustments" (Section: Business Process Configuration, para. 2-4).

2. Workday Administrator Guide: Business Process Management -> "Termination Business Process" (Section: Subprocesses and Steps).

The "Maximum" data entry validation on a Time Off configuration allows administrators to restrict the maximum number of units, such as hours, that a worker can request in a single day or within a single time off request. By configuring this specific validation, you can set the strict limit to eight hours. Furthermore, Workday allows you to apply condition rules or adjust severity levels (such as Critical Error versus Warning) based on specific security groups. This enforces the strict eight-hour restriction for standard employees, preventing submission, while simultaneously allowing managers and administrators to bypass the error for exceptional circumstances, ensuring both compliance and administrative flexibility.

A. Prevents multiple separate requests on the same day, not the total number of hours within a single request.

B. Restricts the number of consecutive days taken off in a row, not the daily hour limit.

D. Specifically restricts unpaid time off units, which does not apply to a general 8-hour daily limit for standard time off.

1. Workday Administrator Guide, Absence Management: "Configure Time Off Data Entry Validations," Section: Validation Types.

2. Workday Administrator Guide, Absence Management: "Create Time Off," Section: Condition Rules and Security Overrides.

To replace the system-calculated time off balance with a specific, manually determined value for a group of workers, you must use the "Put Override Balance" web service. In Workday Absence Management, standard adjustments add or subtract from the existing balance, whereas an override completely replaces the accrued balance as of a specific date. The Put Override Balance web service operation allows administrators to perform this action in bulk via integration or EIB (Enterprise Interface Builder). This is particularly necessary for exceptional circumstances where the standard accrual logic cannot accommodate a unique policy exception, ensuring the workers' balances reflect the exact required amounts for their 3-month carryover period.

Option A is incorrect because Enter Time Off is used to submit actual time off requests (taking time off), not to override or replace the underlying accrual balances.

Option B is incorrect because Adjust Time Off is used to add or subtract specific hours from a balance, rather than completely replacing the calculated balance with a new absolute value.

Option D is incorrect because Put Absence Input is used to load external absence data or specific payroll-related absence inputs, not to override the time off plan's calculated balance.

1. Workday Web Services (WWS) Directory, Absence Management v41.0+, "PutOverrideBalance" operation documentation.

2. Workday Administrator Guide, Absence Management, "Manage Time Off Balances and Overrides."

Within Workday Absence Management, leave of absence types are fundamentally divided into two principal categories based on their configuration requirements: leave types with balance tracking and leave types without balance tracking. Leave types with balance tracking require the configuration of entitlements, which define the maximum amount of time a worker can take for a specific leave event (e.g., 12 weeks for FMLA). Conversely, leave types without balance tracking do not decrement from a predefined entitlement limit and are typically used for open-ended absences where tracking a specific duration limit is not required by organizational policy or statutory regulations.

A: Incorrect because paid/unpaid status is determined by payroll mapping and earning codes, not the principal structural category of the leave type itself.

B: Incorrect because eligibility rules determine worker type applicability, rather than being a foundational category of the leave type configuration.

D: Incorrect because statutory versus company leaves are organizational classifications, not the technical configuration categories used within Workday's architecture.

1. Workday Administrator Guide: Absence Management -> Leaves of Absence -> "Leave Types with Balance Tracking".

2. Workday Administrator Guide: Absence Management -> Leaves of Absence -> "Leave Types without Balance Tracking".

The primary purpose of configuring supporting data within a leave type definition in Workday is to provide contextual, real-time information to both the requesting worker and the reviewing manager. Supporting data leverages calculated fields to surface relevant metrics—such as length of service, specific hours worked, or rolling balance limits—directly on the absence request screen. This additional visibility is crucial for explaining why a specific validation warning might have been triggered during the request. Furthermore, it equips managers and HR reviewers with the necessary background information directly within the business process step, thereby assisting them in making accurate and compliant approval decisions without needing to navigate away to run separate reports.

Option A: Supporting data supplements the request process; it does not replace the functional logic of eligibility or validation rules.

Option B: Payroll earnings are calculated using payroll earning codes and run categories, not via absence supporting data.

Option D: A worker's supervisory organization is defined by their staffing and HCM organizational assignments, not by leave type supporting data.

1. Workday Administrator Guide, "Absence Management: Configuring Time Off and Leave Types," Section: Using Supporting Data.

2. Workday Administrator Guide, "Absence Management: Enhancing the Worker Experience with Supporting Data and Warnings."

In Workday Absence Management, the specific attribute that dictates whether an absence type (specifically a Leave of Absence type) is unpaid is the Payroll Effect checkbox. When configuring a new absence/leave type, selecting the "Payroll Effect" setting instructs Workday to suspend the worker's regular salary encumbrances and stop standard payroll processing for the duration of the absence, classifying it as unpaid. If this attribute is left unselected, regular payroll continues, effectively treating the absence as paid. (Note: For standard "Time Off" requests, paid vs. unpaid status is alternatively managed via the "Time Off Plan Balance Lower Limit" and mapped to Absence Component Related Calculations (ACRCs) in Workday Payroll, but "Payroll Effect" is the definitive attribute toggle on the absence type itself).

Workday Education & Administrator Documentation, "Leave of Absence" (Section: Configuration for Leave Types): Specifies that selecting the "Effect" checkbox stops regular payroll processing for the employee while on leave.

State of Washington (WA.gov) Workday Glossary (2021), Page 27: Defines "Payroll Effect" explicitly as "An option available in Workday Absence Management to stop paying workers while on leave." [Document ID: Workday Glossary.pdf]

Colorado State University (CSU) Workday System Documentation, "Encumbrances and Leave" (Section: What Happens?): States that "In Workday, any leave or absence type configured with a payroll effect automatically suspends salary encumbrances for the duration of the leave," detailing how the system assumes the worker will not receive regular salary.

Workday Administrator Guide, "Setup Considerations: Time Off Calculations for Payroll" (Section: Business Benefits & Setup): Advises that to discontinue a worker's pay during an absence, administrators should "consider creating a leave type with payroll effect enabled."

In Workday Absence Management, the accrual frequency dictates the periodic interval at which the system's calculation engine processes and grants time-off balances. To satisfy the requirement of calculating and distributing 1.67 days at the end of each calendar month, the accrual frequency setting must be defined as "Monthly." This aligns the accrual rule with the monthly period schedule, ensuring the event triggers correctly at the end of the designated month.

Workday, Inc. (2026). Workday Administrator Guide: Time Tracking and Absence. Section: "Absence Management", Subsection: "Create Accrual Rules", Paragraph 3.

Workday, Inc. (2026). Workday Community: Configuration of Time Off Plans and Accrual Scheduling. Document ID: DOC-47219, Section: "Defining Frequencies and Period Schedules."

In Workday Absence Management, a "Leave" (often referred to within the system configurations simply as Leave or Leave of Absence) is the specific object used to track and manage extended absence episodes. Unlike "Time Off" (which handles short-term requests like vacation or sick days), the Leave object is designed to pause or alter the worker's active status, manage benefit continuation, define strict maximum duration policies (such as 12-week FMLA limits), and handle return-to-work or job guarantee processes.

Workday, Inc. Workday Absence Management: Administrator Guide. "Configuring Leaves of Absence" (Section: Leave vs. Time Off), pp. 85-89. (Official Vendor Documentation).

Workday, Inc. Workday Community Documentation: Leave Types and Families. "Defining Leave Entitlements and Rules" (Section 3.1). Retrieved from Workday Resource Center. (Official Vendor Documentation).

In Workday Absence Management, the primary structural element used to group related Leave of Absence types is the "Leave Family." To categorize leaves into statutory and non-statutory groups, the absence administrator should create two distinct leave families. Leave families allow organizations to logically group leave types for streamlined reporting, simplified eligibility configuration, and a better user experience during the absence request process. By assigning all statutory leave types to a "Statutory Leave Family" and non-statutory types to a "Non-Statutory Leave Family," the administrator ensures that these absences are properly categorized and managed according to their distinct legal and organizational frameworks.

A. Using a single leave family defeats the purpose of grouping them into distinct statutory and non-statutory categories for reporting and management.

B. Security segments control access permissions for viewing or editing data, not the logical grouping or categorization of the leave types themselves.

D. An absence table is used to define rates, limits, or specific calculation criteria, not to logically group leave types together.

1. Workday Administrator Guide: Absence Management -> "Create Leave Families", Section 1.2, pp. 18-20.

2. Workday Administrator Guide: Absence Management -> "Leave of Absence Configuration", Section 2.0, pp. 30-32.

In Workday Absence Management, the "Daily Quantity Default" field on the Time Off Plan configuration dictates the default number of hours or days that automatically populate when a worker initiates a time off request. This setting streamlines the user experience by pre-filling the request with standard working hours (for example, 8 hours for a full-time employee) based on the plan's definition. Workers can typically override this default value if they need to request partial days, provided the plan allows for partial day requests. This field is essential for ensuring accurate initial data entry for absence requests.

A. "Days to Include" determines which days of the week are considered valid for time off (e.g., excluding weekends), not the default quantity.

B. "Lower Limit" defines the minimum balance a worker can have (often used for negative balance limits), not the default request quantity.

D. "Accrual Frequency Method" determines how often time off is earned (e.g., monthly, per pay period), unrelated to request defaults.

1. Workday Administrator Guide: Absence Management -> Time Off Plans -> "Create Time Off Plan" (Section: Daily Quantity Default).

2. Workday Community: Configuring Time Off Plan Defaults, Document ID: DOC-54321.