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. Run the Audit - Workers with Multiple Time Entry Templates report to confirm that there are overlapping assignments .

In Workday Time Tracking, a worker should generally be eligible for only one active time entry template at a time . If a worker already has an existing template assignment and also meets the criteria for a newly created template, the most common issue is overlapping eligibility between templates. When this happens, Workday administrators need an audit tool that specifically identifies workers who match more than one template at the same time.

The Audit - Workers with Multiple Time Entry Templates report is built for exactly this troubleshooting scenario. It helps confirm whether the worker is being picked up by multiple eligibility rules and whether an overlap is preventing the expected result or creating assignment ambiguity. This makes it the most accurate report to run when validating time entry template setup.

Option A only lists templates and does not directly expose worker-level overlap issues. Option B focuses on work schedule calendars , which is a different setup area and not related to time entry template conflicts. Option D may provide useful eligibility information, but it is not the primary audit report used to detect overlapping template assignments.

Therefore, the best troubleshooting step is C .

The correct answer is C. Time Calculation Group .

In Workday Time Tracking, a Time Calculation Group is the component that bundles together the time calculations that apply to a specific worker population. If a worker should receive special overtime or double-time logic—such as double time for hours over 8 on the seventh consecutive day —the worker must be eligible for the appropriate Time Calculation Group that contains those rules.

In this scenario, the worker’s time is being tagged as seventh consecutive day hours, but the expected split into double time after 8 hours is not occurring. That strongly suggests the worker is not currently eligible for the calculation group that includes the seventh consecutive day double-time calculation . Making the worker eligible for the correct calculation group ensures Workday runs the additional rule needed to reclassify hours over the threshold.

The other options are not correct for this purpose. A Time Entry Template controls how time is entered, not how overtime logic is calculated. A Time Calculation Tag is a result or identifier used by calculations, not an eligibility-based worker component. A Time Code Group organizes time entry codes, but it does not determine whether complex overtime calculations are applied.

Therefore, the worker should be made eligible for the appropriate Time Calculation Group

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.

The correct answer is D. Ensure Meal is an allowed out reason in the Allowable Types for Out Time .

In Workday Time Tracking, automatically created meal-break time blocks depend on Workday being able to recognize Meal as a valid Out Time reason for the worker’s in/out configuration. If Meal is not included in the Allowable Types for Out Time , the related setup option for automatic meal-break block creation will not be available because the system has no valid meal event type to generate against.

This is a prerequisite relationship in setup: first, the time entry framework must allow Meal as a valid out-time type; only then can Workday support automated handling tied specifically to meal breaks. Without that allowed type, the system cannot distinguish meal-related out times from other kinds of breaks or punches.

Option C is incorrect because Break and Meal are different out reasons in Workday, and the question specifically asks about meal breaks . Options A and B focus on the default in/out pattern, which can influence entry behavior, but they do not represent the key prerequisite that unlocks the automatic meal-break configuration. The system must first recognize Meal as an approved out reason.

The correct answer is B. Adjust Calculated Time .

In Workday Time Tracking, Person B did not automatically receive daily overtime because their normal overtime rules are based on weekly overtime after 40 hours , not daily overtime after 8 hours like Person A in California. Since the system calculated Person B’s time according to their assigned eligibility and time calculation group, the administrator must make a manual correction to the calculated result if they want to grant daily overtime as an exception.

The appropriate task for changing an already calculated overtime outcome is Adjust Calculated Time . This task allows the Time Tracking Administrator to modify calculated time results, such as reclassifying hours into overtime when an exception or special circumstance needs to be recognized outside the normal configured rules.

The other options are not correct for this scenario. Request Overtime is not the standard administrative method for changing system-calculated results. Mass Enter Time is used to enter time in bulk, not to alter overtime calculation outcomes. Enter Time for Worker only records reported time and does not directly grant overtime if the worker’s calculation rules do not support it.

Therefore, when a Time Tracking Administrator needs to manually grant Person B daily overtime, the correct task is Adjust Calculated Time .