Workday-Pro-Absence Workday Pro Absence Certification Exam Questions and Answers

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.

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.

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.

The Leave Payment Type field is configured when the applicable country-specific Workday Payroll product is in scope. It connects the tenanted Absence leave type with the Workday-delivered statutory payment or earning configuration used by payroll. This relationship enables Workday Payroll to process the leave according to the statutory rules for the relevant country and leave category.

The field is therefore relevant when Workday Payroll for Australia, the United Kingdom, or France is implemented and the leave type is associated with a supported statutory leave. Absence and payroll administrators must coordinate the leave type, statutory payment classification, payroll earning, and related payroll-processing rules so that approved leave produces the intended payment outcome.

When Workday Payroll for the applicable country is not in scope, the Workday-delivered payroll relationship is not used by the tenant’s payroll processing. Configuring the field would not provide the required external-payroll integration by itself. The United States options are also incorrect because the scenario explicitly concerns statutory leave configurations for Australia, the United Kingdom, or France. The determining factor is whether the corresponding Workday Payroll country product participates in processing the statutory leave.

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 .

Leave Type Segmented Security is required because the permitted leave-type population differs according to the requester’s security role. Employees acting as Employee as Self must access six leave types, while managers entering leave on behalf of workers must access all eight. Separate leave type security segments and their associated segment-based security groups provide this role-specific access.

Worker eligibility rules determine whether the subject worker qualifies for a leave type. They do not determine whether an employee or manager is authorized to initiate that leave type. On Leave Status Visibility Type controls who can see the “On Leave” indicator after the worker’s name and has no effect on request availability. Enabled for Worker Type distinguishes whether a leave type applies to employees, contingent workers, or both; it does not distinguish employee self-service from manager self-service.

The six employee-accessible leave types should be included in a segment available to Employee as Self. The manager segment must provide access to all eight leave types. Both roles must also have the appropriate initiating actions on the Request Leave of Absence business process security policy.

Study Guide reference: Leave of Absence – Leave Type Security Segment and Segment-Based Security Group .

A Leave Family groups related leave types into a recognizable category. When employees, managers, or administrators enter a leave request, Workday presents the leave family as the category under which its associated leave types appear. For example, an organization might create a Regulatory Leave family for jury duty, military leave, and statutory parental leave, while using a Company Leave family for bereavement or discretionary personal leave.

A Leave Type is the transactional configuration that defines the rules for a specific leave, including eligibility, validation, balance tracking, entitlement, and processing effects. It belongs to a leave family but does not perform the broader grouping function. Absence Family is not the delivered Workday component used for this purpose. Time Off Type categorizes time offs such as vacation or sickness and applies to the time off configuration model rather than leave-of-absence types.

Leave families improve navigation and reporting while allowing each included leave type to retain independent eligibility, entitlement, validation, and security configuration. Administrators create and maintain these categories through the Maintain Leave Families task.

Study Guide reference: Leave of Absence – Leave Families .

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 .

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.

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.

Eligible in period or prior periods is designed for situations in which the worker is no longer currently eligible but was eligible in an earlier processing period. Workday continues displaying the balance and presents the time off and accrual totals as of the worker’s last eligible period. This supports historical administration without incorrectly treating the worker as currently eligible.

Eligible in period is narrower. It displays the balance only when the worker is eligible at some point during the processing period containing the selected as-of date. If the worker was not eligible during that period, Workday does not display the balance. Eligible in balance period operates across the broader balance period; it can display balances when the worker was eligible at any point during that balance period, but visibility normally ends when the user selects an as-of date in a subsequent balance period.

Never show balance suppresses the balance for workers, managers, and administrators under all conditions. It therefore cannot satisfy the administrative reporting requirement. The prior-period option precisely supports continued historical visibility following loss of eligibility.

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 .

Absence Type Groups provide the calendar-facing classification used to organize and expose selected absence information through Team Absence functionality. Marking the applicable group as Visible for Team Absence enables the associated absence categories to participate in the calendar presentation available to authorized workers and managers.

The other objects perform calculation or balance-management functions rather than controlling calendar visibility. A Leave Entitlement Balance records the amount of entitlement available or used for a leave; it is not a Team Absence display category. A Time Off Plan Balance is a calculated balance for a worker’s plan and is subject to separate balance-visibility controls. An Absence Table coordinates tiered absence calculations or related time offs, but it is not the presentation object selected for this visibility requirement.

Visibility must still be interpreted together with tenant security. Marking an object visible does not independently grant calendar access or expose protected absence details to every user. The user must have access to the Team Absence Calendar, and the configured visibility and security policies determine what information appears.

Study Guide references: Time Off Plans and Components – Visible for Team Absence and Leave of Absence – Absence Type Grouping .

A leave of absence rule does not operate as a validation until it is associated with a specific leave type on the Validations/Supporting Data tab. The administrator must first add the rule to the leave type and save the leave type. This establishes the relationship required for Workday to configure a validation message in the context of that leave type. The administrator can then use the leave type’s Related Actions to configure the message.

By default, Workday can display the leave of absence rule’s Description as the warning or error text. A separately configured validation message can provide more precise guidance and may include static text, report-field values, or calculated-field values relevant to the request. This allows the same underlying rule to be associated with multiple leave types while supporting context-specific messaging.

The message is not selected from a fixed list of predefined options. Configuring it directly on an unassociated rule would not provide the leave-type context required for the validation. Accessing Related Actions before adding and saving the rule would likewise leave no saved validation relationship to configure. The correct sequence is to associate the rule, save the leave type, and then configure the message through Related Actions.

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 .

Clearing Do Not Allow Request converts the applicable validation from a blocking error into a warning. When the request fails the validation, Workday displays the warning message but permits the user to save and submit the request. The request can then continue through the configured business process, where a manager or administrator can review, approve, send back, or deny it.

When Do Not Allow Request is selected, Workday prevents the employee from saving a request that fails the validation and displays an error. Clearing the checkbox does not cause Workday to correct the quantity automatically or present guided correction prompts. It only changes the validation’s enforcement level.

This configuration is available for supported validations such as Maximum Unpaid Time Off Units Allowed, Consecutive Days Maximum, and Consecutive Days Minimum. Administrators can also define custom text to explain the warning and optionally place that text before the standard message. If Allow Override for Entry on Behalf of Worker is configured, authorized managers or administrators can proceed when entering an otherwise invalid request for an employee.

Study Guide reference: Time Off Validations – Do Not Allow Request .

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.

Supporting Data displays contextual information that helps a worker understand the effect of a leave request. The administrator can configure calculated fields or Workday-delivered report fields to show the worker’s available leave entitlement, the amount consumed by the current request, and the projected entitlement balance if the request is approved.

Supporting data is configured on the Validations/Supporting Data tab of the leave type. By default, Workday uses the report or calculated field name as the displayed label, although the administrator can provide a Label Override to make the information clearer. Supporting data can also help approvers interpret warnings or determine whether a request should be approved or rejected.

Eligibility Criteria determines whether the leave type is available to the worker and does not present projected balance information. Leave Reasons capture the reason for the absence, such as illness or family care. Cascading Leave defines a sequence in which one leave type follows another. None of these options provides the required entitlement details during the request. Supporting Data is therefore the correct configuration for presenting current and projected leave-balance information to the requester.

Workday coordinates short-duration time off with a leave entitlement through the Intermittent Time Offs field on the leave type. The administrator creates the appropriate time off and time off plan, then adds that time off to the Sickness leave type’s Intermittent Time Offs field. Units requested through the intermittent time off are subsequently counted as leave taken and reduce the sickness leave entitlement balance.

When a coordinated intermittent request is processed, Workday evaluates the time off plan balance and the leave entitlement balance independently. The request must satisfy the eligibility and validation rules configured for both the time off and the related leave type. The time off may therefore reduce its time off plan balance while simultaneously reducing the coordinated leave balance.

An absence type group changes how available absence types are organized in the request prompt; it does not coordinate their balances. An accrual calculation adds to a time off plan balance and is not the mechanism for deducting short sickness events from a leave entitlement. Calculated fields can establish an entitlement amount but do not create the transactional relationship between time off taken and leave taken. The Intermittent Time Offs relationship is the configuration designed for this requirement.

The eight-hour accrual must be entered in the Default Response field of the conditional calculation. A conditional calculation evaluates its configured conditions in sequence. California workers satisfy the California condition and receive 12 hours, while Illinois workers satisfy the Illinois condition and receive 10 hours. Workers who satisfy neither condition fall through to the Default Response and receive eight hours.

The 2nd Operand belongs to a comparison calculation and represents the value against which the first operand is evaluated. It does not define the fallback result of the conditional calculation. Target Instance is used in calculations that resolve or compare a specific business-object instance. Custom field is not the conditional calculation field used to provide an otherwise result.

A default response is essential because the configuration must return a valid numeric accrual amount for every eligible U.S. worker. Without it, workers outside California and Illinois could receive no resolved value. The returned values must use the same unit of time as the associated time off plan—in this scenario, hours.

Study Guide reference: Calculations for Time Off Plans – Conditional Calculations .

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.

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 .

An accrual is the configuration that adds units to a worker’s time off plan balance. It specifies both the quantity awarded and the conditions or timing under which the worker receives that quantity. The amount can be a constant or can be calculated from factors such as service, location, worker type, or other report-field values.

The accrual definition also establishes processing priority, scheduling rules, adjustment and override permissions, eligibility requirements, accrual-frequency overrides, and applicable limits. Because accruals increase balances, they are used only with time off plans that have balance tracking enabled. A basic plan that does not track a balance has no need for an accrual component.

A time off type provides the category name displayed to users. An underlying time off represents the absence and subtracts approved units from the plan balance. Leave dates are managed through leave-of-absence requests and leave-type configuration. These functions are distinct from the accrual. Option B correctly combines the two defining characteristics: the amount awarded and when that award is made.

Leave families group related leave types into functional categories. When users initiate a leave request, Workday presents the leave family name as the category containing the associated leave types. The administrator should therefore create one family for statutory leave types and a second family for non-statutory leave types.

This structure provides a clear functional distinction while preserving the individual rules, eligibility, validations, entitlements, balance calendars, and payroll effects configured on each underlying leave type. Leave families can also participate in coordinated-leave configuration when units taken from leave types in the same family must affect related entitlement balances.

Placing all leave types in one family would eliminate the required category separation; different eligibility rules would change worker access but would not produce separate leave-family groupings. Leave type security segments control access to specified leave types for roles such as Employee as Self or Manager. They are security boundaries rather than functional leave categories. An absence table can combine absence-related data or selection behavior for other purposes, but it is not the primary Workday component for grouping leave types into statutory and non-statutory categories. Two leave families directly satisfy the requirement.

Scheduling: Worker Hired Mid-Period identifies workers whose hire date occurs after the applicable period has started. Adding this calculation as a scheduling rule provides a separate trigger for the front-loaded accrual when a worker is hired after January 1. The accrual amount calculation can then apply the required proration.

The January scheduling condition processes the regular full-year award for workers who are already eligible at the beginning of the year. That condition alone does not ensure that a worker hired later receives an accrual because the worker was not eligible when the January event was processed. Scheduling: Worker Hired Mid-Period captures this second event.

Scheduling: Last Period of the Balance Period would process the accrual near the end of the balance year and contradicts the stated requirement. Scheduling: Front-Loaded identifies the nature of front-loaded processing but does not independently isolate mid-period hires. The scheduling grid can contain separate rows, applying OR logic between rows, so either the annual January condition or the mid-period-hire condition can initiate processing.

Study Guide reference: Calculations for Time Off Plans – Scheduling Rules and Front-Loaded Accruals .

Workday classifies leave types according to whether they track an entitlement balance. A leave type without balance tracking supports straightforward leave request and approval processing but does not maintain a fixed entitlement balance. Bereavement or long-term disability can be configured this way when the policy does not require Workday to calculate entitlement minus leave taken.

A balance-tracking leave type retains the same request and approval functionality but adds entitlement accounting. It requires balance-calendar start and end dates, entitlement units or calculations, a unit of time, and rules determining which requested days or hours reduce the entitlement. Workday calculates the remaining balance from entitlement less applicable leave taken, including coordinated leave or intermittent time off where configured.

Paid versus unpaid, statutory versus company-provided, and employee versus contingent-worker distinctions can influence a leave type’s configuration, eligibility, payroll effect, or leave family. They are not the two structural leave-type categories used by Workday. The decisive classification is whether the leave type maintains and calculates a balance. Therefore, option C is the complete technical classification.