Free Practice Questions for the Workday Payroll, Absence, and Time Tracking Workday-Pro-Absence Exam (2026 Updated)

A Date Difference calculation returns the elapsed interval between two dates as a numeric value. Workday supports intervals such as years, months, days, hours, minutes, or seconds, depending on the calculation context. For this requirement, the calculation uses the worker’s hire date and the applicable period start date and returns the completed number of years between them.

That numeric result can then drive service-based accrual logic. For example, the value may be evaluated directly in a conditional calculation or used as search criteria in a numeric lookup table to return different accrual rates for workers with fewer than five years, five through nine years, or ten or more years of service.

A Date Extract calculation returns only a component of one date, such as its year or month; subtracting extracted calendar years can produce an incorrect service result when the employment anniversary has not yet occurred. A Lookup calculation returns a configured value after criteria have already been calculated, while a Conditional calculation selects a result based on conditions. Neither independently calculates the elapsed years. The Date Difference calculation is therefore the correct foundational numeric calculation for determining service duration.

The carryover limit is configured as part of the time off plan’s balance information. It determines the maximum quantity of unused hours or days that Workday can transfer from one balance period into the next. The limit can be represented by a constant, such as 80 hours, or by a calculation that derives the permitted carryover from another value, such as a percentage of the closing balance. Any units exceeding the calculated limit are treated as carryover forfeited and are available for reporting.

The period schedule does not establish the carryover ceiling. It determines processing periods, accrual frequency, and period start and end dates. A time off type is the user-facing category presented when entering or viewing a time off request. A leave family groups related leave types and does not govern time off plan carryover. Consequently, the time off plan is the only component among the options that owns the carryover date, carryover-limit calculation, expiration rules, and related balance-processing behavior.

The user-facing category displayed in the time off request prompt is the Time Off Type name, which is configured through the Maintain Time Off Types task. Workday describes time off types as categories that group one or more underlying time off definitions. For example, a user may see “Vacation” in the request prompt even though the configuration contains separate underlying time offs for full-time and part-time workers.

This separation provides a cleaner employee experience while allowing administrators to maintain different eligibility rules, validations, plan associations, or calculation behavior behind the same visible category. The worker sees the time off type that applies to the request, while Workday resolves the eligible underlying time off based on configuration.

The Name field on the Create Time Off task identifies the individual time off component; it does not determine the category name presented in the selection prompt described by the question. A time off plan name identifies the overall plan and balance structure rather than the request category. The Code field is an administrative identifier and is not the requested user-facing label. Therefore, the required name is maintained in the Name column of Maintain Time Off Types.

The Visible for Team Absence setting determines whether an absence type is displayed on the Team Absence Calendar. To prevent sick leave from appearing, the administrator must leave this option cleared for the sick leave when using the Configure Team Absence task. Authorized administrators can continue managing the underlying leave event through secured absence reports and tasks, while the team calendar omits the sensitive absence.

Workday does not automatically classify and hide every sickness-related leave. Privacy requirements vary by jurisdiction and organization, so calendar visibility must be deliberately configured. Leaving the option cleared provides direct control over whether the leave is exposed in the shared team view.

Leave type segmented security controls which leave types designated security roles can request or administer. It is not the calendar-display control and should not be used as a substitute for Team Absence visibility. Removing a leave from a security segment could interfere with legitimate manager or administrator processing without reliably implementing the intended calendar behavior. It is also incorrect that leave types cannot be hidden: the Visible for Team Absence setting exists specifically to control inclusion. Clearing that option is therefore the appropriate privacy configuration.

A leave type is the central configuration object governing a specific form of leave of absence. It defines the rules that apply when a worker requests or is placed on personal leave, bereavement leave, short-term disability, parental leave, or another extended absence.

The configuration identifies the associated leave family, the unit of time used for the request, eligible worker populations, additional eligibility criteria, validation rules, entitlement structure, and whether Workday tracks an entitlement balance. It can also control the On Leave status visibility, calendar display, Days to Include calculation, payroll effect, benefit effect, accrual effect, and other cross-functional consequences. For balance-tracking leave types, the definition additionally includes balance-calendar dates and entitlement calculations.

A period schedule belongs to time off plan configuration rather than leave type configuration. Supervisory organization membership is determined through HCM organization and staffing structures, while payroll calendars and pay-period processing belong to Payroll. Therefore, the leave type’s defining function is to assemble the policy, eligibility, validation, entitlement, visibility, and processing rules for one specific category of leave.

Leave type segment security controls which leave types specific roles can access when placing workers on leave. Four coordinated security elements are required.

First, the Request Leave of Absence business process security policy identifies the security groups permitted to initiate relevant actions. Second, the leave type security segment groups the leave types requiring distinct access—for example, leave types that only managers may initiate. Third, a segment-based security group associates the permitted roles or security groups with that leave type segment. Fourth, the group must receive View or Modify access through the Leave Type Segmented Setup domain.

Creating only a leave type security segment does not grant access. It defines the protected collection, but the segment-based group establishes who receives access, and the domain policy supplies the actual privileges. Business process initiation security remains necessary because access to the leave type does not independently authorize a user to start the request process.

Leave families and absence type groups organize selections rather than enforce segmented access. Eligibility rules determine worker qualification, not the initiator’s security permissions. Therefore, option D contains the complete security architecture.

Calculated fields can be used directly or indirectly throughout leave-of-absence configuration. Direct uses include displaying calculated information as supporting data and determining entitlement quantities. Supporting data might calculate months of service, actual hours worked, or an available leave balance so that requesters and reviewers can understand the circumstances surrounding a request. Entitlement calculations can return different leave quantities based on worker or position attributes.

Calculated fields are also used indirectly through leave-of-absence rules. An eligibility rule can reference calculated fields based on the Worker or Position business object to determine whether a worker can select a leave type. A validation rule can use calculated fields to evaluate a submitted request and generate either a warning or an error.

Calculated fields are resolved at runtime rather than permanently storing their results. They can perform date calculations, retrieve related values, manipulate text, evaluate logical expressions, or transform existing data. Balance-calendar dates are another valid application, but they are not the only use. Payroll effects, leave-family names, and absence-type display labels do not represent the complete calculated-field usage model.

A Value Comparison Calculation can create the Boolean conditions that identify whether a worker’s resolved work-state value equals California or Illinois. One comparison can test whether the work-state calculation equals California, and another can test whether it equals Illinois. These Boolean results are then referenced by the conditional calculation that returns the appropriate accrual rate.

A Lookup Calculation could return a value directly from a lookup table, but the stated solution separates the state-identification conditions from the calculation that specifies the accrual amounts. An Instance Value Calculation retrieves a value from a related instance but does not, by itself, evaluate whether that value matches California or Illinois. An Instance Set Comparison is principally used to compare a class report field or instance collection with user-selected instances; it is not the intended comparison when the worker’s state has already been resolved into a calculation value.

The conditional accrual calculation should evaluate the California condition first, return 12 hours, then evaluate the Illinois condition and return 10 hours. Workers who meet neither condition receive the default response of eight hours.

Study Guide reference: Calculations for Time Off Plans – Boolean and Value Comparison Calculations .

The leave must maintain a distinct 180-day entitlement for each birth event. Selecting Entitlement per Event directs Workday to grant and track an entitlement for each separate qualifying event rather than treating all requests within the balance calendar as one shared entitlement. However, Workday also needs an event-specific value that distinguishes one child’s birth from another.

Configuring Child’s Birth Date as an additional field provides that event identifier. When a worker has more than one birth within the same rolling-forward 12-month window, the different birth dates allow Workday to associate each request with the appropriate event-specific entitlement. The combination prevents requests related to separate births from consuming a single undifferentiated balance.

A validation rule can restrict request behavior but does not establish multiple event balances. Child’s Birth Date by itself captures supporting information but does not instruct Workday to create an entitlement for every event. Conversely, Entitlement per Event without the identifying additional field does not provide the required data for distinguishing the births in this scenario. Both configurations are necessary: the additional field identifies the event, and Entitlement per Event establishes separate entitlement tracking for it.

Start and stop time entry is configured on the time off component before that component is associated with the intended hours-based time off plan. In the Create Time Off task, the administrator selects the appropriate entry option and enables Display Start and End Time. Workday then exposes Start and End Time Required, which makes both values mandatory when a requester enters the time off. An additional option can calculate the requested quantity from the interval between those times.

The configuration must align with the plan’s unit of time. An hours-based plan is the appropriate design when the business requirement depends on precise clock times and a calculated duration. Although Workday can display start and end times in several request contexts, the selected time off, accruals, limits, and calculations attached to a plan must remain compatible with that plan’s unit of time. Workday does not automatically convert day-based configuration values into hourly values.

Configuring the requirement before adding the time off to the hours-based plan ensures the component is correctly defined and compatible when it becomes part of the plan architecture. Options A and D incorrectly use a days-based plan, while option C reverses the required configuration sequence.

The rule must identify the invalid condition: the requested leave is not covered by the available balance. The source field Sufficient Balance Exists for Leave or Time Off Request returns a Boolean value. When sufficient balance exists, it resolves to Yes; when the request exceeds the balance, it resolves to No.

The rule should therefore evaluate whether the source field is equal to No . The comparison type is Value specified in this filter because the rule compares the Boolean report-field result with the explicitly selected value No. When that condition evaluates as true, the validation is triggered.

The configuration should then be associated with the leave type on the Validations/Supporting Data tab. To prevent submission rather than merely display a warning, the administrator must select Do Not Allow Request . Workday will evaluate the validation when the request is submitted and prevent the request from continuing until the worker reduces the requested amount or cancels the request.

Testing for Yes identifies requests that have sufficient balance and reverses the intended logic. “Not equal to Yes” might appear logically similar, but the explicit Boolean comparison against No is the precise configuration for identifying an insufficient balance condition.

Leave Results for Worker displays leave results for a specific employee as of a selected date. It includes each leave type taken during the applicable balance period, the leave calendar period, units taken, the remaining entitlement balance, and details of individual leave requests. Both in-progress and completed leave events can be included.

Time Off Results Summary reports high-level time off plan balances and results for selected organizations and periods. It does not provide the worker-specific leave entitlement and leave-request detail required here. View Time Off Balance reports time off plan information such as carryover, year-to-date accruals, paid time off, and remaining time off balances; it does not report leave type entitlement results. Manage Absence Cases is used to administer absence cases and associated reintegration activities, not to review leave balances.

The report’s as-of date determines the applicable leave balance period and the leave activity included in the results. This is important for leave types using rolling calendars or other configurable balance-calendar definitions. Appropriate leave-of-absence security is required to view the worker’s results.

Study Guide reference: Absence Management Reports, Dashboards, and Calendars – Leave of Absence Reports .

Selecting Inactivate Worker directly causes Workday to make the employee inactive while the employee is on the configured leave type. Once the leave request is approved and processing is complete, the worker’s status changes without requiring a separate eligibility rule, payroll configuration, or benefits event.

Payroll Effect requires coordination with Workday Payroll configuration. Payroll run categories must be reviewed to determine which earnings or deductions continue or stop while the employee is on leave. Absence Accrual Effect identifies the leave as relevant to absence accrual processing, but an administrator must build time off or accrual eligibility logic that references the effect if accruals should stop during leave. Benefit Effect indicates that the leave may affect benefit eligibility; changing benefit elections generally requires a life event and associated benefit processing.

Inactivate Worker therefore has an immediate operational result from the leave-type setting itself. The worker is subsequently returned to active status when the Return from Leave of Absence business process is completed. Administrators should still evaluate the broader security and integration consequences of inactive status, but no additional functional configuration is needed to produce the status change.

Study Guide reference: Leave of Absence – Details Tab and Leave Impacts .

An absence table supports a single absence request that must draw from more than one time off plan. The table contains prioritized tiers, and each tier identifies a time off plan and the corresponding time off. Workday evaluates those tiers in priority order and automatically assigns the appropriate time off to each portion of the request.

This structure is useful when workers must exhaust one balance before using another. For example, an organization may require workers to use a non-carryover floating-holiday balance before using their standard vacation balance. The worker enters one request, while the absence table allocates the units across the applicable tier balances. It can also support separate plans representing different rates of pay or different components of a common absence allowance.

The Create/Edit Absence Table task controls tiers, details, validations, and reasons. The table does not merge leave entitlements, replace the business process governing approval, or calculate payroll taxes. Its defining function is the controlled cascade of a time off request through multiple prioritized time offs and plan balances.

The Request Leave of Absence business process must contain the Automated Leave Processing service. For cascading leaves, this service is normally added after the completion step with a step delay. The delay determines when Workday evaluates the current leave’s ending condition and initiates the transition.

When the Short Term Disability leave reaches the configured date, Automated Leave Processing generates a return request for the current leave. If the worker meets the eligibility requirements for the Next Leave Type, it also generates a request to begin Long Term Disability Leave. Conditions can be added to the service step to restrict automated processing to specified leave types.

Automated Absence Case Creation creates absence cases when configured absence-case thresholds are met; it does not move workers between leave types. Time Off Balance Transfer is used during job changes to transfer or pay out time off plan balances. Update Time Off Requests updates future time off requests when staffing changes affect plan eligibility. Neither subprocess performs cascading-leave processing.

Study Guide reference: Absence Management Business Processes – Automated Leave Processing Service .

A balance-tracking plan requires the components necessary to define the calculation window, processing frequency, balance presentation, permitted request dates, measurement unit, balance additions, balance reductions, and worker eligibility. The balance period supplies the overall calculation range, while the period schedule establishes processing periods and accrual frequency. Balance visibility and calendar-display settings determine how balance information is presented.

Days to Include and Unit of Time control which dates contribute to requests and whether the plan processes hours or days. Accruals add units to the balance; time offs subtract units. Eligibility rules determine which workers can accrue and use the plan. Together, these elements form the minimum functional architecture of a balance-tracking time off plan.

Leave families, leave entitlements, and payroll-effect configurations belong primarily to leave-of-absence configuration and cannot replace time off plan components. A time off type categorizes the user-facing request but is associated with the underlying time off rather than serving as the complete plan architecture. A balance period and period schedule alone are insufficient because the plan would have no configured sources or uses of balance units.

Supporting data provides contextual information relevant to a leave request. Typical values include the worker’s months of service, actual hours worked, available entitlement balance, or the quantity included in the current request. This information can help the requester understand why Workday generated a warning or error and can help a manager or administrator determine whether the request should be approved or rejected.

Administrators configure supporting data on the Validations/Supporting Data tab of the Create/Edit Leave Type task. They can use Workday-delivered report fields or custom calculated fields. By default, Workday displays the report-field or calculated-field name as the label, although the Label Override field can provide clearer user-facing terminology. Supporting data can also be hidden from employee self-service while remaining visible to administrators.

Supporting data does not enforce eligibility or validation by itself. The rule produces the eligibility result or warning; supporting data explains the relevant facts behind that result. It also does not calculate payroll earnings or establish organization membership. Its function is informative and decision-supporting, making option C technically correct.

A time off plan is the central configuration that establishes how one or more related time offs are entered, processed, tracked, and reported. Depending on whether balance tracking is enabled, it can govern the balance period, period schedule, unit of time, worker eligibility, balance visibility, accrual processing, limits, carryover, and the time offs that reduce the balance.

After the plan is configured, workers and managers can submit requests, correct eligible requests, and monitor request status through self-service pages and reports. Administrators can maintain the associated accruals, time off results, adjustments, overrides, and plan balances. A single plan may support multiple related accruals or time offs when they operate against a common balance, provided their units and eligibility design are compatible.

The plan can pass results to Payroll or Payroll Interface, but it does not calculate payroll taxes. Security permissions are controlled through business process and domain security policies, while supervisory organizations and staffing models belong to HCM organization and staffing configuration. Therefore, the defining function of the time off plan is establishing the rules for entering and tracking related time offs.

When the termination is rescinded, Workday automatically reverses the absence consequence associated with that termination. The system removes the termination adjustment that previously reduced the time off plan balance to zero and restores the balance represented by the removed adjustment. This maintains transactional integrity between the worker’s employment status and absence records.

The administrator should not remove the configured Time Off for Termination Adjustment from the plan. That field is part of the plan’s continuing termination-processing design and changing it would affect future terminations. The Overrides Allowed setting is unrelated to reversing a system-generated termination adjustment. Likewise, manually entering a balance override is unnecessary and could create a discrepancy because an override establishes a replacement balance independently of the original termination transaction.

Automatic reversal is significant because the adjustment is linked to the termination business-process event. Rescinding the source event causes Workday to remove its dependent adjustment rather than requiring an administrator to reconstruct the worker’s previous balance manually. Administrators should validate the restored balance and transaction history, but no manual restoration is required under the stated configuration.

Study Guide reference: Absence Management Business Processes – Termination Adjustments and Rescinded Terminations .

Advanced lookup tables are the preferred Workday structure for lookup calculations that must process substantial data volumes or accommodate policies that change over time. They centralize the lookup data, enabling administrators to update values in one maintained table instead of modifying multiple calculation definitions. This design improves consistency and reduces configuration duplication.

An advanced lookup table can contain up to ten columns, allowing different calculations to retrieve separate values from the same underlying table. Administrators can assign effective dates to search and return values, which is particularly useful when accrual rates, eligibility thresholds, or policy limits change on a specified date. Supported search methods include single-instance or multi-instance report fields, text report fields, and numeric calculations. A default-value table can also be created when search criteria are unnecessary.

Advanced lookup tables do not eliminate lookup calculations; the lookup calculation calls the table and returns the applicable result. They are not limited to numeric search criteria or static values. Their material advantages are scalability, centralized maintenance, effective dating, and flexible search criteria.

The worker begins with an annual Illness Leave entitlement of 30 days. The ten days of Illness Leave taken in March reduce the leave balance to 20 days. Because Intermittent Illness Time Off is coordinated with the Illness Leave Type, the two intermittent days taken in May also reduce the leave entitlement. The resulting calculation is:

30 days − 10 leave days − 2 coordinated time off days = 18 days .

Coordinating an intermittent time off with a leave type instructs Workday to include that time off when calculating leave taken. The intermittent time off can reduce both its associated time off plan balance and the coordinated leave entitlement balance because Workday evaluates those balances independently. The time off and leave type must use compatible units of time for the coordination to calculate correctly.

The remaining balance is therefore not 20 days, because that result ignores the intermittent time off. It is not 28 days, because that result ignores the continuous Illness Leave. The entitlement is not restored to 30 days while both events remain inside the same calendar-year balance period.

Study Guide reference: Leave of Absence – Coordinated Leaves and Time Off .

Workday’s primary leave-of-absence setup components are leave families and leave types. The Maintain Leave Families task creates the high-level categories used to group related leave types. Examples can include Regulatory Leave, Company Leave, or Disability Leave. When a user initiates a leave request, Workday displays the leave family as the category containing the available leave types.

The Create/Edit Leave Type task establishes the detailed rules for a specific leave. It configures eligibility, validations, unit of time, On Leave status visibility, entitlement, balance tracking, balance-calendar dates, Days to Include, supporting data, coordinated leave relationships, and cross-functional effects. The leave type must be associated with a leave family.

Maintain Time Off Types and Create Period Schedule relate to time off configuration. Configure Absence Type Groups can improve the request-selection interface by grouping time offs, absence tables, and leaves, but it does not create the underlying leave definition. Create Absence Table manages cascading time off plans, while accrual tasks govern time off balance additions. Therefore, Maintain Leave Families and Create/Edit Leave Type are the two foundational leave setup tasks.

An Evaluate Expression calculated field returns different values according to ordered conditions. The administrator can configure an expression that evaluates whether the worker is hourly or salaried and returns the applicable numeric entitlement: 10 days for an hourly worker and seven days for a salaried worker. The resulting field can be selected as the leave type’s Entitlement Units calculation.

Evaluate Expression is the calculated-field equivalent of a conditional calculation in the Workday Calculation Engine. Each condition is evaluated against the worker data available at runtime. The calculation should also include an appropriate default value or complete coverage of the expected worker categories so the entitlement does not resolve blank for an eligible worker.

A Build Date calculated field constructs a date from year, month, and day components and cannot return the required numeric entitlement. Sum-Related Instances aggregates numeric values across multiple related records; there is no collection of entitlement records to aggregate in this scenario. An Arithmetic Calculation performs mathematical operations on numeric operands but does not independently choose between two amounts based on worker classification. Because the requirement is conditional—return one entitlement for hourly workers and another for salaried workers—Evaluate Expression is the appropriate calculated field.

The Allow Override for Entry On Behalf Of Worker checkbox permits authorized managers and administrators to override a time off validation when entering, revising, or correcting time off for an employee. The users must belong to security groups authorized for the applicable “enter on behalf of worker” action in the relevant Absence business process security policy.

The eight-hour restriction should remain a hard validation for employees. When an employee attempts to exceed the configured maximum, Workday prevents submission. When an authorized manager or administrator enters the request on the employee’s behalf, Workday displays a warning identifying the validation failure but permits the authorized user to continue. This supports exceptional cases without weakening the general employee restriction.

Clearing Do Not Allow Request would convert the validation into a warning for employees as well, allowing them to submit requests above eight hours. Segmented security controls access to particular time offs; it does not grant permission to disregard a quantity validation. A time off plan eligibility override determines which workers qualify for the time off and has no effect on the maximum daily request. The administrative-override checkbox is therefore the targeted control for the stated exception.