Free Workday Workday-Pro-Time-Tracking Practice Exam with Questions & Answers

The correct answer is B. Assign an eligibility rule to the new time calculation group and make only the California full-time workers eligible.

In Workday Time Tracking, Time Calculation Groups are used to bundle multiple time calculations together so that a specific population of workers receives the appropriate rules. Eligibility for these groups is controlled through Time Tracking Eligibility Rules , which determine which workers should receive a particular configuration.

In this scenario, US full-time workers already have a calculation group that handles weekly overtime after 40 hours . California workers, however, have additional legal requirements , including daily overtime after 8 hours, double time after 12 hours, and overtime rules related to consecutive days worked. Because these rules apply only to California workers, they must be placed in a separate time calculation group and assigned only to that population.

The correct approach is to configure an eligibility rule that identifies California full-time workers (for example using worker location, country/state, or supervisory organization attributes) and attach that rule to the new California time calculation group.

The other options are incorrect because they either apply the California rules to all US workers or fail to include the full set of required calculations. Therefore, using a specific eligibility rule for California full-time workers is the correct configuration approach.

The correct answer is D. Callback must be configured on the Advanced tab on the time entry code . In Workday Time Tracking, when a specific type of entered time such as callback time needs to be recognized only by certain time calculations, that behavior is typically controlled through calculation tags associated with the time entry code . These settings are maintained on the Advanced configuration area of the time entry code, where Workday allows the code to be tied to the appropriate calculation logic.

This setup is important because callback hours are usually different from regular worked hours and often need separate treatment for premiums, overtime rules, or special pay outcomes. By configuring the Callback-related calculation behavior directly on the time entry code, Workday ensures that only time calculations referencing the Callback tag evaluate that entry in the intended way.

Option A is incorrect because leaving the default calculation tag blank would not specifically direct callback entries into callback-based calculations. Option B is incorrect because a “temporary Time Calculation tag” is not the correct setup approach for a permanent time entry type like callback. Option C is incorrect because callback absolutely can and often should be configured as a distinct time entry code for accurate tracking and payroll-related calculation logic.

The correct answer is A. USA0040 .

In Workday Time Tracking, time calculation priority determines the order in which calculations are processed. A calculation with a lower priority value runs before a calculation with a higher value. Since the existing Daily Overtime calculation has a priority of USA0045 , any new calculation that must run earlier needs a priority number lower than 0045.

Because the organization wants the Daily Double Time rule for hours greater than 12 to calculate before Daily Overtime, the proper priority is USA0040 . This ensures that the double time logic evaluates first and can correctly identify the hours that should receive double time treatment before the broader overtime calculation processes the remaining qualifying hours.

The other options are incorrect for the following reasons. USA0045 would place the new calculation at the same priority as Daily Overtime, which does not ensure the correct processing sequence. USA0050 and USA0055 are higher values, so they would run after the overtime calculation, which could lead to incorrect tagging or pay treatment of hours above 12.

In Workday, correct priority sequencing is critical whenever multiple calculations interact, especially for overtime and premium scenarios. Therefore, the correct priority is USA0040 .

The correct answer is A. Time Block .

In Workday Time Tracking, a Time Block Conditional calculation evaluates conditions at the individual time entry level . When the requirement is to check for adjusted, calculated time , the relevant information is associated with the actual time block record, because that is where Workday stores the entered time and the calculation outcomes tied to that specific entry. A Time Block is the most granular time-related business object and is the correct object to use when testing whether a block has been adjusted or contains calculated results.

This is important because Time Block Conditional logic is intended to inspect and act on specific time blocks rather than broader summarized periods. If you need to determine whether a worker’s time block reflects adjusted calculated time, the evaluation must happen on the Time Block object itself.

The other options are not correct for this use case. Time Shift relates more to shift structure or scheduling context, not the direct record used for conditional evaluation of calculated time. Time Day summarizes time at the day level and is used for daily comparisons or accumulations. Time Week is used for weekly totals and thresholds. Neither Time Day nor Time Week is the right object for checking an individual adjusted, calculated time block.

Therefore, the correct business object is Time Block .

The correct answer is D. Worker .

In Workday Time Tracking, Time Tracking Eligibility Rules are built by selecting a business object and then defining condition rules based on fields available from that object and its related fields. In this scenario, the eligibility criteria include attributes such as Time Type , Country , and Supervisory Organization . These are evaluated in the context of the worker record , because the rule is determining which workers should receive the new Time Tracking components.

The Worker business object is the correct choice because it serves as the central object for worker-specific eligibility evaluation and allows access to related worker attributes, including employment and organizational data. This makes it possible to create one rule that consistently evaluates all three conditions together for a worker population.

The other options are too narrow. Compensation focuses on pay-related data, Position centers on the job position, and Organization focuses on organizational structures. Although some of the required values may relate to those areas, the eligibility rule itself must evaluate them from the perspective of the worker who is being assigned the Time Tracking setup.

That is why the appropriate business object for this rule is Worker .

The correct answer is D. Run time tracking calculations on the period that is being tested .

In Workday Time Tracking, after correcting a configuration issue related to overtime or double-time rules, the system does not confirm the result simply because the setup has been updated. The relevant time calculations must be reprocessed for the time period being tested so Workday can apply the corrected logic to the worker’s reported time. This is especially important in scenarios involving California overtime, where daily overtime, daily double time, and weekly overtime calculations may interact and depend on proper eligibility, grouping, and priority configuration.

Running time tracking calculations ensures that the reported time blocks are reevaluated using the updated configuration. Only then can you verify whether the worker’s hours are now correctly tagged and calculated.

The other options are not appropriate for this validation step. A job change or compensation change affects worker data but does not rerun time calculation logic for the testing period. Run a pay calculation is a payroll activity and occurs downstream from Time Tracking; it does not replace the need to first verify that time has been calculated correctly in Workday Time Tracking.

Therefore, the final action needed to confirm the fix is to run time tracking calculations on the period being tested

The correct answer is C. 3 . On Tuesday , Amanda Baker reported 15 hours . Based on the rules provided, Workday Time Tracking would evaluate those 15 hours against the applicable daily and weekly thresholds. The first 8 hours remain regular hours . Since she worked more than 8 hours in the day, the next block of hours qualifies for daily overtime . Because she also exceeded 12 hours in the same day , the hours above 12 qualify for daily double time .

That means Tuesday’s calculated results would typically be split into three calculation tag categories: Regular , Daily Overtime , and Daily Double Time . This produces a total of 3 time calculation tags on the calculated tab for that day.

The weekly overtime rule does not add a fourth tag for Tuesday. Weekly overtime applies only after total regular hours for the week exceed 40 . By the end of Tuesday, Amanda has worked 10 hours on Monday + 15 hours on Tuesday = 25 total hours , which is still below the weekly 40-hour threshold. Therefore, weekly overtime has not yet been triggered on Tuesday.

So the correct count of calculation tags assigned for Tuesday is 3 .

The correct answer is C. Assign a higher priority to the time calculation for hours worked on the seventh consecutive day.

In Workday Time Tracking, calculation priority determines the order in which time calculations are processed . When multiple calculations depend on each other, the prerequisite calculation must execute first so that its results can be used by subsequent calculations. In this scenario, the first time calculation identifies when a worker reaches a certain number of consecutive days worked . The second calculation specifically evaluates hours worked over 8 hours on the seventh consecutive day .

For the second calculation to work correctly, Workday must already know that the worker has reached the seventh consecutive day threshold . Therefore, the calculation that evaluates hours beyond 8 on that seventh day must run after the initial consecutive-day identification calculation . This is achieved by assigning it a higher priority value , ensuring it processes later in the calculation sequence.

Options A and B are incorrect because Workday does not automatically determine priority between time calculations. Administrators must configure priorities manually. Option D is also incorrect because Time Calculation Groups control eligibility and grouping , not execution order.

Thus, assigning a higher priority to the seventh-day overtime calculation ensures the correct processing sequence and accurate tagging of hours.

The correct answer is D. View Worker’s Time Eligibility .

In Workday Time Tracking, when you want to confirm whether a specific worker has been assigned a period schedule , the most direct report is View Worker’s Time Eligibility . This report is used to review which Time Tracking components a worker is currently eligible for and receiving, including items such as time entry templates, approval templates, and period schedules . Since the question is focused on verifying assignment to a worker , this worker-level eligibility view is the most appropriate choice.

The other options do not fit the requirement as well. Audit - Workers with Multiple Time Period Schedules is an exception report used to identify workers who have more than one schedule, not to simply confirm that a worker has one assigned. View Period Schedule lets you inspect the schedule definition itself, but it is not the best worker-specific confirmation tool. Time Entry Period Schedule Review may sound related, but it is not the standard report used to validate a worker’s eligibility-based assignment in the same direct way.

So, if your goal is to ensure that a particular worker is assigned the correct period schedule, the correct report is View Worker’s Time Eligibility .

The correct answer is D. 1-Minimum Weekly 40 Hours . In the scenario shown, the Priority column lists the calculation priorities as values such as USA_HRL_16 , USA_SAL_10 , USA_HRL_15 , USA_HRL_20 , and USA_HRL_50 . Among the answer choices, 1-Minimum Weekly 40 Hours has the priority USA_SAL_10 , which represents the highest priority in the report because it carries the lowest priority number shown among the listed options.

In Workday Time Tracking, priorities are important because they determine the sequence in which time calculations are applied. This matters when more than one time calculation can affect the same reported time. Higher-priority calculations are evaluated first, and their output may influence later calculations such as overtime, premiums, shift differential, or exception handling. That sequencing is essential to avoid overlap, double counting, or incorrect premium generation.

The other options have lower priority values in the report: 1-Night Shift Differential is USA_HRL_15 , 1-Minimum Rest is USA_HRL_16 , and 1-Weekly Overtime is not the highest priority item shown. Therefore, based on the priority values displayed in the report, the correct choice is 1-Minimum Weekly 40 Hours .