Workday Workday-Pro-Time-Tracking Practice Test Questions Answers

The correct answer is D. Remove Tags . In the scenario, the calculation is built to evaluate time that currently has the Regular calculation tag because Include Calculation Tags contains Regular . That part is correct, since the calculation must first identify which hours are eligible to be converted into daily overtime. The problem is in the result of the calculation: the hours are being given the Daily Overtime tag, but the original Regular tag is not being removed. As a result, the same hours appear with both tags.

In Workday Time Tracking, Add Tags is used to place a new calculation tag on qualifying hours, while Remove Tags is used to take away a tag that should no longer remain on those hours after the calculation runs. For a daily overtime rule, once hours greater than the threshold qualify as overtime, those hours should no longer stay tagged as Regular. Therefore, you must update the calculation to remove the Regular tag in the Remove Tags field.

The other options do not solve the issue. Period only defines the time frame, and Include Calculation Tags controls which hours are evaluated, not which old tag is cleared from the result.

The correct answer is A. Time Week .

In Workday Time Tracking, the top-level business object should match the level at which the validation needs to evaluate data. This question asks for a warning if a worker has multiple time blocks with overtime in a time period . Because the requirement is not limited to a single block or a single day, Workday must evaluate time across a broader period and determine whether multiple qualifying overtime blocks exist within that span. For this kind of period-based validation, Time Week is the correct top-level business object.

Using Time Week allows the validation to review all related time blocks within the weekly time context and count or evaluate how many overtime-related blocks exist. This is appropriate when the validation logic depends on a grouped time period rather than on an individual transaction.

The other options are less suitable. Time Block is too granular because it only represents one specific entry and cannot serve as the best top-level object for evaluating multiple blocks across a period. Time Day would only evaluate one day at a time, not the broader time period. Worker is too general and does not provide the specific time-period structure needed for this validation design.

Therefore, for a validation checking multiple overtime time blocks within a time period, the correct top-level business object is Time Week .

The correct answer is B. Count Related Instances .

In Workday Time Tracking, when the requirement is to determine how many holidays occur for a worker within a time week , the calculation is about counting occurrences of related records that meet certain criteria. That is exactly what Count Related Instances is designed to do. It counts the number of related objects or records associated with the parent business object, typically after applying a filter such as days marked as holidays.

In this scenario, the parent context is the time week , and the system needs to count how many related day-level instances in that week qualify as holidays. Because the requirement is a numeric count of instances , not a sum of hours or a mathematical formula, Count Related Instances is the most appropriate calculated field type.

The other options do not match the business need. Arithmetic is used when combining numeric values through math operations, but first you would still need the holiday count itself. Lookup Related Value retrieves a value from a related object, not the number of occurrences. Date Difference calculates the difference between two dates and is not intended for counting holiday days in a week.

Therefore, for calculating the number of holidays in a time week, the correct calculated field type is Count Related Instances .

The correct answer is D. Six regular hours on April 05 and two regular hours on April 06 .

In Workday Time Tracking, a Day Breaker determines when one workday ends and the next workday begins for time calculation purposes. When the Day Breaker is set to 2:00 AM , any time worked before 2:00 AM is treated as belonging to the previous day , and any time worked at or after 2:00 AM belongs to the current day .

In this example, the worker enters time from 8:00 PM on April 05 to 4:00 AM on April 06 , which equals 8 total hours . These hours split as follows:

8:00 PM to 12:00 AM = 4 hours on April 05

12:00 AM to 2:00 AM = 2 hours, but because of the 2:00 AM Day Breaker, these hours still belong to April 05

2:00 AM to 4:00 AM = 2 hours that belong to April 06

That produces:

6 regular hours on April 05

2 regular hours on April 06

The key concept is that Workday does not simply split time at midnight when a Day Breaker is defined. Instead, it uses the configured Day Breaker to assign hours to the proper workday for scheduling, calculations, and reporting.

The correct answer is B. On the Calculated tab in the Time Block in the Worker’s Time Entry Calendar on the day the hours were worked .

In Workday Time Tracking, a Time Calculation Tag is part of the calculation framework used to identify or classify time after Workday evaluates the entered hours through configured calculation logic. When a rule tags hours worked on the seventh consecutive day , that result is not treated as the original entered time itself. Instead, it is displayed as a calculated result tied to the time block for the relevant date.

That is why these tagged hours appear on the Calculated tab of the worker’s time block. The entered line remains the source time entry, while the calculated section shows the results produced by Workday’s time calculations, such as tagged hours, overtime, premiums, or other rule-based outcomes.

Option D is incorrect because the top line of the time block is generally where the worker’s entered time appears, not the detailed calculation-tag output. Option A is incorrect because the Work Schedule Calendar reflects planned schedule information, not calculated time-tag results. Option C is incorrect because View Worker’s Time Eligibility is used to review assigned time tracking components, not to display daily calculated tagged hours.

So the correct display location is the Calculated tab in the time block.