Workday Workday-Pro-Absence - Workday Pro Absence Certification Exam

The delivered task used to manually establish a period schedule is Set Up Period Schedule. This task creates the schedule framework and enables the administrator to define its frequency and periods directly in the Workday tenant. Period schedules are foundational to Absence configuration because they establish the processing periods used for accruals, time off transactions, reporting, and period-based eligibility evaluation.

Generate Period Schedule Periods serves a different purpose. It extends an existing supported schedule by generating future periods from its established pattern; it is not the manual setup task for a new schedule. “Produce Period Schedule Periods” is not the applicable delivered task. Although Workday course materials may describe the overall activity as creating a period schedule and reference period-schedule creation functionality, the task label tested by this question is Set Up Period Schedule.

During setup, administrators should specify the correct frequency and application usage and ensure that the periods are consecutive. Workday Absence, Payroll, and Time Tracking can share a schedule when their period dates align. After creating the schedule, it can be selected on a time off plan, where it governs accrual frequency, processing periods, reporting intervals, and available effective dates.

A time off type is the category presented to users when they enter or review a time off request. For example, Vacation can be the user-facing time off type. An organization may associate different underlying time offs—such as Vacation Full Time and Vacation Part Time—with that category to support separate eligibility rules or worker populations while displaying a consistent selection to users.

A time off is the operational configuration that represents the actual time away from work. It subtracts units from the associated time off plan balance and defines processing details such as priority, entry method, validation rules, eligibility or limit overrides, reasons, and adjustment permissions. Every time off must be associated with a time off type.

The distinction is therefore between classification and processing configuration. The time off type organizes and labels the user’s selection, while the time off determines how the absence is entered, validated, processed, and deducted. Neither component independently controls period schedules or creates leave families. Payroll and benefits may consume absence information, but they do not define this relationship.

The Accrual and Time Off Adjustments/Overrides by Batch ID report is specifically designed to review adjustment and override records associated with a particular import batch. Put Absence Input assigns or carries a batch identifier that enables administrators to isolate the records created by that EIB load.

The report displays batch totals for each affected accrual or time off and provides employee-level adjustment or override data by processing period. This supports reconciliation of the expected record count, worker population, accrual component, effective period, and imported values. It can include transactions for plans with or without balance tracking.

View Time Off Balance displays calculated plan balances but does not isolate the imported accrual override records by batch. Leave Results for Worker reports leave entitlement and leave-request information. All Worker Time Off reports time off requests and statuses rather than accrual input transactions.

Administrators should compare the report totals against the EIB source file and investigate rejected, duplicated, or incorrectly effective-dated records. The batch-specific report provides a more reliable audit trail than reviewing workers’ resulting balances individually.

Study Guide reference: Absence Management Reports, Dashboards, and Calendars – Accrual and Time Off Adjustments/Overrides by Batch ID .

A touchpoint diagram is used to evaluate dependencies and interactions between Workday Absence Management and other functional areas. Absence configuration does not operate in isolation. Period schedules may be shared with Time Tracking or Payroll; time off results can feed payroll calculations; leave events can affect worker status, benefits, compensation, scheduling, and other HCM processes. A touchpoint view helps administrators identify these cross-functional impacts before changing configuration.

The diagram is therefore an architectural and impact-assessment tool. It allows the implementation team to determine which upstream data supplies Absence processing, which downstream processes consume absence results, and which business processes or integrations may require coordinated changes. It does not calculate an individual worker’s balance, define the approval chain for one request, or perform segmented-security configuration.

Those operational functions are handled by time off plan calculations, business process definitions, and security domains or segments respectively. Selecting the cross-functional impact purpose is essential because configuration changes made without considering touchpoints can produce inconsistent payroll results, incorrect eligibility behavior, or unexpected effects in related Workday applications.

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.

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 .

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.

An eligibility rule determines whether a worker qualifies for the leave type. Workday evaluates eligibility against the requested leave’s start date and displays only the leave types for which the worker is eligible. Eligibility rules are attached through Additional Criteria on the leave type’s Details tab and must use Worker- or Position-based information because Workday evaluates qualification before it has complete leave-event information.

A validation rule evaluates whether an otherwise eligible request complies with policy. Workday can apply the validation to each requested day when the request is submitted. A failed validation can produce a hard error, preventing submission, or a soft warning that allows the request to continue for review. Examples include preventing a request that exceeds the worker’s entitlement or generating a warning when supporting conditions are not satisfied.

Eligibility therefore controls access to the leave type; validation controls the acceptability of a particular request. Neither function replaces segmented security, accrual-frequency configuration, payroll processing, or benefits administration. Option B correctly describes both the timing and functional purpose of the two rule types.