Workday-Pro-Absence Exam Dumps and Practice Questions

Balance tracking is a foundational and non-editable characteristic of a time off plan after the plan is saved. Workday specifically identifies Track Balance, Period Schedule, and Unit of Time as fields that cannot be changed after creating and saving the plan. Consequently, an administrator cannot convert the existing plan into a non-balance-tracking plan by clearing either the Track Balance setting or its balance period.

A balance-tracking plan contains architecture that is not present in a basic plan, including a balance period, accrual calculations, carryover behavior, upper and lower limits, balance visibility, and accrual and time-off balance processing. Removing only the balance period would leave the plan configuration internally inconsistent. Adding another accrual would further reinforce balance tracking rather than remove it.

The correct remediation is to remove the incorrectly configured plan and create a new basic time off plan without balance tracking. Before deletion, the administrator should confirm that no production time off requests, accrual results, adjustments, or other transactions depend on the plan. If operational data already exists, the replacement requires controlled migration and effective-dated planning rather than an immediate deletion. Within the stated scenario, deletion and recreation is the valid configuration response.

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.

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.

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.

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.