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 .

The correct answer is B. Only the validations in the validation group .

In Workday Time Tracking, validations are typically assigned to workers through Validation Groups , not simply by creating the validation itself. A worker becomes subject to the validations contained in the group for which they are eligible. In this scenario, the worker is eligible for a validation group that contains only Unsubmitted Time and Cannot Work on a Holiday . Since the new validation, Cannot Work on Sunday , was not added to any validation group , it is not delivered to the worker through eligibility.

This is a key setup concept in Workday: creating a validation does not automatically make workers subject to it. The validation must be included in the appropriate Validation Group , and the worker must be eligible for that group. Because the new Sunday validation was left outside the group, the worker continues to receive only the validations already included in the assigned group.

Option A is incorrect because the new validation alone is not independently assigned. Option C is incorrect because validation eligibility is not applied in isolation here; group membership drives delivery. Option D is incorrect because the worker will not receive the third validation unless it is added to a validation group for which they are eligible.

Therefore, the worker is eligible for only the validations in the validation group

The correct answer is D. Time Day and Time Block .

In Workday Time Tracking, a validation that prevents or warns against time entry on a holiday must evaluate both the date context and the entered time record . The Time Day business object is used to determine day-level attributes, such as whether the date is a holiday. The Time Block business object is used to evaluate the actual time entry being submitted or edited. Together, these two objects give Workday the information it needs to create a critical validation that checks whether a worker is trying to enter time on a holiday.

This pairing is appropriate because the holiday condition itself exists at the day level , while the transaction being controlled is the time block . A critical validation can then be configured to trigger when a time block is entered on a day identified as a holiday.

The other options are less appropriate. Worker may be useful for worker-specific eligibility or attributes, but it does not provide the direct day-and-entry combination needed for this specific validation. Time Shift is related more to scheduled shift context and is not the primary business object for validating holiday entry against submitted time blocks.

Therefore, to create a critical validation that reminds or restricts workers from entering time on a holiday, the correct business objects are Time Day and Time Block .

The correct answer is C. Up to 5 years .

In Workday Time Tracking, the Generate Period Schedule task is used to create future time periods in bulk for a defined period schedule. Rather than manually creating each period one at a time, administrators can use this task to automatically generate a set of future periods so workers, managers, approvals, and downstream payroll processing all have the required calendar structure in place. Workday allows this generation to extend up to 5 years , which gives organizations enough coverage for long-term schedule planning and administrative continuity.

This limit is important because period schedules drive the availability of time entry periods, review cycles, approvals, and closing processes. Generating too short a range may require frequent maintenance, while the system does not allow unlimited generation because controlled administrative maintenance is still expected. That is why Indefinitely is not correct.

The other options are too limited for standard Workday administration. Up to 1 year and Up to 2 years may sound reasonable for some organizations operationally, but they do not reflect the actual supported maximum of the Generate Period Schedule task. Workday provides a broader generation window to reduce repetitive administrative effort.

So, the correct answer is C. Up to 5 years .

The correct answer is D. Time Entry template .

In Workday Time Tracking, the Time Entry template controls the structure of the time entry experience for a group of workers. This includes what fields appear during time entry, how time is entered, and whether certain information must be provided before a worker can submit time. When a business wants to make a worktag required , that requirement is configured through the Time Entry template , because the template governs the entry rules and data capture requirements presented to the worker.

This is the correct design point because worktags such as cost center, project, grant, or other organizational tracking values are often needed at the point of entry for labor costing, reporting, or downstream payroll and financial processing. By making the worktag required in the template, Workday enforces that workers supply that value whenever they enter qualifying time.

The other options are not the primary place for this setup. A Worktag is the classification object itself, not the entry-rule configuration component. A Time entry code identifies the type of time being reported, such as regular or training time, but it does not generally control whether a worktag is universally required in the entry interface. A Time Calculation tag is used for calculation logic, not for entry field requirements.

So the correct answer is D. Time Entry template .

The correct answer is C. Time Calculation Group .

In Workday Time Tracking, a Time Calculation Group is the component that bundles together the time calculations that apply to a specific worker population. If a worker should receive special overtime or double-time logic—such as double time for hours over 8 on the seventh consecutive day —the worker must be eligible for the appropriate Time Calculation Group that contains those rules.

In this scenario, the worker’s time is being tagged as seventh consecutive day hours, but the expected split into double time after 8 hours is not occurring. That strongly suggests the worker is not currently eligible for the calculation group that includes the seventh consecutive day double-time calculation . Making the worker eligible for the correct calculation group ensures Workday runs the additional rule needed to reclassify hours over the threshold.

The other options are not correct for this purpose. A Time Entry Template controls how time is entered, not how overtime logic is calculated. A Time Calculation Tag is a result or identifier used by calculations, not an eligibility-based worker component. A Time Code Group organizes time entry codes, but it does not determine whether complex overtime calculations are applied.

Therefore, the worker should be made eligible for the appropriate Time Calculation Group