Refer to the following scenario to answer the question below. You need to configure a Core Connector: Candidate Outbound integration for your vendor…

The most accurate method to meet this requirement is by using the Configure Integration Services task for the integration system. This task allows you to define the behavior of the services the connector uses, such as the Data Initialization Service (DIS). Within this configuration, you can set the Transaction Log Criteria to subscribe to specific business process transaction types. By subscribing to the "candidate assessment" event, the integration will process and output only the candidates who have undergone that specific event, fulfilling the vendor's requirement.

B. Set the integration transaction log to subscribe to specific transaction types.

This action is correct, but it is a specific step performed within the broader Configure Integration Services task. Option A is the more comprehensive answer as it names the overall task required.

C. Make the Candidate Assessment field required in integration field attributes.

This option controls field-level validation, not record-level inclusion. It would cause an error for a record if the field were blank, rather than filtering the dataset based on an event.

D. Create an integration map to output values for candidates with assessments.

An integration map is for data transformation, not data selection. Filtering at this stage is inefficient as the integration would have already extracted a larger, unfiltered set of data.

1. Workday Documentation

"Core Connectors and Document Transformation": This guide details the configuration of Core Connectors. It specifies that the Configure Integration Services task is the primary interface for defining the data scope and behavior of services like the Data Initialization Service. The guide explains that within this task

an administrator configures the "Transaction Log Criteria" to subscribe to specific business process events

which is the mechanism for event-based filtering. (Note: Access to specific Workday documentation requires a Workday Community account).

2. Workday Documentation

"Integration Services in Workday Studio": While focused on Studio

this document explains the underlying services. It describes the Data Initialization Service (DIS) and its reliance on the transaction log for capturing incremental changes or building an initial data set based on historical business process events. The configuration of these services is consistently referenced as being managed through the Configure Integration Services UI task on the integration system.