Free Workday Pro Absence Certification Exam Workday-Pro-Absence Exam Questions

A period schedule establishes the recurring processing periods used by the time off plan and therefore determines its default accrual frequency. For example, a monthly period schedule normally causes Workday to process periodic accruals monthly, while a weekly schedule provides weekly processing periods. This behavior can be modified through an accrual frequency override, custom frequency, or front-loaded configuration, but the period schedule supplies the standard framework.

The schedule also defines period start and end dates used to retrieve and process time off, organize balance reporting, evaluate period-based eligibility criteria, and determine which effective dates are available for time off plan components. Every time off plan must therefore reference a valid period schedule.

Public holidays are defined through holiday calendars rather than period schedules. The maximum number of consecutive absence days is controlled by a Consecutive Day Maximum validation. The types of time off available to workers are determined through time off types, underlying time offs, eligibility, and security configuration. These functions do not belong to the period schedule. Among the available choices, determining the plan's default accrual frequency is the defining period-schedule characteristic.

The time off plan must have the Overrides Allowed checkbox selected. This plan-level setting enables administrators to use Maintain Time Off Plan Carryover Overrides to change a worker's calculated carryover amount or carryover expiration date when exceptional circumstances justify an exception.

Adjustments/Overrides Allowed on an accrual enables changes to accrual values for individual processing periods. It does not enable carryover overrides. The corresponding setting on a time off permits adjustments or overrides to time off activity, not to the plan's carryover calculation. A lower limit override controls the amount of paid time off available when the worker's balance falls below zero and has no relationship to carryover limits.

After overrides are enabled, the administrator can define an employee-specific carryover exception. The override must differ from the amount generated by the plan, cannot duplicate another carryover override, and cannot establish an expiration date before the carryover date. Retroactive carryover overrides may affect calculated balances, so the calculated balance process may need to be rerun after the change.

Study Guide reference: Absence Management Administration -- Maintain Time Off Plan Carryover Overrides.

The Adjust Time Off Balances service step initiates the processing required to reduce eligible time off plan balances when a worker terminates. It is normally positioned after the completion step in the Termination business process because the termination must first be completed before Workday performs the associated balance adjustment.

For each eligible plan, Workday identifies the configured Time Off for Termination Adjustment, creates the required adjustment, and reduces the worker's remaining balance to zero. The resulting adjustment supplies the balance-reduction transaction needed for downstream payroll treatment when the organization has configured the associated payroll calculation or interface.

Terminate User Account controls system-access termination and has no responsibility for absence balances. Automated Leave Processing addresses leave-related processing rather than time off payouts. Automated Accrual Adjustment is used for accrual changes caused by eligibility events, particularly mid-period job changes; it does not execute termination balance payout processing.

The business-process step is only one part of the complete configuration. The time off plan must also identify the time off used for the termination adjustment, and that time off must permit adjustments.

Study Guide reference: Absence Management Business Processes -- Automating Payout of Plan Balance upon Termination.

The Include all Leave Types from Leave Family setting causes units taken for other leave types in the same family to count as leave taken against the current leave type's entitlement balance. Because the requirement is reciprocal---usage of any one leave must reduce all three balances---the setting must be selected on each of the three leave types.

For example, if Leave A, Leave B, and Leave C share a family and a worker takes five days of Leave A, Workday must count those five days against the entitlement balances of A, B, and C. Selecting the setting only on Leave A would make Leave B and Leave C count against A, but it would not automatically cause an event for Leave A to reduce the other balances. Coordinated relationships must be configured from the perspective of every balance that should be reduced.

The leave types must use compatible units of time for family-level coordination. Intermittent Time Offs links a time off with a leave type; it does not coordinate multiple leave types. An absence table defines a selectable absence construct and does not establish shared entitlement deductions. Applying the family coordination option to all three leave types creates the required concurrent reduction behavior.

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.

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.

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.

Workday automatically recalculates the accrual adjustment when the effective date of the underlying job change is corrected. The adjustment is system-generated from the Change Job business process and is dependent on the job-change effective date, the worker's eligibility transition, the applicable accrual period, and the accrual's adjustment configuration. Correcting the source event causes Workday to reevaluate those inputs and update the dependent adjustment.

Manual deletion is neither required nor preferred because it would separate the adjustment from the business event responsible for creating it. The Time Off for Balance Transfer Adjustment field supports balance-transfer scenarios and does not govern recalculation of an accrual adjustment created because the worker lost eligibility. Carryover overrides apply to balances transferred between balance periods and are similarly unrelated to correcting the effective date of a job change.

This automated recalculation prevents an incorrect proration from remaining after the source event changes. For example, moving the job-change date later in the processing period may increase the portion of the period for which the worker was eligible. Workday recalculates the resulting adjustment using the corrected date.

Study Guide reference: Absence Management Administration -- Accrual Adjustment during a Job Change, including automated processing associated with Change Job events.

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.

A balance-tracking leave type requires the ordinary leave request configuration plus the elements necessary to calculate an entitlement balance. The leave family organizes the leave type for user selection. On Leave status visibility controls who can see that the worker is on leave, while the eligible worker type establishes whether the leave applies to employees, contingent workers, or both.

Track Balance must be enabled. Calculated fields define the balance-calendar start and end dates, establishing the period over which Workday calculates entitlement minus leave taken. The unit of time ensures that entitlement and leave usage are consistently expressed in hours or days. Calendar Display determines whether entitlement information appears in the Absence Calendar or Time Off and Leave Calendar. Leave entitlement defines the maximum available units, and Days to Include determines which requested dates or hours reduce the balance.

Period schedules, accrual frequency, upper and lower limits, and carryover rules are time off plan mechanics. Payroll, benefit, and stock effects are optional cross-functional settings, not a complete required configuration. Option A contains the full required set identified by Workday.