The correct answer is B. Alpha-Numeric .

In Workday Time Tracking, calculation priorities are defined using an alpha-numeric field . This allows organizations to create priority values that include both letters and numbers , such as USA0045 or USA_HRL_50 , depending on how the tenant’s naming convention is structured. Workday uses these values to control the order in which time calculations run, with lower priority values generally processing before higher ones.

An alpha-numeric format is useful because it provides flexibility. The alphabetic portion can identify a country, worker group, pay group, or processing category, while the numeric portion establishes the sequence. This helps administrators organize time calculations in a way that is both readable and scalable, especially when many calculation rules exist across different populations.

The other options are incorrect because they do not support how Workday defines calculation priorities. A Lookup field would reference another object rather than store a structured priority code directly. A Boolean field only supports true/false values, which would not be enough to define processing order. A Date field is designed for calendar-based values and has no role in sequencing time calculations.

Therefore, the field type used to define Time Tracking Calculation priorities in Workday is Alpha-Numeric .

The correct answer is B. USA_HRL_40 .

In Workday Time Tracking, time calculation priorities control the sequence in which calculations run . Lower priority numbers run first, and higher numbers run later. The calculation Weekly OT > 40 Hours has priority USA_HRL_50 and explicitly includes the tag “1-Holiday Double Time.” This means the system expects the Holiday Double Time tag to already exist before the Weekly OT calculation executes .

Therefore, the calculation that generates the 1-Holiday Double Time tag must run before priority 50 so that the Weekly OT calculation can recognize those tagged hours when it evaluates overtime eligibility.

Looking at the options:

USA_SAL_10 is used for salaried logic and not appropriate for hourly worker calculations.

USA_HRL_55 would run after Weekly OT > 40 Hours, which is incorrect.

USA_HRL_45 would run before 50, but the standard Workday configuration typically places holiday or premium tagging calculations earlier in the sequence so downstream overtime rules can reference them consistently.

Thus USA_HRL_40 is the most appropriate priority because it executes before Weekly OT > 40 Hours (USA_HRL_50) while still allowing earlier calculations such as Night Shift or other hourly rules to run first if needed.

This ensures that Holiday Double Time hours are correctly tagged before weekly overtime calculations evaluate total hours and remove or replace the Regular tag where necessary.

The correct answer is B. Import Reported Time Blocks .

In Workday Time Tracking, when an organization needs to load legacy time entry data into the tenant for configuration testing , the appropriate Enterprise Interface Builder (EIB) is Import Reported Time Blocks . This EIB is specifically designed to bring in historical or external reported time entries so that organizations can validate how Workday processes time calculations, overtime rules, validations, approvals, and downstream integrations using realistic data.

This is especially useful during implementation or testing cycles when the team wants to confirm that configured time entry templates, time calculations, and administrative processes behave correctly with actual time data patterns from the legacy system. By importing reported time blocks, Workday can apply the configured rules and allow testers to compare expected and actual outcomes.

The other options are not intended for loading time entry history. Payroll Input is used for payroll-related input data, not for time entry blocks. Put Period Schedule is used to maintain or load period schedule information. Put Holiday Calendar is for holiday setup, not worker time records. None of those options load the detailed reported worked-time entries needed for time tracking configuration testing.

Therefore, the correct EIB for loading legacy time entry data into Workday Time Tracking is Import Reported Time Blocks .