Workday Pro Time Tracking Exam Questions

Answer : B

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.

Answer : A

The correct answer is A. Salaried workers adjusting their auto-fill from schedule hours.

In Workday Time Tracking, Mass Submit Time is most commonly used for worker populations whose time is largely predictable and auto-generated, especially salaried workers who use auto-fill from schedule hours. These workers often have standard scheduled hours and may only make small adjustments before time needs to be submitted. Because their time is generally consistent, administrators can efficiently submit time in bulk for many workers at once, which reduces manual effort and supports period-end processing.

This function is less appropriate for populations with more variable or punch-based time entry. Hours-only workers using micro-edit may still require individual changes that make bulk submission less common. In/Out workers using check-in/check-out functionality rely on punch data and break patterns, so their entries often need closer review before submission. Project workers using enter time by type usually allocate time across projects, tasks, or worktags, making their time more complex and less suitable for broad mass submission.

Mass Submit Time is most valuable when time entry follows a stable pattern and does not require frequent day-by-day validation. That is why salaried workers with auto-fill from schedule hours are the most common population for this administrative action.

Answer : A

The correct answer is A. Include Calculation Tags grid.

In Workday Time Tracking, the Include Calculation Tags section determines which hours are evaluated by a specific time calculation. For a rule such as Seventh Consecutive Day Double Time, Workday looks at the hours that already carry certain calculation tags and uses those tagged hours to determine whether the threshold for double time has been reached. In other words, the hours that count toward the seventh consecutive day double-time rule are identified in the Include Calculation Tags grid.

This is different from the Add Tags field, which defines the result of the calculation by specifying the tag that will be added after the criteria are met. The Remove Tags field controls which tags should be removed once the calculation applies. The Time Calculation Group grid is not where the hours are identified; it simply groups related calculations for worker eligibility and execution.

In this scenario, if all 11 hours remain tagged as seventh consecutive day hours instead of splitting after 8 hours, reviewing the Include Calculation Tags grid is essential because it shows exactly which tagged hours Workday is counting toward the threshold. That is the configuration area that determines the hours considered for the seventh consecutive day double-time calculation.

Therefore, the correct answer is A.

Answer : C

The correct answer is C. USA_HRL_70. In this scenario, the new calculation is designed to evaluate hours that already have the 1-Supervisor Premium tag. In the report, the existing 1-Supervisor Premium calculation has a priority of USA_HRL_60. In Workday Time Tracking, when a calculation depends on the output of another calculation, it must run after the earlier calculation has already assigned its tag. Otherwise, the new calculation would run too soon and would not find the tagged hours it is supposed to evaluate.

Because this new weekly calculation is specifically looking for hours with the 1-Supervisor Premium tag that exceed 20 hours in a week, it must be placed at a priority after USA_HRL_60. Among the answer choices, USA_HRL_70 is the correct next priority that ensures proper sequencing.

The other options are not appropriate. USA_HRL_30 and USA_HRL_10 would run before the Supervisor Premium calculation, so the required tag would not yet exist. USA_HRL_60 is the same priority as the existing calculation and does not clearly guarantee the dependent logic runs afterward. Therefore, the best and correct priority for the new calculation is USA_HRL_70.

Answer : B

The correct answer is B. Lock Time Entry.

In Workday Time Tracking, Lock Time Entry is the function used when an organization wants historical reported time and calculated time results to be locked from further editing by any user. This is typically used after time has been finalized and organizations want to preserve data integrity for payroll, audit, compliance, and historical recordkeeping. Once time is locked, Workday prevents normal editing activity against that time data, which makes it the strongest control for protecting finalized history.

This is different from Close Time Entry. Closing time entry generally controls whether a time entry period is open for entry and processing, but it is not the same as applying a hard lock to historical data. Unlock for Adjustments is the opposite action, used when previously locked time must be reopened in a controlled way for corrections. Open Time Entry is used to allow time entry activity, not to secure finalized data.

The wording in the question is important: it asks for a function that ensures historical reported and calculated time data is permanently locked from editing by any user. In Workday Time Tracking, that requirement aligns most directly with Lock Time Entry, because it is specifically intended to secure finalized time data from further modification.

Answer : D

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.

Answer : B

The correct answer is B. Time calculation. In Workday Time Tracking, daily and weekly totals on a worker's time entry calendar are driven through the Time Calculation framework. Time calculations are used to evaluate entered time and produce results such as totals, overtime, premiums, exceptions, and other rule-based outcomes. When Workday needs to total time across a day or across a week, that logic is configured in a time calculation because calculations define how time is interpreted, accumulated, and processed.

The other options do not control this type of totaling behavior. A time calculation tag is mainly used to organize or identify calculations, not to perform the actual totaling logic. A time entry code identifies the type of time being entered, such as regular hours, training, or on-call time, but it does not define calendar total behavior. A time entry template helps control the layout or default structure for time entry, but it is not where daily or weekly total rules are configured.

So, if the question asks specifically where Workday configures the totals shown for a worker's calendar, the best and correct choice is Time calculation.