Workday Pro Absence Certification Workday-Pro-Absence Exam Questions

Answer : C

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.

Answer : B

View Worker Leave of Absence Eligibility by Organization displays the leave types for which active workers in selected organizations are eligible as of the current day. It enables a manager or other appropriately secured user to review the leave options available to workers across the manager's organization.

Leave Results for Organization reports actual leave results as of a specified date, including leave taken, applicable calendar periods, remaining balances, and individual leave-request details. It is designed to analyze leave activity rather than identify every leave type currently available to the team. Time Off Balances and Liability by Organization reports time off financial liability and employee time off plan balances. All Worker Time Off displays approved, pending, and denied time off for workers and managers in an organization; it does not report leave-of-absence eligibility.

The report evaluates eligibility using the active worker population and the current date. Its results can therefore change when worker attributes or leave configurations change, including worker type, country or region, job data, and additional eligibility criteria. Report visibility remains subject to the manager's organization-based and leave-of-absence security access.

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

Answer : D

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.

Answer : A

The Generate Period Schedule Periods task extends an existing period schedule by automatically creating future periods. Workday states that this task can extend supported period schedules for up to two years. The schedule must already contain at least one configured period so Workday can derive the sequence, frequency, period boundaries, and related dates for the newly generated periods.

This task is appropriate because the requirement is to extend an existing schedule, not establish a new schedule. Create Period Schedule is used when manually defining a new period schedule. ''Set Up Period Schedule'' and ''Produce Period Schedule Periods'' are not the delivered tasks for this operation.

For supported frequencies---including annual, weekly, biweekly, semimonthly, and monthly---the administrator selects the existing schedule and specifies the number of periods to generate. Workday then derives the period start and end dates based on the existing schedule pattern. Depending on the schedule's usage, the administrator may also need to review application-specific dates or overrides after generation.

Answer : A

Workday Absence, Payroll, and Time Tracking can share the same period schedule when the schedule's frequency and period dates satisfy each application's requirements. The Usage field identifies which Workday applications are permitted to use that schedule. Therefore, the administrator should edit the existing schedule and add Absence to the Usage field.

Creating a duplicate schedule is unnecessary and introduces avoidable maintenance risk. Two schedules containing equivalent periods can diverge when future periods, lock dates, or application-specific configuration are updated independently. Reusing the existing schedule maintains a consistent period framework across Time Tracking and Absence.

Eligibility configuration determines which workers are assigned or eligible for a schedule within an application; it does not make a Time Tracking schedule available to Absence. Adding Absence-related criteria to a Time Tracking eligibility rule also mixes application responsibilities and fails to update the schedule's declared usage. Likewise, simply adding an Absence eligibility rule without enabling Absence in the Usage field does not establish the required application association. Once Absence is added to Usage, the administrator can select the schedule on the new time off plan and configure any appropriate Absence eligibility separately.

Answer : C

The Daily Quantity Default field specifies the number of hours or days that Workday automatically supplies for each selected date when a user enters a time off request through the calendar. The value can be a fixed quantity, such as eight hours, or a calculation that derives the worker's scheduled hours or another applicable quantity.

When a conditional calculation provides the default, Workday evaluates the calculation using the first day of the request and can apply that resolved quantity to the requested dates. The field improves entry consistency and reduces the need for workers to manually enter the expected quantity on every date. A time off can also contain an override when its default quantity must differ from the default established on the plan.

Days to Include determines which dates Workday initially includes when the worker selects a date range, such as all days, weekdays, or workdays. It does not specify the quantity for those dates. The Lower Limit determines the point below which time off becomes unpaid. The Accrual Frequency Method determines whether Workday adds accruals at the start or end of a period or according to a custom frequency. Consequently, only Daily Quantity Default controls the automatically populated daily units.

Answer : B

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.