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 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 B. Alpha-Numeric .

In Workday Time Tracking, calculation priorities are defined using an alpha-numeric field . This allows organizations to create priority values that include both letters and numbers , such as USA0045 or USA_HRL_50 , depending on how the tenant’s naming convention is structured. Workday uses these values to control the order in which time calculations run, with lower priority values generally processing before higher ones.

An alpha-numeric format is useful because it provides flexibility. The alphabetic portion can identify a country, worker group, pay group, or processing category, while the numeric portion establishes the sequence. This helps administrators organize time calculations in a way that is both readable and scalable, especially when many calculation rules exist across different populations.

The other options are incorrect because they do not support how Workday defines calculation priorities. A Lookup field would reference another object rather than store a structured priority code directly. A Boolean field only supports true/false values, which would not be enough to define processing order. A Date field is designed for calendar-based values and has no role in sequencing time calculations.

Therefore, the field type used to define Time Tracking Calculation priorities in Workday is Alpha-Numeric .

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 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 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 B. Overwrite existing time blocks containing the default time entry code .

In Workday Time Tracking, the auto-fill feature on a Time Entry Template is designed to prepopulate time for workers using the default time entry code configured on that template. Its purpose is to make time entry faster and more consistent by filling expected hours automatically, usually for standard schedules or routine work patterns.

When auto-fill is used, Workday can overwrite existing time blocks that already contain that same default time entry code . This is important because the system assumes those blocks are part of the auto-fill pattern and can be refreshed or replaced to match the current template logic. However, Workday does not use auto-fill to delete or overwrite time off entries , because time off is a separate type of entry with different business meaning and approval implications.

That makes options A , C , and D incorrect. Workday does not delete time off entries for the current or following week as part of standard auto-fill behavior, and it does not overwrite time blocks containing time off entries. Auto-fill is intended to work with regular time entry patterns, especially those tied to the default time entry code on the template.

Therefore, the correct answer is B