Which information is typically included in a "Data Load Job"?

The inclusion of the type of data being loaded and load configuration in a "Data Load Job" is essential as it sets the foundation for the entire data loading process. When initiating a data load job in Workday, implementers must define the specific data type, such as employee records, financial data, or custom object data. This allows Workday to understand how to process the incoming data correctly.

Additionally, the load configuration specifies how the data should be handled—this includes settings such as mapping fields, determining how to deal with duplicates, and specifying whether data should be merged or replaced. By clearly outlining these parameters, organizations ensure that data integrity is maintained and that the data load job proceeds without unintended errors or complications.

In contrast, the other options do not typically pertain to the immediate requirements of a data load job. The amount of storage space used is more relevant to system performance and management rather than the specifics of the data load itself. Similarly, while tracking users involved or having backup schedules is important for overall data governance and operational best practices, they are not core components of the load job configuration. Therefore, focusing on the type of data and load configuration is crucial for the effective execution of a data load job in Workday.