Free Workday Workday-Pro-Time-Tracking Practice Exam with Questions & Answers | Set: 2

The correct answer is C. 8 Regular and 2 Daily OT . In Workday Time Tracking, daily calculations are evaluated based on the hours entered for that specific day, while weekly overtime is applied only after total eligible regular hours for the week exceed the weekly threshold.

Let us total Amanda’s regular hours before Friday. On Monday , she worked 10 hours, which results in 8 Regular + 2 Daily OT . On Tuesday , she worked 15 hours, which results in 8 Regular + 4 Daily OT + 3 Daily Double Time . On Wednesday , she worked 6 Regular hours. On Thursday , she worked 8 Regular hours. That gives her a total of 30 regular hours through Thursday.

On Friday , Amanda worked 10 hours . Applying the daily overtime rule, the first 8 hours are regular and the remaining 2 hours become Daily OT . At that point, her total regular hours for the week become 38 (30 + 8), which is still below the weekly overtime threshold of 40 . Because weekly overtime has not yet been reached on Friday, none of Friday’s hours convert to Weekly OT.

Therefore, Friday’s calculated hours are 8 Regular and 2 Daily OT .

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 C. A worker cannot adjust their own calculated time .

In Workday Time Tracking, the Adjust Calculated Time task is an administrative function used to correct or override calculated time results, such as overtime or premium outcomes, when the automatically generated result needs manual intervention. Because this task can directly change calculation outcomes that affect pay, compliance, and reporting, Workday restricts it from being performed by the worker on their own time. Instead, it is intended for authorized administrative roles, such as a time tracking administrator or another appropriately secured user.

Option A is incorrect because time off is not generally the focus of the Adjust Calculated Time task; this task is used for calculated worked-time results, not for adjusting absence or time-off entries in the same way. Option B is not the best restriction stated here because period locking rules relate to broader time-entry administration and do not define the core restriction of who can perform the task. Option D is incorrect because once calculated time is manually adjusted, it is no longer simply treated the same as fully system-calculated normal time; the adjustment reflects an administrative override.

Therefore, the key restriction that applies is that a worker cannot adjust their own calculated time , making C the correct answer.

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 D. The hours are tagged with the Callback Guaranteed Time Calculation Tag .

In Workday Time Tracking, when a default calculation tag is assigned to a Time Entry Code , that tag is automatically applied to time reported with that code unless other calculation logic changes the outcome. This means the time entry itself carries the designated calculation tag into the time calculation process. In this case, if the Time Entry Code has a default calculation tag of Callback Guaranteed Time , then any hours entered using that code will be tagged with Callback Guaranteed Time .

This setup is commonly used to ensure specific kinds of time are consistently identified for later calculation logic, such as guaranteed callback minimums, premiums, or special pay treatment. The tag itself does not automatically determine the pay rate; instead, it marks the hours so the relevant time calculations can recognize and process them correctly.

Option A is incorrect because the worker’s Work Schedule Calendar does not control the default calculation tag placed on a Time Entry Code. Option B is incorrect because the Time Entry Template does not retag the reported time to another default code in this way. Option C is incorrect because assigning a calculation tag alone does not directly guarantee payment at time and a half; pay outcomes depend on downstream calculation and payroll configuration.

The correct answer is C. Lookup Value As of Date .

In Workday Time Tracking, when you need to determine the value of a worker-related attribute on a specific date , the appropriate calculated field type is Lookup Value As of Date . In this scenario, the requirement is to know the worker’s leave status on the date tied to a particular time block . Because leave status can vary over time, the calculation must return the value that was effective as of the time block date , not just the worker’s current status.

This is exactly what Lookup Value As of Date is designed to do. It allows Workday to evaluate an effective-dated field and return the correct value for the specified date context. That makes it especially useful in Time Tracking calculations where the date of the time block is critical for determining eligibility, status, or rule outcomes.

The other options do not meet this requirement. True/False Condition only evaluates whether a condition is met and does not retrieve the dated value itself. Date Difference calculates the number of days between two dates, which is unrelated here. Arithmetic is used for numeric calculations and cannot return an effective-dated status value.

Therefore, for finding a worker’s leave status on the date of a specific time block, the correct calculated field is Lookup Value As of Date .