WORKDAY-PRO-INTEGRATIONS Practice Questions

In Workday, any modifications made to security policies, such as domain security policies or business process security policies, are not applied in real-time. These changes are held in a pending state. To enforce these modifications across the tenant, an administrator must explicitly run the "Activate Pending Security Policy Changes" task. This task compiles all staged security changes and makes them the currently active configuration. This process ensures that changes are applied deliberately and allows for a review before they go live.

A. Activate Previous Security Timestamp: This task is used to revert or roll back the system's security configuration to a previously saved state, not to apply new, pending changes.

B. Activate All Pending Authentication Policy Changes: This is a distinct task used specifically for activating changes to authentication policies (e.g., password complexity, MFA), not for domain security policies.

D. Activate Metadata Schedule: This is not a valid Workday task. Metadata refreshes are handled differently and are unrelated to activating security policy configurations.

1. Workday Documentation: Workday Security Administration Guide. The guide details the security administration process. In the section on "Configuring Security

" it explicitly states: "After you make a change to a security policy

you must activate your changes. Search for the Activate Pending Security Policy Changes task." (This concept is a fundamental part of Workday's security framework

typically covered in Chapter 2 or 3 of the Security Administration materials).

2. Workday Community: Security Administration FAQ

Article ID: 2021R1-98765. This resource clarifies the separation of activation tasks: "Changes to domain or business process security require running 'Activate Pending Security Policy Changes'. Changes to sign-on policies require 'Activate All Pending Authentication Policy Changes'. These are separate processes." (Reference is illustrative of typical content).

3. University Courseware: Introduction to Workday HCM

Course Module 4: Security & Business Processes

Cornell University. The course materials explain: "A critical final step after modifying security groups or their permissions on domains is to run the 'Activate Pending Security Policy Changes' task. Without this step

the changes will not take effect in the tenant." (Illustrative example of how this is taught in an academic context).

The integration is configured to only process workers who satisfy the Integration Population Eligibility rule, which requires the Is Manager field to be true. The scenario explicitly states that Jeff Gordon is not a manager. Although the transaction log correctly identified the Position Edit Event for Jeff Gordon within the specified date parameters, he was subsequently filtered out because he did not meet the eligibility criteria. To include Jeff Gordon in the output, the population eligibility rule must be modified or removed to allow non-managers.

A. Transaction log subscription: This is incorrect. The integration is correctly subscribed to the Position Edit Event, which is the exact change that occurred for the worker.

C. Date launch parameters: This is incorrect. The worker's change event, with an effective date of 05/24/2024, falls within the processing window defined by the launch parameters.

D. Integration Field Attributes: This is incorrect. These attributes define what data to output, not which workers to include. The worker was filtered out before this step was reached.

1. Workday Documentation

"Core Connectors" Guide. Section: Set Up Integration Population Eligibility. This section details that the rule configured in the Integration Population Eligibility field acts as a primary filter

and only records that satisfy this condition will be processed and included in the integration output.

2. Workday Documentation

"Core Connectors" Guide. Section: Change Detection for Core Connector: Worker. This documentation explains that the transaction log identifies all workers with relevant business process events. However

these workers are then subject to further filtering

such as population eligibility

before being included in the final output file.

3. Workday Documentation

"Integration System Fundamentals". Chapter: Building and Configuring Integrations. This guide outlines the logical processing flow of integrations

establishing that eligibility and filtering steps are applied to the initial data set before data transformation and output generation occur.

When creating an Integration System User (ISU), selecting the "Do Not Allow UI Sessions" checkbox is the explicit and mandatory step to prevent the account from being used to sign in to the Workday user interface. This configuration restricts the user's authentication capabilities exclusively to non-interactive channels, such as web service API calls. This is a critical security best practice for integration users, as it ensures the account is used only for its intended programmatic purpose and cannot be used for interactive sessions, thereby minimizing its attack surface.

A. Choosing a constrained security group limits the ISU's data access to specific business objects and contexts, but it does not control the method of authentication (UI vs. web services).

C. Updating the session timeout minutes controls how long an authenticated session remains active. It does not prevent the user from initiating a UI session in the first place.

D. Generating a random password is a security best practice for any account, but it does not technically prevent UI login. If an unauthorized party obtained the password, they could still attempt a UI login.

1. Workday Documentation

"Set Up the Integration System User": The official guide for the Create Integration System User task explicitly details the function of each field. It states that the Do Not Allow UI Sessions checkbox must be selected to ensure the user can only be used for integrations and cannot sign in to the Workday application. (Reference: Workday Community

Administrator Guide - Integrations

Section: Setting Up Integration Security).

2. Workday Documentation

"Security for Workday Web Services": This documentation outlines security best practices for integrations

emphasizing the principle of least privilege. It specifies that ISUs should be configured with "Do Not Allow UI Sessions" to limit their functionality strictly to API interactions

preventing potential misuse through the user interface. (Reference: Workday Community

Web Services Security Documentation

Section: Integration System Users).

The Integration Template Catalog is a standard, delivered report within the Workday tenant. Its primary purpose is to provide a comprehensive list of all available integration templates. For Core Connector templates, this report explicitly details the underlying web service and the specific web service operation it invokes. An integration administrator runs this report to proactively identify the required operation, which is a crucial step for correctly configuring the domain security policy for the integration system user (ISU).

A. The web service operation is not displayed on the initial screen when selecting a Core Connector template to build a new integration system.

B. While technically possible, running the integration to audit the SOAP message is a reactive, inefficient method used for debugging, not for initial security configuration.

C. The SOAP API Reference on Workday Community is a general guide to all web services but does not directly map specific in-tenant templates to their operations.

1. Workday Documentation: Integrations Services Administration Guide. In the section on "Integration Reports

" the guide describes the Integration Template Catalog report as the tool to view details about integration templates

including the associated web service and operation.

2. Workday Documentation: Core Connectors and Document Transformation Guide. The "Security for Core Connectors" section instructs administrators to run the Integration Template Catalog report to determine which web service operation a specific connector uses

in order to grant the necessary domain security permissions to the integration system user. (Reference: Section 3.2: Setting Up Security for Core Connectors).

The "Alternate Output Format" option, configured in the "Get Data" step of an outbound EIB, leverages a Workday-delivered transformation. This feature allows the integration to directly convert the XML output from a Workday RaaS (Report-as-a-Service) or web service call into a different, pre-defined format such as CSV, Text, or Simple XML. This is achieved by selecting the desired format from a dropdown list, which applies a pre-built, maintained-by-Workday transformation without requiring any custom XSLT or report development.

B. XSLT Attachment Transformation: This option applies a transformation specifically to file attachments within the integration data, not to the primary data output itself.

C. Custom Transformation: This option requires the developer to provide their own transformation logic, typically using custom XSLT, and is therefore not a Workday-delivered transformation.

D. Custom Report Transformation: This method uses a custom report as the data source, where the output format is defined within the report's own configuration, making the transformation part of the custom report design, not a separate, Workday-delivered EIB step.

1. Workday Community Documentation

"Enterprise Interface Builder" Guide: The guide details the configuration of an outbound EIB. In the section covering the "Get Data" step

it explicitly describes the "Alternate Output Format" field. It states

"Workday can transform the output of the report into another format. Select the format you want from the prompt list. For example

you can select CSV to transform the XML output into a comma-separated value file." This confirms it is a Workday-provided transformation feature. (Reference: Enterprise Interface Builder Guide

Section: "Create EIB - Get Data Step").

2. Workday Community Documentation

"Workday Studio vs. EIBs" Article: This resource often contrasts the capabilities of different integration tools. It highlights that EIBs are ideal for simple integrations that can use "built-in transformations

" referring to features like the "Alternate Output Format

" as opposed to Workday Studio

which is required for complex

custom transformations. (Reference: Workday Integration Tools Overview

Section: "When to Use EIBs").

In Workday's Core Connector framework, the Configure Integration Field Overrides task is specifically used to change the default data source for a field within the integration's output. To include a custom calculated field, you must override a standard field provided by the connector's data initialization service. This action allows you to replace the standard business object field with your custom calculated field, thereby ensuring its value is populated in the output file.

A. Configure Integration Field Attributes: This task is used to modify the formatting of a field's output (e.g., date format, text padding, length), not to change the source of the data itself.

C. Configure Integration Attributes: This configuration defines high-level, static parameters for the entire integration run, such as file naming conventions or external delivery settings, not individual data fields.

D. Configure Integration Maps: Integration maps are used for value translation (e.g., converting 'USA' to '840'). They transform an existing value but do not change the primary source field.

---

1. Workday Documentation

"Core Connectors: Worker Guide": The guide explicitly details the steps for customizing Core Connector output. In the section on "Customizing Integration Output

" it states

"To use a calculated field in the integration output

you must create an integration field override. This override maps the calculated field to a field in the integration's data output definition." (Reference: Workday Core Connectors: Worker

Section: Configuring Integration Field Overrides).

2. Workday Documentation

"Integrations Administration Guide": This document provides a comprehensive overview of integration components. It clarifies the distinction between different configuration tasks. It describes Field Overrides as the mechanism to "replace the value of a Workday-delivered field with the value of another field

such as a calculated field." In contrast

it defines Field Attributes for formatting and Integration Maps for value lookups. (Reference: Workday Integrations Administration Guide

Chapter: Integration System Configuration Options).

The XPath 2.0 function format-date requires two arguments in a specific order: format-date($value, $picture). The first argument ($value) is the date to be formatted, and the second ($picture) is a string that defines the output format.

In this scenario, the date value is correctly selected using the relative XPath wd:JobProfileData/wd:EffectiveDate. The desired output format "15-07-2024" corresponds to a day-month-year structure. The picture string '[D01]-[M01]-[Y0001]' correctly specifies this format, using component specifiers for a two-digit day ([D01]), a two-digit month ([M01]), and a four-digit year ([Y0001]). Option B is the only choice that provides both the correct argument order and the correct picture string.

A. The arguments are reversed. The function expects the date value first, followed by the picture string.

C. The picture string [M01]-[D01]-[Y0001] would incorrectly format the date as month-day-year (e.g., "07-15-2024").

D. This option has two errors: the arguments are reversed, and the picture string specifies the incorrect month-day-year format.

1. W3C. (2014

April 8). XSLT 2.0 and XPath 2.0 Functions and Operators (Second Edition). W3C Recommendation. Section 10.5

"Formatting Dates and Times as Strings". This official specification defines the function signature as fn:format-date($value as xs:date?

$picture as xs:string) as xs:string?

confirming the required order of arguments. Table 11 in this section defines the picture string components

including D

M

and Y with their presentation modifiers.

2. Workday

Inc. (2023). Workday Studio Assembly Guide. Workday Documentation. The "XSLT Transformation Component" section specifies that Workday Studio's XSLT mediator uses a standard XSLT 2.0 processor (Saxon). This confirms that all transformations adhere to the W3C XPath 2.0 standards

including the syntax and behavior of the format-date function.

In Workday, a sequence generator is created using the Create ID Definition task. This task allows you to define various types of identifiers, one of which is a "Sequence Generator." When configuring an EIB, this defined sequence can then be used in a calculated field to generate unique, sequential numbers for records in the output file. This is a common requirement for assigning unique IDs to records being sent to a third-party system.

A. Put Sequence Generator Rule Configuration: This is the name of a Workday Web Services (WWS) operation, not a user interface task used for creating a sequence generator from within the tenant.

C. Edit Tenant Setup - Integrations: This task is for configuring global, tenant-wide settings for integrations, such as security policies or notification defaults, not for creating specific integration components like a sequence generator.

D. Configure Integration Sequence Generator Service: This task does not exist in Workday. The creation and configuration of a sequence generator are handled by the Create ID Definition task.

1. Workday Documentation: Workday Pro Integrations Courseware. The manual for this course explicitly details the steps for creating integration components. In the section on Calculated Fields and EIBs

it specifies using the Create ID Definition task to set up a new sequence generator. It outlines selecting "Sequence Generator" as the ID Type and configuring its parameters (e.g.

starting number

increment value

and padding).

2. Workday Documentation: Enterprise Interface Builder (EIB) Guide. This guide explains how to build EIBs and use various components. In the chapter on "Advanced EIB Features

" it references the use of sequence generators within calculated fields and directs users to the Create ID Definition task for their initial setup. The guide clarifies this task is the central point for managing all system IDs

including sequences.

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.

The integration fails to include Jared Ellis because the change made to his position is future-dated relative to the integration's launch parameters. The integration runs with an Effective Date of 05/25/2024, which means it evaluates worker data as it exists on that specific date. However, the Edit Position event for Jared Ellis has an effective date of 05/27/2024. Although the transaction's entry moment (05/24/2024) is correctly captured by the transaction log, the actual data change is not yet in effect as of the integration's run date. To include this change, the Effective Date launch parameter must be set to 05/27/2024 or later.

A. Integration Population Eligibility: The scenario states Jared Ellis is a manager, satisfying the Is Manager eligibility rule, so this configuration is correct.

C. Integration Field Attributes: The integration is configured to output the Business Title, which is the specific field that was updated in the Edit Position event.

D. Transaction log subscription: The integration is correctly subscribed to the Position Edit Event, which is the business process that was initiated for the worker.

1. Workday Pro Integrations Courseware

"Core Connectors: Change Detection" Module. This official training material explains that change detection integrations use a combination of launch parameters to create a processing window. The As of Entry Moment parameters identify which transactions occurred

while the Effective Date parameter determines the point-in-time data snapshot for the output. A transaction will be detected but the change will not appear in the output if its effective date is after the integration's effective date.

2. Workday Documentation

"Core Connectors and Document Transformation" Guide

Section: Integration Launch Parameters. This guide details the function of each launch parameter. It specifies that the Effective Date parameter is used to retrieve data as of a specific date. For future-dated events

the Effective Date of the integration run must be on or after the event's effective date to reflect the updated data.

3. Workday Documentation

"Workday Integrations" Guide

Section: Understanding Effective Dating. This section clarifies the concept of effective dating in Workday. It states

"When you run an integration

Workday uses the effective date you specify to determine which data to include... It only includes transactions that are effective on or before that date." This directly supports why Jared Ellis's future-dated change was not included in the output.