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 .

The worker begins with an annual Illness Leave entitlement of 30 days. The ten days of Illness Leave taken in March reduce the leave balance to 20 days. Because Intermittent Illness Time Off is coordinated with the Illness Leave Type, the two intermittent days taken in May also reduce the leave entitlement. The resulting calculation is:

30 days − 10 leave days − 2 coordinated time off days = 18 days .

Coordinating an intermittent time off with a leave type instructs Workday to include that time off when calculating leave taken. The intermittent time off can reduce both its associated time off plan balance and the coordinated leave entitlement balance because Workday evaluates those balances independently. The time off and leave type must use compatible units of time for the coordination to calculate correctly.

The remaining balance is therefore not 20 days, because that result ignores the intermittent time off. It is not 28 days, because that result ignores the continuous Illness Leave. The entitlement is not restored to 30 days while both events remain inside the same calendar-year balance period.

Study Guide reference: Leave of Absence – Coordinated Leaves and Time Off .

An Evaluate Expression calculated field returns different values according to ordered conditions. The field can evaluate the worker’s country and return 25 for the UK, 18 for the USA, and 22 for Canada. The default value is 20, ensuring that workers in every other country receive the specified entitlement.

Arithmetic Calculation performs operations such as addition, subtraction, multiplication, or division. It does not provide the required country-based branching. Extract Multi-Instance selects one or more instances from a multi-instance field and does not return the required entitlement quantity. A True/False Condition can determine whether a worker belongs to a particular country, but it returns only Boolean results. Those conditions can support the Evaluate Expression field, while Evaluate Expression returns the final numeric entitlement.

Condition order and the default value must be configured carefully so that each worker receives exactly one result. The calculated field should be based on the Worker or Position business object when it is used directly as a leave entitlement calculation. The result can then be selected in the Entitlement Units calculation field of the leave type.

Study Guide reference: Leave of Absence – Calculated Fields Overview and Calculation Equivalencies .

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.

The Workers on Leave report provides a dedicated reporting method for identifying employees who are currently on leave. Setting On Leave Status Visibility Type to Never Show suppresses the “On Leave” indicator that would otherwise appear after an employee’s name. It does not remove the underlying leave event, change the worker’s leave status, or prevent appropriately secured users from reporting on leave records.

The Employee View Time Off report focuses on time off activity rather than the longer-duration leave-of-absence status addressed in the question. My Team’s Time Requests is designed to review time-related requests and their workflow status; it is not the authoritative report for identifying the population currently on leave. View Time Clock History belongs to Workday Time Tracking and reports clock events, not leave-of-absence status.

This distinction supports confidentiality and operational reporting simultaneously. An organization can suppress the broadly displayed On Leave label while still allowing HR administrators or other authorized security groups to identify affected workers through a purpose-specific report. Report access remains governed by the relevant worker-data and leave-of-absence security domains.

Study Guide references: Absence Management Overview – Leave-of-Absence Indicators and Absence Management Administration – Manage Leave of Absence .

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.

Workday automatically recalculates the accrual adjustment when the effective date of the underlying job change is corrected. The adjustment is system-generated from the Change Job business process and is dependent on the job-change effective date, the worker’s eligibility transition, the applicable accrual period, and the accrual’s adjustment configuration. Correcting the source event causes Workday to reevaluate those inputs and update the dependent adjustment.

Manual deletion is neither required nor preferred because it would separate the adjustment from the business event responsible for creating it. The Time Off for Balance Transfer Adjustment field supports balance-transfer scenarios and does not govern recalculation of an accrual adjustment created because the worker lost eligibility. Carryover overrides apply to balances transferred between balance periods and are similarly unrelated to correcting the effective date of a job change.

This automated recalculation prevents an incorrect proration from remaining after the source event changes. For example, moving the job-change date later in the processing period may increase the portion of the period for which the worker was eligible. Workday recalculates the resulting adjustment using the corrected date.

Study Guide reference: Absence Management Administration – Accrual Adjustment during a Job Change , including automated processing associated with Change Job events.

The administrator should configure Start of Period as the accrual frequency method on the time off plan. With Start of Period processing, Workday adds the applicable accrual before subtracting time off for the processing period. This sequence ensures the accrued amount is available in the balance when the corresponding public-duty request is evaluated.

That processing order is particularly important for an Accrue-As-You-Go design. The plan is intended to generate accrual in response to the time-off requirement rather than grant workers a conventional fixed entitlement independently of their requests. Processing the accrual first enables the plan balance to fund the qualifying absence before Workday applies the time-off deduction and lower-limit rules.

Under End of Period, Workday subtracts time off before adding the current-period accrual. That order can cause the request to encounter the lower limit or produce unpaid units before the compensating accrual is applied. An accrual-level override is unnecessary when the required processing method applies to the entire plan. Custom Frequency based on hire date defines an anniversary-style recurring accrual and does not correspond to the variable timing and duration of public-duty requests. Start of Period on the plan therefore provides the correct processing sequence.

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.