Question 1

After configuring domain security policies, what task must you run to ensure the most recent changes go into effect?

Accepted Answer

C

Explanation: 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.

Question 2

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?

Accepted Answer

B

Explanation: 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.

Question 3

When creating an ISU, what should you do to ensure the user only authenticates via web services?

Accepted Answer

B

Explanation: 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.

Question 4

You are configuring integration security for a Core Connector integration system. How do you find the web service operation used by the connector template?

Accepted Answer

D

Explanation: 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).

Question 5

What option for an outbound EIB uses a Workday-delivered transformation to output a format other than Workday XML?

Accepted Answer

A

Explanation: 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.

Question 6

Refer to the following scenario to answer the question below.
You have been asked to build an integration using the Core Connector: Worker template and should
leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no
change detection) for employees only and will include personal data.
What configuration is required to output the value of a calculated field which you created for
inclusion in this integration?

Accepted Answer

B

Explanation: 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.

Question 7

Refer to the following XML to answer the question below.
Refer to the following XML to answer the question below.
Workday-Pro-Integrations practice exam questions

Workday-Pro-Integrations practice exam questions

You are an integration developer and need to write XSLT to transform the output of an EIB which is
making a request to the Get Job Profiles web service operation. The root template of your XSLT
matches on the element. This root template then applies
templates against . XPath contains a number of delivered functions such as format-
date. The format-date function uses the following syntax: format-date ($value as xs: date? $picture
as xs:string). Within the template which matches on , what XPath syntax would you
use to output the value of the element formatted with the day-month-year
format of "15-07-2024"?

Accepted Answer

B

Explanation: 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.

Question 8

What task is needed to build a sequence generator for an EIB integration?

Accepted Answer

B

Explanation: 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.

Question 9

Refer to the following scenario to answer the question below.
You need to configure a Core Connector: Candidate Outbound integration for your vendor. The
connector requires the data initialization service (DIS).
The vendor needs the file to only include candidates that undergo a candidate assessment event in
Workday.
How do you accomplish this?

Accepted Answer

A

Explanation: 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.

Question 10

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?

Accepted Answer

B

Explanation: 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.

Question 11

An external system needs a file containing data for recent compensation changes. They would like to
receive a file routinely at 5 PM eastern standard time, excluding weekends. The file should show
compensation changes since the last integration run.
What is the recurrence type of the integration schedule?

Accepted Answer

B

Explanation: The requirement is to run an integration at a specific time (5 PM EST) on a recurring basis, but only on business days (Monday through Friday). The "Recurs every weekday" schedule type is the specific Workday configuration designed for this exact scenario. It establishes a daily recurrence pattern that automatically excludes Saturdays and Sundays, aligning perfectly with the external system's needs. The time of day (5 PM) is set within this schedule's configuration.

Question 12

You have a population of workers who have put multiple names in their Legal Name - First Name
Workday delivered field. Your third-party vendor only accepts one-word first names. For workers that
have included a middle name, the first and middle names are separated by a single space. You have
been asked to implement the following logic:
* Extract the value before the single space from the Legal Name - First Name Workday delivered
field.
* Count the number of characters in the extracted value.
* Identify if the number of characters is greater than.
* If the count of characters is greater than 0, use the extracted value. Otherwise, use the Legal Name
- First Name Workday delivered field.
What functions are needed to achieve the end goal?

Accepted Answer

D

Explanation: This solution requires a sequence of functions to meet the specified logic. First, Substring Text is used to extract the portion of the string before the space (the first name). Second, Text Length calculates the number of characters in this extracted value. Third, a True/False Condition is used to evaluate if the character count is greater than zero. Finally, Evaluate Expression acts as an if-then-else statement, using the output of the True/False Condition to decide whether to return the newly extracted first name or the original, unmodified field value. This combination directly addresses all requirements of the problem.

Question 13

What is the workflow to upload an XSLT file for a brand new Document Transformation system?

Accepted Answer

B

Explanation: The correct workflow for implementing a new Document Transformation in Workday begins with defining the transformation logic itself. This is accomplished by using the Create XSLT Attachment Transformation task, where the XSLT file is uploaded and the transformation is named. Once this transformation object exists within the tenant, an integration service, such as the Integration Attachment Service, must be configured to utilize it. This configuration step links the service to the specific transformation, enabling it to process documents according to the defined XSLT logic. This sequence ensures the transformation is available before any service attempts to reference it.

Question 14

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?

Accepted Answer

C

Explanation: The Core Connector: Worker integration evaluates changes based on two key parameters: the transaction's entry date and its effective date, relative to the integration's run parameters. For Run #1 (Effective Date: May 15), the salary change is not included. Although the transaction was entered on May 13 (within the entry date window), its effective date of May 22 is in the future. The integration reports the data as it exists on May 15, at which time the new salary is not yet active. For Run #2 (Effective Date: May 31), the salary change is included. The integration's change detection logic compares the worker's data as of May 31 against the data from the last successful run (effective May 15). Since the salary increase became effective on May 22, a change is detected, and the new data is included in the output.

Question 15

A vendor needs to create a Date Difference calculated field. However, the two dates needed for that
calculation are on two separate business objects.
What additional calculated field do you need to create that Date Difference calculated field?

Accepted Answer

A

Explanation: The 'Date Difference' calculated field requires both date fields to exist on the same business object. When the dates are on two separate, but related, business objects, you must first bring one date into the context of the other. The Lookup Related Value (LRV) calculated field is designed for this exact purpose. It retrieves the value of a field from a related business object, making it available for use in calculations on the primary business object. Therefore, an LRV field must be created first to "pull" the remote date, which can then be used in the 'Date Difference' calculation.

Free Workday Workday-Pro-Integrations Actual Exam Questions