Workday-Pro-Absence Exam Questions

The Put Override Balance EIB performs mass time off plan balance overrides. It is appropriate because 200 acquired workers require the same type of beginning-balance conversion. Each worker's eligible plan balance can be established at 40 hours as of the applicable period start date, after which Workday uses that amount as the starting point for subsequent accrual and time off calculations.

Import Request Leave of Absence loads leave-of-absence events and does not establish time off plan balances. Adjust Time Off creates mass time off adjustment or correction transactions; it is not the delivered EIB for setting the authoritative opening balance. Enter Time Off loads time off requests through the Request Time Off business process and would reduce balances instead of establishing them.

The effective date must align with the start of a period for which each worker is eligible. Administrators must also understand that an override replaces the calculated balance at that point. Workday does not recalculate the overridden balance for the override date or earlier dates when retroactive activity is subsequently entered. Data validation should therefore confirm worker eligibility, plan, unit of time, effective date, and the 40-hour value before loading.

Study Guide reference: Absence Management Administration -- Maintain Time Off Plan Carryover and Balances for Employees.

The 30-day entitlement is awarded at the beginning of the balance period, so the accrual is classified as front-loaded. If a worker subsequently becomes ineligible because of a job change, Workday must calculate the portion of the front-loaded award that the worker was not entitled to retain. Selecting Front-Loaded activates this proration behavior, while the scheduling condition identifies the business event that should initiate the adjustment.

The scheduling row must use Scheduling: Worker Job Change Mid-Period because the triggering event is a change of job that causes eligibility loss during the balance period. Workday then evaluates the job-change effective date, determines the eligible portion of the calendar year, and creates the corresponding accrual adjustment. The termination condition in option A applies to a termination event, not a job change. Selecting None provides no special mid-period proration. Merely selecting Front-Loaded without the required scheduling condition does not identify when the adjustment should occur.

Study Guide references: Absence Management Administration -- Accrual Adjustment during a Job Change and Time Off Plans and Components -- Accrual Options.

The time off plan must specify a time off in the Time Off for Termination Adjustment field. This configuration tells Workday which time off component to use when generating the adjustment that removes the worker's entire remaining balance during termination processing.

When the Adjust Time Off Balances service step runs in the Termination business process, Workday evaluates the eligible plan, determines the remaining balance, and creates a termination adjustment using the designated time off. The adjustment reduces the plan balance to zero. Where payroll integration or Workday Payroll calculations are appropriately configured, that adjustment can support payment of the outstanding amount.

A payout accrual is not required because an accrual ordinarily adds units to a time off plan; it does not remove and pay the existing termination balance. Accrual Frequency Method controls whether ordinary accrual processing occurs at the start or end of a processing period and does not establish termination payout behavior. Time Off Forfeiture Adjustment is used when a balance is being forfeited under plan rules, not when the organization intends to pay the balance upon termination.

Study Guide reference: Absence Management Business Processes -- Automating Payout of Plan Balance upon Termination, particularly the time off plan's termination-adjustment configuration.

A lower limit of zero means Workday treats time off that would reduce the plan balance below zero as unpaid. That calculation setting alone does not necessarily stop the worker from submitting the request; it determines how much of the requested absence can be processed as paid.

To prohibit unpaid time off, configure the Maximum Unpaid Time Off Units Allowed validation with a value of zero. This establishes that no portion of the request may be unpaid. The Do Not Allow Request checkbox must also be selected so that a request failing the validation produces an error and cannot be saved or submitted. If that checkbox is cleared, Workday generates a warning but permits the request to proceed, which does not satisfy the requirement that workers request only paid time.

Setting the maximum unpaid units to eight would explicitly permit up to eight unpaid hours or days, depending on the plan's unit of time. Therefore, options B and D conflict with the requirement. Option A uses the correct zero-unit threshold but configures only a warning. The combination in option C creates a hard validation: zero unpaid units are permitted, and any request exceeding the available paid balance is blocked.

The Team Absence Calendar is the configurable report used to provide workers and managers with a calendar-based view of selected absence information for members of their team. It can present configured time off and leave information in a shared operational view, subject to the user's security access and the visibility settings assigned to the relevant absence components.

Time Off Results Detail and Time Off Results Summary are administrative result reports used to analyze processed time off transactions and balances. They are not designed as the primary team-facing calendar. My Team's Upcoming Time Off can display future time off information, but it does not provide the combined, configurable calendar framework for both selected time off and leave information described in the question.

Configuration determines which absence categories are displayed, while security determines which workers and details the viewer is permitted to see. Sensitive absence information should therefore be exposed only through properly configured visibility and security policies. Selecting Visible for Team Absence on applicable components supports their appearance on the calendar but does not independently grant access.

Study Guide references: Time Off Plans and Components -- Visible for Team Absence and Absence Management Business Processes -- Absence Reports, Dashboards, and Calendars.