In XSLT, the processor applies transformation rules by matching nodes using XPath expressions inside <xsl:
template match=""> statements.
"Templates define the rule, and XPath expressions determine which nodes they apply to." This is the foundational mechanism by which XSLT processes XML data.
Why the others are incorrect:
* B. The <xsl:stylesheet> element defines scope, not node matching.
* C. <xsl:call-template> invokes a named template but does not itself match nodes.
* D. Namespace prefixes are used within XPath, but node matching is based on XPath.
Reference:W3C XSLT 1.0 Specification - xsl:template and XPath MatchingWorkday Integration Training -
"How XSLT Applies Rules to XML Output"

Population Eligibility controls which workers are included in the Core Connector output population. In this scenario, the Population Eligibility is configured to include all US workers, so the connector correctly outputs that entire eligible population. The Eligibility Criterion field does not replace Population Eligibility as the population filter. It can support eligibility-related logic, but it is not the correct place to enforce the final worker population restriction when the actual extract should include only Sales workers. To fix the output, the Sales organization condition must be moved into the Population Eligibility rule itself. Updating the criterion field or running a full file would not solve the problem because the population filter would still include all US workers. The integration population must be filtered at the source.

The scenario describes a Core Connector: Worker integration configured to output Position Title and Business Title fields for workers who meet the Integration Population Eligibility criteria (Is Manager = true), with the Transaction Log service subscribed to the " Position Edit Event. " The integration is launched with specific date parameters, and a test is performed by updating Jared Ellis' Business Title via an " Edit Position " action.
Jared is a manager, and the change is logged with an effective date of 05/27/2024 and an entry moment of 05
/24/2024 07:58:53 AM. Despite this, Jared does not appear in the output. Let's analyze why and determine the configuration element that needs modification.
In Workday, the Core Connector: Worker integration relies on the Transaction Log service to detect changes based on subscribed transaction types and processes them according to the date launch parameters. The integration is configured as an incremental run (since " Last Successful " parameters are provided), meaning it captures changes that occurred since the last successful run, within the specified date ranges. The date launch parameters are:
* As of Entry Moment: 05/25/2024 12:00:00 AM - The latest point for when changes were entered into the system.
* Effective Date: 05/25/2024 - The latest effective date for changes to be considered.
* Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM - The starting point for entry moments from the last run.
* Last Successful Effective Date: 05/23/2024 - The starting point for effective dates from the last run.
For an incremental run, Workday processes changes where:
* The Entry Moment falls between the Last Successful As of Entry Moment (05/23/2024 12:00:00 AM) and the As of Entry Moment (05/25/2024 12:00:00 AM), and
* The Effective Date falls between the Last Successful Effective Date (05/23/2024) and the Effective Date (05/25/2024).
Now, let's evaluate Jared Ellis' change:
* Entry Moment: 05/24/2024 07:58:53 AM - This falls within the range of 05/23/2024 12:00:00 AM to 05
/25/2024 12:00:00 AM, so the entry timing is captured correctly.
* Effective Date: 05/27/2024 - This is after the Effective Date of 05/25/2024 specified in the launch parameters.
The issue arises with the Effective Date. The integration only processes changes with an effective date between 05/23/2024 (Last Successful Effective Date) and 05/25/2024 (Effective Date). Jared's change, with an effective date of 05/27/2024, falls outside this range. In Workday, the effective date determines when a change takes effect, and incremental integrations rely on this date to filter relevant transactions. Even though the entry moment (when the change was entered) is within the specified window, the effective date being in the future (relative to the integration's Effective Date of 05/25/2024) excludes Jared from the output.
To include Jared Ellis in the output, the Date launch parameters must be modified. Specifically, the Effective Date needs to be adjusted to a date that includes 05/27/2024 (e.g., 05/27/2024 or later). This ensures the integration captures changes effective up to or beyond Jared's edit. Alternatively, if the intent is to process future-dated changes entered within the current window, the integration could be adjusted to consider the entry moment as the primary filter, though this would typically require a different configuration approach (e.
g., full file mode or a custom report, not standard incremental behavior).
Let's evaluate the other options:
* A. Integration Population Eligibility: Set to " Is Manager = true, " and Jared is a manager. This filter is correct and does not need modification.
* C. Integration Field Attributes: Configured to output Position Title and Business Title, and the change to Business Title is within scope. The field configuration is appropriate.
* D. Transaction log subscription: Subscribed to " Position Edit Event, " which matches the " Edit Position " action performed on Jared. The subscription type is correct.
The mismatch between the integration's Effective Date (05/25/2024) and Jared's change effective date (05/27
/2024) is the reason for exclusion, making B. Date launch parameters the correct answer.
Workday Pro Integrations Study Guide References
* Workday Integrations Study Guide: Core Connector: Worker - Section on " Change Detection " explains how effective dates and entry moments govern incremental processing.
* Workday Integrations Study Guide: Launch Parameters - Details the roles of " Effective Date " and " As of Entry Moment " in filtering changes, emphasizing that incremental runs focus on the effective date range.
* Workday Integrations Study Guide: Incremental Processing - Describes how future-dated changes (effective dates beyond the launch parameter) are excluded unless the parameters are adjusted accordingly.

The <xsl:template> is the core component in XSLT. It defines the transformation rules that will be applied to nodes in the XML document.
"Without at least one <xsl:template> element, an XSLT file cannot perform any transformation. This is the execution block where processing logic begins." Why the others are incorrect:
* B. <xsl:apply-templates> applies templates but is not valid without the actual template definitions.
* C. <xsl:call-template> calls named templates - which must first exist.
* D. <xsl:output> defines format but does not perform transformation logic.
Reference:W3C XSLT Specification - Section: xsl:template Required for ExecutionWorkday XSLT Examples - "Template-Based Transformations in Workday"