Workday Pro Time Tracking Exam Questions

The correct answer is B. Time Week.

In Workday Time Tracking, the business object you choose depends on the level at which the calculation needs to evaluate time. Since the requirement is to count all hours in a week for system-generated break time blocks, the calculation must operate at the weekly level, which makes Time Week the appropriate business object. Time Week is used when Workday needs to total, compare, or evaluate hours across an entire workweek rather than looking at only one block or one day at a time.

This is especially important for time calculations involving accumulated weekly values, such as total break hours, weekly overtime thresholds, or weekly premium eligibility. Because the requirement explicitly says all hours in a week, Workday must evaluate the data in a weekly context, not as isolated entries.

The other options are not correct for this scenario. Time Block is too granular because it evaluates individual entries or blocks of time rather than the total for the week. Time Day would only support daily accumulation, not a full weekly count. Worker is too broad and is typically used for eligibility or worker-level attributes rather than time aggregation logic.

So, for counting break-related system-generated time block hours across a full week, the correct business object is Time Week

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.

The correct answer is D. Ad hoc schedule changes.

In Workday Time Tracking, when a manager assigns a work schedule to a worker using the Assign Work Schedule task, that schedule becomes the worker's standard planned schedule. However, Workday also supports temporary or date-specific exceptions through ad hoc schedule changes. These changes are designed to override the normal assigned schedule for a particular day or period without replacing the worker's overall schedule assignment. This is useful when a worker has a temporary shift change, a one-time different start and end time, or a short-term adjustment due to business needs.

This is why ad hoc schedule changes are considered the override mechanism. They sit on top of the normal schedule assignment and take precedence for the affected dates.

The other options do not override the assigned work schedule itself. Flextime bands provide flexibility around expected start and end times, but they do not replace the assigned schedule. Schedule deviation calculation is used to compare reported time against schedule expectations and identify variances; it analyzes schedule differences rather than overriding the schedule. Work schedule eligible rules determine which workers can receive certain schedules, but they do not act as overrides after assignment.

So, the component that overrides an assigned work schedule is Ad hoc schedule changes.

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 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.