What calculated field type will you use to calculate the number of holidays a worker has in a time week?
Correct Answer: B
Explanation:
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 .
Question 2
What type of field is used to define Time Tracking Calculation priorities?
Correct Answer: B
Explanation:
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 .
Question 3
You create a Sum Related Instances calculated field to add the total number of hours worked in a week with a specific time entry code.
What is the related business object of the Sum Related Instances calculation?
Correct Answer: A
Explanation:
The correct answer is A. Time Block .
In Workday Time Tracking, a Sum Related Instances calculated field is used when you want to total values from a set of related records. In this scenario, the goal is to add up the hours worked in a week for entries that use a particular time entry code . Although the overall calculation context may be weekly, the actual hours being summed come from the individual time records , which are stored as Time Blocks . That is why the related business object for the Sum Related Instances calculation is Time Block . Each time block contains the detailed reported time information, including hours, time entry code, and other attributes used for filtering and summing. The weekly total is produced by summing the qualifying Time Block records associated with the week. The other options are not correct as the related object for the sum itself. Time Entry Code is a filter attribute, not the object containing the hours to total. Time Week is the broader context or parent level for the calculation, but it is not the related instance being summed. Time Calculation Tag is also an identifying or filtering element used in calculations, not the transactional object that stores the hour values. So, for a Sum Related Instances field totaling weekly hours by a specific entry code, the related business object is Time Block .
Demo Practice Mode
You are viewing only the questions marked as Demo.