Practice Free Workday Pro Integrations Exam Online Questions

Question #1

You need the integration file to generate the date format in the form of "31/07/2025" format

• The first segment is day of the month represented by two characters.

• The second segment is month of the year represented by two characters.

• The last segment is made up of four characters representing the year

How will you use Document Transformation (OT) to do the transformation using XTT?

A)

A . Option A
B . Option B
C . Option C
D . Option D

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

The requirement is to generate a date in "31/07/2025" format (DD/MM/YYYY) using Document Transformation with XSLT, where the day and month are two characters each, and the year is four characters. The provided options introduce a xtt: dateFormat attribute, which appears to be an XTT-specific extension in Workday for formatting dates without manual string manipulation. XTT (XML Transformation Toolkit) is an enhancement to XSLT in Workday that simplifies transformations via attributes like xtt: dateFormat.

Analysis of Options

Assuming the source date (e.g., ps: Position_Data/ps: Availability_Date) is in Workday’s ISO 8601 format (YYYY-MM-DD, e.g., "2025-07-31"), we need XSLT that applies the "dd/MM/yyyy" format .

Let’s evaluate each option:

Option A:

xml

<xsl: template match<Record xtt: dateFormat<Availability_Date>

<xsl: value-of select</Availability_Date>

</Record>

</xsl: template>

Analysis:

The xtt: dateFormat<xsl: value-of selectThis aligns with Workday’s XTT functionality, where attributes can override default date rendering.

Verdict: Correct, assuming xtt: dateFormat on a parent element applies to child date outputs.

Option A (Second Part):

xml

<Record>

<Availability_Date xtt: dateFormat<xsl: value-of select</Availability_Date>

</Record>

Analysis:

Here, xtt: dateFormatThis is a valid alternative and likely the intended "best practice" for targeting a specific field.

Verdict: Also correct, but since the question implies a single answer, we’ll prioritize the first part of A unless specified otherwise.

Option B:

xml

<xsl: template match</xsl: template>

Analysis:

Incomplete (lines 2-7 are blank). No date transformation logic is present.

Verdict: Incorrect due to lack of implementation.

Option C:

xml

<xsl: template match<Record>

<Availability_Date>

<xsl: value-of xtt: dateFormat</Availability_Date>

</Record>

</xsl: template>

Analysis:

Places xtt: dateFormatThis is a strong contender as it directly ties the formatting to the output instruction.

Verdict: Correct and precise, competing with A.

Option C (Second Part):

xml

<Record>

<Availability_Date>

<xsl: value-of select</Availability_Date>

</Record>

Analysis:

No xtt: dateFormat, so it outputs the date in its raw form (e.g., "2025-07-31").

Verdict: Incorrect for the requirement.

Option D:

xml

<xsl: template xtt: dateFormat Analysis:

Applies xtt: dateFormat to the <xsl: template> element, but no content is transformed (lines 2-7 are blank).

Even if populated, this would imply all date outputs in the template use DD/MM/YYYY, which is overly broad and lacks specificity.

Verdict: Incorrect due to incomplete logic and poor scoping.

Decision

A vs .

C: Both A (first part) and C (first part) are technically correct:

A: <Record xtt: dateFormatC: <xsl: value-of xtt: dateFormat Explanation:

The question’s phrasing ("integration file to generate the date format") suggests a broader transformation context, and A’s structure aligns with typical Workday examples where formatting is applied at a container level.

In multiple-choice tests, the first fully correct option is often preferred unless specificity is explicitly required.

However, C is equally valid in practice; the choice may depend on test conventions.

Final XSLT in Context

Using Option A:

xml

<xsl: template match<Record xtt: dateFormat<Availability_Date>

<xsl: value-of select</Availability_Date>

</Record>

</xsl: template>

Input: <ps: Availability_Date>2025-07-31</ps: Availability_Date>

Output: <Record><Availability_Date>31/07/2025</Availability_Date></Record>

Notes

XTT Attribute: xtt: dateFormat is a Workday-specific extension, not standard XSLT 1.0. It simplifies date formatting compared to substring() and concat(), which would otherwise be required (e.g., <xsl: value-of selectNamespace: ps: likely represents a Position schema in Workday; adjust to wd: if the actual namespace differs.

Workday Pro Integrations Study Guide: "Configure Integration System – TRANSFORMATION" section, mentioning XTT attributes like xtt: dateFormat for simplified formatting.

Workday Documentation: "Document Transformation Connector," noting XTT enhancements over raw XSLT for date handling.

Workday Community: Examples of xtt: dateFormat

Question #2

A calculated field used as a field override in a Connector is not appearing in the output .

Assuming the field has a value, what could cause this to occur?

A . Access not provided to calculated field data source.
B . Access not provided to all fields in the calculated field.
C . Access not provided to Connector calculated field web service.
D . Access not provided to all instances of calculated field.

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

This question addresses a troubleshooting scenario in Workday Pro Integrations, where a calculated field used as a field override in a Connector does not appear in the output, despite having a value. Let’s analyze the potential causes and evaluate each option.

Understanding Calculated Fields and Connectors in Workday

Calculated Fields: In Workday, calculated fields are custom fields created using Workday’s expression language to derive values based on other fields, conditions, or functions. They are often used in reports, integrations, and business processes to transform or aggregate data. Calculated fields can reference other fields (data sources) and require appropriate security permissions to access those underlying fields.

Field Override in Connectors: In a Core Connector or other integration system, a field override allows you to replace or supplement a default field with a custom value, such as a calculated field. This is configured in the integration’s mapping or transformation steps, ensuring the output includes the desired data. However, for the calculated field to appear in the output, it must be accessible, have a valid value, and be properly configured in the integration.

Issue: Calculated Field Not Appearing in Output: If the calculated field has a value but doesn’t appear in the Connector’s output, the issue likely relates to security, configuration, or access restrictions. The question assumes the field has a value, so we focus on permissions or setup errors rather than data issues.

Evaluating Each Option

Let’s assess each option based on Workday’s integration and security model:

Option A: Access not provided to calculated field data source.

Analysis: This is partially related but incorrect as the primary cause. Calculated fields often rely on underlying data sources (e.g., worker data, organization data) to compute their values. If access to the data source is restricted, the calculated field might not compute correctly or appear in the output. However, the question specifies the field has a value, implying the data source is accessible. The more specific issue is likely access to the individual fields within the calculated field’s expression, not just the broader data source.

Why It Doesn’t Fit: While data source access is important, it’s too general here. The calculated field’s value exists, suggesting the data source is accessible, but the problem lies in finer-grained permissions for the fields used in the calculation.

Option B: Access not provided to all fields in the calculated field.

Analysis: This is correct. Calculated fields in Workday are expressions that reference one or more fields (e.g., Worker_ID + Position_Title). For the calculated field to be used in a Connector’s output, the ISU (via its ISSG) must have access to all fields referenced in the calculation. If any field lacks "Get" or "View" permission in the relevant domain (e.g., Worker Data), the calculated field won’t appear in the output, even if it has a value. This is a common security issue in integrations, as ISSGs must be configured with domain access for every field involved.

Why It Fits: Workday’s security model requires granular permissions .

For example, if a calculated field combines Worker_Name and Hire_Date, the ISU needs access to both fields’ domains. If Hire_Date is restricted, the calculated field fails to output, even with a value. This aligns with the scenario and is a frequent troubleshooting point in Workday Pro Integrations.

Option C: Access not provided to Connector calculated field web service.

Analysis: This is incorrect. There isn’t a specific "Connector calculated field web service" in Workday. Calculated fields are part of the integration’s configuration, not a separate web service. The web service operation used by the Connector (e.g., Get_Workers) must have permissions, but this relates to the overall integration, not the calculated field specifically. The issue here is field-level access, not a web service restriction.

Why It Doesn’t Fit: This option misinterprets Workday’s architecture. Calculated fields are configured within the integration, not as standalone web services, making this irrelevant to the problem.

Option D: Access not provided to all instances of calculated field.

Analysis: This is incorrect. The concept of "instances" typically applies to data records (e.g., all worker records), not calculated fields themselves. Calculated fields are expressions, not data instances, so there’s no need for "instance-level" access. The issue is about field-level permissions within the calculated field’s expression, not instances of the field. This option misunderstands Workday’s security model for calculated fields.

Why It Doesn’t Fit: Calculated fields don’t have "instances" requiring separate access; they depend on the fields they reference, making this option inaccurate.

Final Verification

The correct answer is Option B, as the calculated field’s absence in the output is likely due to the ISU lacking access to all fields referenced in the calculated field’s expression .

For example, if the calculated field in a Core Connector: Worker Data combines Worker_ID and Department_Name, the ISSG must have "Get" access to both the Worker Data and Organization Data domains. If Department_Name is restricted, the calculated field won’t output, even with a value. This is a common security configuration issue in Workday integrations, addressed by reviewing and adjusting ISSG domain permissions.

This aligns with Workday’s security model, where granular permissions are required for all data elements, as seen in Questions 26 and 28. The assumption that the field has a value rules out data or configuration errors, focusing on security as the cause.

Supporting Documentation

The reasoning is based on:

Workday Community documentation on calculated fields, security domains, and integration mappings.

Tutorials on configuring Connectors and troubleshooting, such as Workday Advanced Studio Tutorial, highlighting field access issues.

Integration security guides from partners (e.g., NetIQ, Microsoft Learn, Reco.ai) detailing ISSG permissions for fields in calculated expressions.

Community discussions on Reddit and Workday forums on calculated field troubleshooting (r/workday on Reddit).

Question #3

How many integration systems can an ISU be assigned to concurrently?

A . One
B . Three
C . Five
D . Unlimited

Reveal Solution Hide Solution

Question #4

Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled that runs once daily. The integration must extract only active worker records with changes to compensation, home address, or business title since the last run 24 hours ago, using Workday’s change detection to avoid full extracts.

During testing, an employee’s home address is updated, but the integration does not detect the change in the output. The employee is eligible, the connector uses the correct integration field attributes, and the launch parameters are properly configured for a Full-Diff extract.

What configuration task must you modify from the integration system to ensure the expected change is included in the output?

A . Configure Integration Field Overrides
B . Maintain Integration Attributes
C . Edit Subscriptions
D . Configure Integration Transaction Log

Reveal Solution Hide Solution

Question #5

You need to create a report that includes data from multiple business objects. For a supervisory organization specified at run time, the report must output one row per worker, their active benefit plans, and the names and ages of all related dependents. The Worker business object contains the Employee, Benefit Plans, and Dependents fields. The Dependent business object contains the employee’s dependent’s Name and Age fields.

How would you select the primary business object (PBO) and related business objects (RBO) for the report?

A . PBO: Dependent, RBO: Worker
B . PBO: Worker, RBO: Dependent
C . PBO: Dependent, no RBOs
D . PBO: Worker; no RBOs

Reveal Solution Hide Solution

Question #6

What is the relationship between the Integration System User (ISU), Integration System Security Group (ISSG), and domain security policies?

A . Assign domain security policies to the ISSG, and then assign the ISSG to the ISU.
B . Assign domain security policies to the ISU, and then assign the ISU to the ISSG.
C . Assign the ISU to the ISSG, and then assign the ISSG to domain security policies.
D . Assign the ISSG to the ISU, and then assign the ISU to domain security policies.

Reveal Solution Hide Solution

Question #7

Refer to the following scenario to answer the question below.

An external system needs a file containing data for recent worker job changes. They would like to receive a file routinely at 5:00 PM Eastern Standard Time, every 48 hours. The file should show job changes since the last integration run.

What is the recurrence type of the integration schedule?

A . Recurs every 2 day(s)
B . Custom Recurrence
C . Recurs every 48 hours
D . Dependent Recurrence

Reveal Solution Hide Solution

Question #8

Refer to the following scenario to answer the question below.

You have configured a Core Connector: Worker integration, which utilizes the following basic configuration:

• Integration field attributes are configured to output the Position Title and Business Title fields from the Position Data section.

• Integration Population Eligibility uses the field Is Manager which returns true if the worker holds a manager role.

• Transaction Log service has been configured to Subscribe to specific Transaction Types: Position Edit Event.

You launch your integration with the following date launch parameters (Date format of

MM/DD/YYYY):

• As of Entry Moment: 05/25/2024 12:00:00 AM

• Effective Date: 05/25/2024

• Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM

• Last Successful Effective Date: 05/23/2024

To test your integration, you made a change to a worker named Jeff Gordon who is not assigned to the manager role. You perform an Edit Position on Jeff Gordon and update their business title to a new value. Jeff Gordon’s worker history shows the Edit Position Event as being successfully completed with an effective date of 05/24/2024 and an Entry Moment of 05/24/2024 07:58:53 AM however Jeff Gordon does not show up in your output.

What configuration element would have to be modified for the integration to include Jeff Gordon in the output?

A . Transaction log subscription
B . Integration Population Eligibility
C . Date launch parameters
D . Integration Field Attributes

Reveal Solution Hide Solution

Question #9

What is the limitation when assigning ISUs to integration systems?

A . An ISU can be assigned to five integration systems.
B . An ISU can be assigned to an unlimited number of integration systems.
C . An ISU can be assigned to only one integration system.
D . An ISU can only be assigned to an ISSG and not an integration system.

Reveal Solution Hide Solution

Correct Answer: C
C

Explanation:

This question examines the limitations on assigning Integration System Users (ISUs) to integration systems in Workday Pro Integrations. Let’s analyze the relationship and evaluate each option to determine the correct answer.

Understanding ISUs and Integration Systems in Workday

Integration System User (ISU): An ISU is a specialized user account in Workday designed for integrations, functioning as a service account to authenticate and execute integration processes. ISUs are created using the "Create Integration System User" task and are typically configured with settings like disabling UI sessions and setting long session timeouts (e.g., 0 minutes) to prevent expiration during automated processes. ISUs are not human users but are instead programmatic accounts used for API calls, EIBs, Core Connectors, or other integration mechanisms.

Integration Systems: In Workday, an "integration system" refers to the configuration or setup of an integration, such as an External Integration Business (EIB), Core Connector, or custom integration via web services. Integration systems are defined to handle data exchange between Workday and external systems, and they require authentication, often via an ISU, to execute tasks like data retrieval, transformation, or posting.

Assigning ISUs to Integration Systems: ISUs are used to authenticate and authorize integration systems to interact with Workday. When configuring an integration system, you assign an ISU to provide the credentials needed for the integration to run. This assignment ensures that the integration can access Workday data and functionalities based on the security permissions granted to the ISU via its associated Integration System Security Group (ISSG).

Limitation on Assignment: Workday’s security model imposes restrictions to maintain control and auditability. Specifically, an ISU is designed to be tied to a single integration system to ensure clear accountability, prevent conflicts, and simplify security management. This limitation prevents an ISU from being reused across multiple unrelated integration systems, reducing the risk of unintended access or data leakage.

Evaluating Each Option

Let’s assess each option based on Workday’s integration and security practices:

Option A: An ISU can be assigned to five integration systems.

Analysis: This is incorrect. Workday does not impose a specific numerical limit like "five" for ISU assignments to integration systems. Instead, the limitation is more restrictive: an ISU is typically assigned to only one integration system to ensure focused security and accountability. Allowing an ISU to serve multiple systems could lead to confusion, overlapping permissions, or security risks, which Workday’s design avoids.

Why It Doesn’t Fit: There’s no documentation or standard practice in Workday Pro Integrations suggesting a limit of five integration systems per ISU. This option is arbitrary and inconsistent with Workday’s security model.

Option B: An ISU can be assigned to an unlimited number of integration systems.

Analysis: This is incorrect. Workday’s security best practices do not allow an ISU to be assigned to an unlimited number of integration systems. Allowing this would create security vulnerabilities, as an ISU’s permissions (via its ISSG) could be applied across multiple unrelated systems, potentially leading to unauthorized access or data conflicts. Workday enforces a one-to-one or tightly controlled relationship to maintain auditability and security.

Why It Doesn’t Fit: The principle of least privilege and clear accountability in Workday integrations requires limiting an ISU’s scope, not allowing unlimited assignments.

Option C: An ISU can be assigned to only one integration system.

Analysis: This is correct. In Workday, an ISU is typically assigned to a single integration system to ensure that its credentials and permissions are tightly scoped. This aligns with Workday’s security model, where ISUs are created for specific integration purposes (e.g., an EIB, Core Connector, or web service integration). When configuring an integration system, you specify the ISU in the integration setup (e.g., under "Integration System Attributes" or "Authentication" settings), and it is not reused across multiple systems to prevent conflicts or unintended access. This limitation ensures traceability and security, as the ISU’s actions can be audited within the context of that single integration.

Why It Fits: Workday documentation and best practices, including training materials and community forums, emphasize that ISUs are dedicated to specific integrations .

For example, when creating an EIB or Core Connector, you assign an ISU, and it is not shared across other integrations unless explicitly reconfigured, which is rare and discouraged for security reasons.

Option D: An ISU can only be assigned to an ISSG and not an integration system.

Analysis: This is incorrect. While ISUs are indeed assigned to ISSGs to inherit security permissions (as established in Question 26), they are also assigned to integration systems to provide authentication and authorization for executing integration tasks. The ISU’s role includes both: it belongs to an ISSG for permissions and is linked to an integration system for execution. Saying it can only be assigned to an ISSG and not an integration system misrepresents Workday’s design, as ISUs are explicitly configured in integration systems (e.g., EIB, Core Connector) to run processes.

Why It Doesn’t Fit: ISUs are integral to integration systems, providing credentials for API calls or data exchange. Excluding assignment to integration systems contradicts Workday’s integration framework.

Final Verification

The correct answer is Option C, as Workday limits an ISU to a single integration system to ensure security, accountability, and clarity in integration operations. This aligns with the principle of least privilege, where ISUs are scoped narrowly to avoid overexposure .

For example, when setting up a Core Connector: Job Postings (as in Question 25), you assign an ISU specifically for that integration, not multiple ones, unless reconfiguring for a different purpose, which is atypical.

Supporting Documentation

The reasoning is based on Workday Pro Integrations security practices, including:

Workday Community documentation on creating and managing ISUs and integration systems.

Tutorials on configuring EIBs, Core Connectors, and web services, which show assigning ISUs to specific integrations (e.g., Workday Advanced Studio Tutorial).

Integration security overviews from implementation partners (e.g., NetIQ, Microsoft Learn, Reco.ai) emphasizing one ISU per integration for security.

Community discussions on Reddit and Workday forums reinforcing that ISUs are tied to single integrations for auditability (r/workday on Reddit).

Question #10

You are configuring a Core Connector integration that will send data to an external vendor. The vendor requires that the integration output file includes a unique Batch ID in its filename.

This ID must follow the format VNDR_YEARMONTH_seq.xml, where YEAR is the four-digit year, MONTH is the two-digit month, and seq is a five-digit sequence number that must reset to 00001 at the beginning of each new month.

Which settings must you configure on the integration Filename Sequence Generator to produce this Batch ID filename?

A . Sequence ID Format Restart Frequency
B . Sequence ID Format Restart Frequency
C . Sequence ID Format Restart Frequency
D . Sequence ID Format Restart Frequency

Reveal Solution Hide Solution

1 2 3 4

Exams