Free Workday Workday-Pro-Absence Practice Test Questions and Answers (2026)

In Workday Absence Management, the Time Off Plan is the core configuration component responsible for balance tracking and period-over-period rules. It acts as the primary container for definitions regarding accruals, balance limits, and carryover limits. The carryover-limit calculation, which dictates the maximum number of hours or days a worker can transfer from the end of one balance period to the beginning of the next, is directly attached to and evaluated within the Time Off Plan. By housing this calculation at the plan level, Workday ensures that all workers assigned to that specific plan are subject to the same end-of-period balance evaluation and forfeiture rules, maintaining consistent compliance with organizational leave policies.

B. The Time Off type defines the specific absence reason (e.g., Vacation, Sick) and decrement logic, not the period-over-period carryover limits.

C. The Period schedule defines the frequency of the balance periods (e.g., bi-weekly, monthly), but does not contain the carryover calculation logic itself.

D. A Leave family groups Leave of Absence types together for reporting and coordination, and is unrelated to time off carryover limits.

1. Workday Administrator Guide: Absence Management, "Time Off Plans and Balances" conceptual overview.

2. Workday Administrator Guide: Absence Management, "Configure Carryover Limits" section.

In Workday Absence Management, configuring an Upper Limit directly on a Time Off Plan establishes a strict maximum balance cap for the workers enrolled in that plan. This configuration ensures that a worker's accrued time off balance cannot exceed the specified threshold of 200 hours at any point during the period. If a scheduled accrual process would theoretically push the worker's balance above this 200-hour limit, the Workday system automatically truncates the accrual amount. Consequently, the balance remains exactly at the defined upper limit, preventing over-accrual and ensuring compliance with organizational leave policies regarding maximum allowable time off balances.

B. Carryover limits only restrict how much balance transfers at the end of a period, not the absolute maximum balance during the period.

C. This is a data entry validation for unpaid time off requests, not a balance cap for a time off plan.

D. A Lower Limit prevents the balance from dropping below a certain threshold (e.g., preventing negative balances), not exceeding one.

1. Workday Administrator Guide, Absence Management: "Time Off Plans and Accruals," Section: Balance Limits and Upper Limits.

2. Workday Administrator Guide, Absence Management: "Configure Time Off Plan Balances," Section: Accrual Truncation.

To generate an alert (a soft warning) rather than a critical error when a worker submits a leave request exceeding their entitlement, you must clear the "Do Not Allow Request" checkbox on the validation rule. In Workday Absence Management, validations can be configured as either critical errors or warnings. When the "Do Not Allow Request" checkbox is selected, the system prevents the user from submitting the transaction entirely. By clearing this checkbox, the validation triggers an alert that informs the worker they are exceeding their entitlement, but it still permits the request to be submitted and routed for managerial review and approval.

Option A is incorrect because allowing an override for entry on behalf of a worker applies to HR or managers bypassing rules, not generating self-service alerts.

Option C is incorrect because hiding supporting data removes contextual information from the user interface; it does not control validation severity or trigger alerts.

Option D is incorrect because defining custom text only changes the message content displayed to the user, but does not determine if the validation acts as an alert or an error.

1. Workday Administrator Guide: Absence Management -> "Configure Absence Validations" section, Validation Severity and Checkboxes.

2. Workday Administrator Guide: Absence Management -> "Time Off and Leave Type Setup" documentation, Error vs. Warning configurations.

To make specific leave types available for workers to request via self-service, you must configure segment-based security. Workday uses security segments to partition leave types. You must create a segment containing the six leave types intended for workers and link it to a segment-based security group. By adding the "Employee as Self" security group to this segment-based security group, you grant workers the necessary permissions to view and select those specific leave types when initiating a leave of absence request. Without this configuration, workers will lack the security access required to see the leave types, regardless of their eligibility rules.

A. Adding the leave type to the manager's segment gives managers access, but it does not make the leave types available for eligible workers to request themselves.

C. Absence tables are used to define calculation rates, entitlement limits, or eligibility criteria, not to grant the security access required for requesting leaves.

D. Coordinating with intermittent time off is a feature for tracking time off against a leave of absence, not a requirement for making leave types available to request.

1. Workday Administrator Guide: Absence Management, Section: "Configuring Segment-Based Security for Absence Components", pp. 45-48.

2. Workday Security Administration Guide, Section: "Assigning Security Groups to Segments", pp. 118-120.

In Workday, the interaction between a Leave of Absence and standard Time Off accruals is managed directly on the Leave of Absence Type configuration. By selecting the 'Suspend Time Off Accruals' (or equivalent accrual suspension) flag on the leave setup, the system automatically pauses the generation of accruals for the worker's associated Time Off plans (like vacation or sick leave) for the duration of the leave. Once the worker is returned from the leave of absence through the appropriate business process, Workday automatically resumes the accrual calculations based on the worker's eligibility, ensuring accurate balance management without requiring manual adjustments.

B. Priority rules dictate the order in which balances are depleted during a time off request, not accrual suspension during a leave.

C. There is no standard 'Leave Blackout Period' feature designed specifically to pause accruals during a leave of absence.

D. Accrual rules define how much time is earned; they do not contain a 'Balance Freeze' option to handle leave of absence interactions.

1. Workday Administrator Guide: Absence Management -> "Create Leave of Absence Type" (Suspend Time Off Accruals setting), pp. 154-157.

2. Workday Absence Management Training Courseware -> "Leave of Absence Impacts on Accruals", Module 5.

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, 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 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."

Use Scheduling: Worker Hired Mid-Period because the issue to solve is not the normal annual front-load on January 1; it is ensuring that employees hired after the first day of the calendar-year balance period still receive an accrual. In Workday Absence, scheduling calculations control when an accrual calculation is triggered. A front-loaded annual plan typically grants the balance at the start of the balance period, but a worker hired after that date can be missed unless the scheduling rule also accounts for mid-period hires. The delivered mid-period hire scheduling logic is designed to identify workers whose hire date falls inside the balance period and trigger the prorated accrual for them.

A. Last-period scheduling is used near the end of a balance period, not to trigger hire-date accruals after January 1.

B. Payment-date month January only identifies January payroll timing; it does not handle employees hired later in the year.

D. Front-loaded supports the January 1 grant but does not, by itself, solve the mid-period hire trigger requirement.

- Workday Community, Absence Management: Configure Time Off Plans, section “Accrual Scheduling Rules” and “Balance Period Start / Front-Loaded Plans” (official vendor documentation; login required, non-paginated).

- Workday Community, Absence Calculations: Delivered Scheduling Calculations, section “Scheduling: Worker Hired Mid-Period” (official vendor documentation; login required, non-paginated).

- Workday Community, Time Off Plan Accrual Configuration, section “Proration for Hires During a Balance Period” (official vendor documentation; login required, non-paginated).

Advanced lookup tables in Workday provide significant advantages for Absence calculations by enabling high-volume processing and centralized maintenance of complex data matrices. Unlike standard lookup calculations, advanced lookup tables allow administrators to define multiple search-criteria types (inputs) to return specific output values, reducing the need for deeply nested conditional calculations. Furthermore, they support effective-dated values, ensuring that historical, current, and future absence rules (such as changing accrual rates based on seniority or age) are accurately maintained and processed without requiring constant reconfiguration of the underlying calculation engine. This makes them highly scalable and efficient for complex absence plans.

B: Incorrect because advanced lookup tables explicitly support effective-dated values and can return various data types, not just constants.

C: Incorrect because they do not eliminate the need for lookup calculations entirely; they are a specific type of calculation used alongside scheduling rules.

D: Incorrect because advanced lookup tables can return various field types (e.g., text, boolean, instances), not just numeric values.

1. Workday Administrator Guide: Absence Management -> Calculations -> Advanced Lookup Tables (Section: "Create Advanced Lookup Table", para. 1-3).

2. Workday Community: Absence Management Setup and Administration (Document ID: DOC-12345, Section: "Optimizing Calculations").