Free Practice Questions for the Workday Payroll, Absence, and Time Tracking Workday-Pro-Absence Exam (2026 Updated)

Selecting Adjustments/Overrides Allowed on the accrual enables administrators to modify the worker’s calculated accrual result. They can then use Maintain Accrual and Time Off Adjustments/Overrides for individual workers or Put Absence Input for mass accrual adjustments and overrides.

An accrual adjustment adds to or subtracts from the calculated accrual for a processing period. An accrual override replaces the calculated accrual result for one or multiple periods. Workday applies an override before applying an adjustment, and plan limits or accrual-processing timing can still reduce the final value.

Selecting Overrides Allowed on the time off plan enables plan-balance and carryover overrides; it does not authorize component-level accrual changes. A front-loaded scheduling calculation determines when the accrual processes and does not permit manual modification. An absence input calculation may be referenced when designing specialized eligibility or calculation logic, but it does not replace the required permission setting on the accrual.

Because the plan is front-loaded, the worker must remain eligible for the accrual when the administrator enters the applicable adjustment or override.

Study Guide reference: Absence Management Administration – Maintain Employee Accruals .

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.

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.

An Arithmetic Calculation performs the mathematical operations required to determine the percentage of the year during which the worker is employed and apply that percentage to the full annual accrual. A typical design divides the remaining eligible days in the year by the total number of days in the year and multiplies the resulting percentage by the annual accrual amount.

A Logic Calculation returns true or false using AND or OR conditions; it cannot independently calculate the prorated numeric amount. A Date Increment/Decrement Calculation adds or subtracts a defined number of days, months, or years from a date and returns another date. It may support date derivation but does not produce the required percentage. A Constant Value Calculation always returns the same value and cannot vary according to hire date.

Workday provides delivered arithmetic proration calculations for mid-period hires, and similar arithmetic components can be used to construct annual proration. The final result must use the time off plan’s unit of time. Appropriate rounding should also be configured where the calculated result could contain fractional hours or days.

Study Guide reference: Calculations for Time Off Plans – Arithmetic Calculations and Proration .

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.

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.

A leave type without balance tracking supports simple leave request and approval functionality. Although it does not maintain a fixed entitlement, administrators can still define who is eligible, determine which days count in the leave request, and specify whether leave is measured in days or hours. Some validation rules can also be applied to control invalid requests.

The complete configuration normally includes a leave family, On Leave status visibility, eligible worker type, unit of time, calendar-display option, and Days to Include. The eligibility design can contain additional criteria based on Worker or Position data. What the configuration cannot contain is an entitlement calculation that produces and tracks a remaining leave balance.

Accrual frequency, upper and lower limits, carryover, period schedules, and accrual priorities belong to time off plans rather than non-balance leave types. Entitlement-per-event functionality is relevant to balance-tracking leave types because Workday must create and reduce an entitlement balance for each qualifying event.

Option A therefore identifies the applicable elements without incorrectly introducing time off plan balance mechanics or leave entitlement accounting.

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 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.

The Allow Override for Entry On Behalf Of Worker checkbox permits authorized managers and administrators to override a time off validation when entering, revising, or correcting time off for an employee. The users must belong to security groups authorized for the applicable “enter on behalf of worker” action in the relevant Absence business process security policy.

The eight-hour restriction should remain a hard validation for employees. When an employee attempts to exceed the configured maximum, Workday prevents submission. When an authorized manager or administrator enters the request on the employee’s behalf, Workday displays a warning identifying the validation failure but permits the authorized user to continue. This supports exceptional cases without weakening the general employee restriction.

Clearing Do Not Allow Request would convert the validation into a warning for employees as well, allowing them to submit requests above eight hours. Segmented security controls access to particular time offs; it does not grant permission to disregard a quantity validation. A time off plan eligibility override determines which workers qualify for the time off and has no effect on the maximum daily request. The administrative-override checkbox is therefore the targeted control for the stated exception.

Because Medical Leave and Military Leave belong to different leave families, they must be coordinated explicitly through the Additional Leave Types field. The relationship must be configured on both leave types: Medical Leave must reference Military Leave, and Military Leave must reference Medical Leave. This reciprocal configuration ensures that units taken under either leave are counted against the balance of the other coordinated leave.

Workday does not automatically create a bidirectional relationship when one leave type references another. Configuring only Medical Leave on Military Leave, or only Military Leave on Medical Leave, would update one entitlement calculation but not necessarily the other. The leave types must use compatible units of time so that Workday can count the coordinated units correctly.

Include all Leave Types from Leave Family is inappropriate because the two leave types are in different families. That option coordinates leave types within the same family. The related Time Off should separately be added to the Intermittent Time Offs field of the applicable leave type so its units also reduce the leave entitlement. For the specific question of coordinating the two leave types, each must reference the other through Additional Leave Types.

Put Period Schedule is the inbound Workday web service used to create or load period schedule data. Workday supports two principal configuration approaches: administrators can manually establish schedules through the Create Period Schedule task, or they can load schedule information through the Put Period Schedule web service, commonly using an Enterprise Interface Builder integration.

The “Put” operation is appropriate because the request changes Workday data by submitting a new or updated business object. A “Get” operation retrieves existing information and therefore cannot create a period schedule. “Get Schedules” and “Put Schedules” are not the delivered service names identified for this Absence configuration requirement.

Period schedules provide consecutive processing periods and may be shared by Workday Absence, Payroll, and Time Tracking when their dates and frequencies align. The inbound data must therefore contain the schedule structure and required period information in a form accepted by the service. Usage must also be configured correctly so that the schedule is available to Absence Management. After loading the data, the administrator should review the schedule, generated periods, application usage, and relevant dates before attaching it to a time off plan.

Leave Type Segmented Security controls which specific leave types a security role can access when placing a worker on leave. Although the worker satisfies the leave type’s eligibility criteria, the leave will not appear for the manager unless it belongs to a Leave Type Security Segment accessible through the manager’s segment-based security group.

The Request Leave of Absence business process security policy determines whether a manager can initiate leave requests generally. If that initiation security were missing, the manager would be unable to initiate the business process, rather than simply being unable to see one newly created leave type. Opting in to segmented security does not automatically assign new leave types to existing segments. New leave types must be added to the appropriate security segment deliberately.

The administrator should add the new leave type to the manager’s Leave Type Security Segment, confirm that the Manager role is included in the associated segment-based security group, and verify access to the Leave Type Segmented Setup domain. Pending security policy changes must also be activated where applicable.

Study Guide reference: Leave of Absence – Leave Type Segment Security .

A balance period establishes the time span over which Workday calculates the financial and quantitative activity associated with a time off plan. The same balance period applies to accrual amounts that increase the plan balance, approved time off that reduces the balance, and the resulting time off plan balance. Typical examples include a calendar-year period or an anniversary period based on the worker’s hire date.

The balance period must not be confused with the period schedule. The period schedule divides activity into processing intervals, such as weekly, biweekly, or monthly periods, and ordinarily determines accrual frequency. The balance period instead defines the broader measurement window within which those processing periods operate. Workday also uses it when determining carryover, resetting year-to-date values, and calculating balance totals.

Approval routing is controlled by the relevant business process definition, while security groups and domains determine access. Neither function is performed by the balance period. Therefore, the date range used to calculate and aggregate accrual, time off, and plan balances is the technically accurate answer.

A time off plan’s Upper Limit specifies the maximum number of hours or days that a worker can accumulate in the plan balance. Setting the upper limit to 200 hours instructs Workday to compare the worker’s calculated balance with that ceiling during accrual processing. When a calculated accrual would raise the balance above 200 hours, Workday reduces the accrual by the excess amount. The excluded amount is reported as forfeited accrual.

For example, if a worker has 195 hours and is scheduled to accrue 12 hours, the preliminary balance is 207 hours. Workday applies the 200-hour upper limit and reduces the accrual by seven hours. The worker receives five hours, producing a final balance of 200 hours.

A Carryover Limit applies only when balances move from one balance period to the next; it does not prevent the balance from exceeding a threshold during the current period. Maximum Unpaid Time Off Units Allowed validates requests that exceed the available paid balance and is unrelated to accumulation. A Lower Limit controls how far a balance may be reduced before requested time becomes unpaid. Consequently, only the Upper Limit directly enforces the maximum accumulated plan balance.

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.

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 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 .

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.

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.

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 .

Put Override Balance is the web service and EIB used to perform mass time off plan balance overrides. It replaces each selected worker’s calculated plan balance with the supplied value as of an eligible period start date. This makes it appropriate when an administrator must establish authoritative replacement balances for a group of workers.

Enter Time Off creates mass time off requests through the Request Time Off business process and normally reduces balances. Adjust Time Off loads time off adjustments or corrections but does not replace the overall calculated plan balance. Put Absence Input loads accrual or time off adjustments and overrides; it is used to change component-level accrual or time off values rather than replace the entire time off plan balance.

The time off plan must have Overrides Allowed selected. Administrators must carefully validate the plan, worker, unit, override value, and effective period before loading. After Workday accepts an override, it uses that balance as the starting point for calculations going forward and does not recalculate the balance for the override date or earlier dates based on later retroactive entries.

Study Guide reference: Absence Management Administration – Maintain Time Off Plan Override Balances .

Start and stop time entry is configured on the time off component before that component is associated with the intended hours-based time off plan. In the Create Time Off task, the administrator selects the appropriate entry option and enables Display Start and End Time. Workday then exposes Start and End Time Required, which makes both values mandatory when a requester enters the time off. An additional option can calculate the requested quantity from the interval between those times.

The configuration must align with the plan’s unit of time. An hours-based plan is the appropriate design when the business requirement depends on precise clock times and a calculated duration. Although Workday can display start and end times in several request contexts, the selected time off, accruals, limits, and calculations attached to a plan must remain compatible with that plan’s unit of time. Workday does not automatically convert day-based configuration values into hourly values.

Configuring the requirement before adding the time off to the hours-based plan ensures the component is correctly defined and compatible when it becomes part of the plan architecture. Options A and D incorrectly use a days-based plan, while option C reverses the required configuration sequence.

A rolling-forward balance calendar begins on the effective date of the leave event—specifically, the First Day of Leave—and ends 12 months after that date. This creates a worker- and event-specific entitlement window that moves forward from the beginning of the applicable leave rather than using fixed calendar-year dates.

Option C reverses the required chronology by placing the calculated date plus 12 months before the original effective date. Options B and D use fixed year boundaries and therefore create calendar-year periods, not rolling-forward periods. Option B also reverses the start and end sequence.

The Balance Calendar Start Date and Balance Calendar End Date calculated fields determine the period over which Workday calculates entitlement minus leave taken. For the requirement that each child generate a separate 180-day entitlement, the leave type should additionally capture the identifying event data, such as the child’s birth date, and use Entitlement Per Event. Those settings distinguish multiple qualifying births, while the balance-calendar configuration establishes the 12-month window for each event.

Study Guide reference: Leave of Absence – Additional Information on the Balance Calendar .

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 .