Practice Free Workday Pro Integrations Exam Online Questions – Page 2

Question #11

How do you initially upload the XSLT file to a Document Transformation integration system?

A . From the Related Action on the Document Transformation, select Configure Integration Attachment Service.
B . From the Related Action on the Document Transformation, select Configure Integration Attributes.
C . In the Global Workday Search bar, run the Edit Integration Attachment Service task.
D . In the Global Workday Search bar, run the Edit Integration Service Attachment task.

Question #12

Refer to the following scenario to answer the question below.

You are configuring a filename sequence generator for a connector. Below are common pattern tokens for timestamps ranging from the year to the millisecond.

Define the sequence format using a combination of string constants and pattern tokens to create a unique identifier. Note the example tokens include the square brackets.

For the next sequence number: [Seq] or [seq]

Assume date of September 21, 2022, 12:35:59:123 PM .

Some common tokens:

Year: [yyyy] Month: [MMM] Day: [d] Hours: [k] Minutes: [m] Seconds: [s] Milliseconds: [S]

What configuration would generate a filename matching the day month year format for “File-14-1-2024.xml”?

A . File-[d]-[MM]-[yyyy].xml
B . File-[d]-[mmm]-[yyyy].xml
C . File-[d]-[M]-[yyyy].xml
D . File-[d]-[m]-[yyyy].xml

Reveal Solution Hide Solution

Question #13

You have successfully configured an ISU and an ISSG with the correct security policies and have assigned them to an EIB.

What task do you need to run before you can launch the EIB?

A . Activate Pending Security Policy Changes
B . View Security for Securable Item
C . Assign the ISSG to only one security policy
D . Maintain Integration Security Policies

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

In Workday, after configuring an Integration System User (ISU) and an Integration System Security Group (ISSG) with the appropriate security policies and assigning them to an Enterprise Interface Builder (EIB) integration, there is a critical step required before the EIB can be launched successfully. This step ensures that all security configurations and permissions assigned to the ISSG take effect in the Workday tenant. Let’s analyze the question and evaluate each option systematically to determine the correct task, ensuring the answer aligns with Workday’s documented processes and the Workday Pro Integrations Study Guide.

Context of the Scenario

You’ve completed the following:

Created an ISU and configured it (e.g., with "Do Not Allow UI Sessions" checked for web service-only access).

Set up an ISSG and assigned the ISU to it.

Defined the necessary security policies (e.g., domain security policies with "Get" and/or "Put" access) for the ISSG to support the EIB’s operations.

Assigned the ISU and ISSG to the EIB integration system.

The question now is what must be done before launching the EIB to ensure it functions as intended. In Workday, changes to security policies―such as adding permissions to an ISSG―do not take effect immediately. They remain in a "pending" state until activated, which is a key aspect of Workday’s security administration process.

Evaluation of Options

Option A: Activate Pending Security Policy Changes In Workday, whenever you modify security policies (e.g., granting domain permissions like "Integration Build" or "Custom Report Creation" to an ISSG), these changes are staged as "pending." To apply them to the tenant and make them active, you must run the "Activate Pending Security Policy Changes" task. This task reviews all pending security updates, allows you to add a comment for audit purposes, and, upon confirmation, activates the changes. Without this step, the ISSG will not have the effective permissions required for the EIB to access data or execute its operations, potentially causing the launch to fail due to insufficient authorization. This aligns directly with the scenario, as security policies have been configured and assigned, but not yet activated.

Option B: View Security for Securable Item The "View Security for Securable Item" report is a diagnostic tool in Workday that allows you to inspect the security configuration for a specific object (e.g., a web service operation, report, or task). It shows which security groups have access and what permissions (e.g., "Get," "Put," "View," "Modify") are granted. While this is useful for verifying that the ISSG has the correct policies assigned, it is a passive report―it does not modify or activate anything. Running this task would not enable the EIB to launch, as it doesn’t affect the pending security changes. Thus, it’s not the required step before launching the EIB.

Option C: Assign the ISSG to only one security policy This option suggests limiting the ISSG to a single security policy, but this is neither a standard Workday requirement nor a task that exists as a standalone action. ISSGs can and often do have multiple security policies assigned (e.g., permissions for various domains like "Integration Build," "Custom Report Access," etc.), depending on the integration’s needs. Moreover, the question states that the ISSG has already been configured with the "correct security policies" and assigned to the EIB, implying this step is complete. Restricting the ISSG to one policy after the fact would require editing permissions again, triggering more pending changes, and still necessitate activation―making this option illogical and incorrect.

Option D: Maintain Integration Security Policies There is no specific task in Workday called "Maintain Integration Security Policies." This option seems to be a misnomer or a conflation of other tasks, such as "Maintain Domain Permissions for Security Group" (used to assign permissions to an ISSG) or broader security maintenance activities. However, the question indicates that the security policies are already correctly configured and assigned. If this option intended to imply further configuration, it would still result in pending changes requiring activation via Option A. As a standalone action, it does not represent a valid or necessary task to enable the EIB launch.

Why Option A is Correct

The "Activate Pending Security Policy Changes" task is a mandatory step in Workday’s security workflow after modifying security policies, such as those assigned to an ISSG for an EIB. Workday’s security model uses a pending changes queue to ensure that updates are reviewed and deliberately applied, maintaining control and auditability .

Without activating these changes:

The ISSG will lack the effective permissions needed for the EIB to access required domains or perform its operations (e.g., retrieving data from a custom report or delivering a file).

The EIB launch could fail with errors like "Insufficient Privileges" or "Access Denied."

Running this task ensures that the security configuration is live, allowing the ISU (via the ISSG) to authenticate and execute the EIB successfully. This is a standard practice in Workday integration setup, as emphasized in the Workday Pro Integrations curriculum.

Practical Steps to Perform Option A

Log into the Workday tenant with a security administrator role.

Search for and select the "Activate Pending Security Policy Changes" task.

Review the list of pending changes (e.g., new permissions added to the ISSG).

Enter a comment (e.g., "Activating security for EIB launch C ISSG permissions").

Check the "Confirm" box and click "OK" to activate the changes.

Once completed, the security policies are live, and the EIB can be launched.

Verification with Workday Documentation

The Workday Pro Integrations Study Guide and related training materials confirm that activating pending security policy changes is a prerequisite after configuring security for integrations. This step ensures that all permissions are in effect, enabling the ISU and ISSG to support the EIB’s functionality. Community resources and implementation guides also consistently highlight this task as the final step before launching integrations that rely on updated security settings.

Workday Pro Integrations Study Guide Reference

Section: Integration Security Configuration C Explains the process of assigning security policies to ISSGs and the need to activate changes to operationalize them.

Section: Enterprise Interface Builder (EIB) C Notes that security updates for EIBs must be activated before launching to ensure proper access.

Section: Security Administration C Details the "Activate Pending Security Policy Changes" task as the mechanism to apply pending security modifications across the tenant.

Question #14

Refer to the following scenario to answer the question below.

You are configuring a Core Connector: Worker integration to send data to a new external compliance and certification tracking vendor. You have begun to configure the connector with the Data Initialization Service (DIS) enabled .

Your goal is to extract worker qualification data, but the vendor has three specific requirements:

The file must only include Active workers who are in the “Clinical Staff” Job Family.

The vendor has specified that for each worker’s Education data, they only want to receive the Institution Name, Institution Type and Degree.

The vendor requires a custom “License ID” that must combine the Certification Name and Issuing State, for example, “RN-CA”. A Calculated Field that provides this custom “License ID” already exists in the tenant.

During testing, using a Full File run, the output file is missing all education-related information, even though you believe you have initially configured field attributes such as Institution Name, Institution Type and Degree in the Configure Integration Field Attributes step. Additionally, you confirmed that the Worker Qualification Data Section is marked as Include in Output.

What should you do to resolve this issue?

A . Enable the Education subfolder in Configure Integration Field Attributes and then reselect the Institution Name, Institution Type, and Degree fields.
B . Within the Configure Integration Services task, select the Enable All Services checkbox.
C . Enable the Worker Qualification Data Section Fields Service within the Configure Integration Services step.
D . Mark each education field in the Education subfolder as Required in Configure Integration Field Attributes.

Reveal Solution Hide Solution

Question #15

Refer to the following XML to answer the question below.

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 <wd: Get_Job_Profiles_Response> element. This root template then applies templates against <wd: Job_Profile>. 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 <wd: Job_Profile>, what XPath syntax would you use to output the value of the <wd: Effective_Date> element formatted with the day-month-year format of "15-07-2024"?

A . format-date(‘[D01]-[M01]-[Y0001]’, wd: Job_Profile_Data/wd: Effective_Date)
B . format-date (wd: Job_Profile_Data/wd: Effective_Date, ‘[D01]-[M01]-[Y0001]’)
C . format-date (wd: Job_Profile_Data/wd: Effective_Date, ‘[M01]-[D01]-[Y0001]’)
D . format-date(‘[M01]-[D01]-[Y0001]’, wd: Job_Profile_Data/wd: Effective_Date)

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

As an integration developer working with Workday, you are tasked with transforming the output of an Enterprise Interface Builder (EIB) that calls the Get_Job_Profiles web service operation. The XML provided shows the response from this operation, and you need to write XSLT to format the <wd: Effective_Date> element within the <wd: Job_Profile_Data> section. Specifically, you need to output the date "2024-05-15" (as seen in the XML) in the format "15-07-2024" (day-month-year). The root template of your XSLT matches on <wd: Get_Job_Profiles_Response> and applies templates to <wd: Job_Profile>. You are using the format-date XPath function, which follows the syntax: format-date($value as xs: date?, $picture as xs: string). Let’s analyze the XML, the requirement, and each option to determine the correct XPath syntax.

Understanding the XML and Requirement

The provided XML snippet shows a response from the Get_Job_Profiles web service operation in Workday, formatted in SOAP XML with the Workday namespace

(xmlns: wdThe root element is <wd: Get_Job_Profiles_Response>.

It contains <wd: Response_Data>, which includes <wd: Job_Profile> elements.

Within <wd: Job_Profile>, there is <wd: Job_Profile_Data>, which contains <wd: Effective_Date> with the value 2024-05-15.

You need to transform this date into the format "15-07-2024" (DD-MM-YYYY), where:

"15" is the day (D01 for two digits).

"07" is the month (M01 for two digits, noting the XML shows May, but the question specifies July for the output format―likely a hypothetical or test case adjustment).

"2024" is the year (Y0001 for four digits).

The format-date function in XPath 2.0 (used by Workday) formats a date value according to a picture string .

The syntax is:

First parameter: The date value (e.g., wd: Job_Profile_Data/wd: Effective_Date), which must be an xs: date or convertible to one.

Second parameter: The picture string (e.g., ‘[D01]-[M01]-[Y0001]’), specifying the format using patterns like:

[D01] for two-digit day (01-31).

[M01] for two-digit month (01-12).

[Y0001] for four-digit year (e.g., 2024).

The question specifies that the root template matches <wd: Get_Job_Profiles_Response> and applies templates to <wd: Job_Profile>, so the XPath must navigate to <wd: Job_Profile_Data/wd: Effective_Date> within that context.

Analysis of Options

Let’s evaluate each option based on the format-date syntax, the XML structure, and the required output format "15-07-2024":

Option A: format-date(‘[D01]-[M01]-[Y0001]’, wd: Job_Profile_Data/wd: Effective_Date)

This option places the picture string (‘[D01]-[M01]-[Y0001]’) as the first parameter and the date value (wd: Job_Profile_Data/wd: Effective_Date) as the second. However, the format-date function requires the date value as the first parameter and the picture string as the second, per the syntax format-date($value, $picture). Reversing the parameters is incorrect and will result in an error or unexpected output, as format-date expects an xs: date? first. Thus, this option is invalid.

Option B: format-date (wd: Job_Profile_Data/wd: Effective_Date, ‘[D01]-[M01]-[Y0001]’)

This option correctly follows the format-date syntax:

First parameter: wd: Job_Profile_Data/wd: Effective_Date, which points to the <wd: Effective_Date> element in the XML (e.g., 2024-05-15). This is an xs: date value, as Workday web services typically return dates in ISO format (YYYY-MM-DD), which format-date can process.

Second parameter: ‘[D01]-[M01]-[Y0001]’, which specifies the output format:

[D01] outputs the day as two digits (e.g., "15").

[M01] outputs the month as two digits (e.g., "05" for May, but the question requests "07" for July― assuming a test case adjustment or hypothetical transformation).

[Y0001] outputs the year as four digits (e.g., "2024").

The XPath wd: Job_Profile_Data/wd: Effective_Date is correctly nested under the <wd: Job_Profile> context, as the template matches on <wd: Job_Profile>. This would transform "2024-05-15" into "15-05-2024" (or "15-07-2024" if the month is adjusted in the logic), matching the required day-month-year format. This option is valid and correct.

Option C: format-date (wd: Job_Profile_Data/wd: Effective_Date, ‘[M01]-[D01]-[Y0001]’)

This option also follows the correct format-date syntax, with the date value first and the picture string second .

However, the picture string ‘[M01]-[D01]-[Y0001]’ specifies a month-day-year format:

[M01] outputs the month first (e.g., "05" for May).

[D01] outputs the day second (e.g., "15").

[Y0001] outputs the year last (e.g., "2024").

This would transform "2024-05-15" into "05-15-2024," which does not match the required "15-07-2024" (day-month-year) format. Thus, this option is incorrect for the specified output.

Option D: format-date(‘[M01]-[D01]-[Y0001]’, wd: Job_Profile_Data/wd: Effective_Date)

Similar to Option A, this option reverses the parameters, placing the picture string (‘[M01]-[D01]-[Y0001]’) first and the date value (wd: Job_Profile_Data/wd: Effective_Date) second. As explained earlier, format-date requires the date value as the first parameter, so this syntax is incorrect and will not work as intended. This option is invalid.

Why Option B is Correct

Option B correctly uses the format-date function with the proper syntax:

It places the date value (wd: Job_Profile_Data/wd: Effective_Date) as the first parameter, referencing the <wd: Effective_Date> element in the XML.

It uses the picture string ‘[D01]-[M01]-[Y0001]’ as the second parameter, which formats the date as "DD-MM-YYYY" (e.g., "15-05-2024" for the XML’s "2024-05-15," or "15-07-2024" as specified, assuming a month adjustment in the transformation logic).

The XPath is appropriate for the context, as the template matches <wd: Job_Profile>, and <wd: Job_Profile_Data/wd: Effective_Date> is a valid path within it.

The question’s mention of "15-07-2024" suggests either a hypothetical adjustment (e.g., the EIB or XSLT logic modifies the month to July) or a test case variation. Since the XML shows "2024-05-15," the format-date function would output "15-05-2024" with the given picture string, but the principle of formatting day-month-year remains correct. Workday’s XSLT implementation supports such transformations, and the format-date function is well-documented for this purpose.

Practical Example in XSLT

Here’s how this might look in your XSLT:

<xsl: template match<xsl: value-of select</xsl: template>

This would process the <wd: Effective_Date> (e.g., "2024-05-15") and output "15-05-2024," aligning with the day-month-year format requested (adjusted for the hypothetical "07" if needed elsewhere in the logic).

Verification with Workday Documentation

The Workday Pro Integrations Study Guide and SOAP API Reference (available via Workday

Community) detail the use of XPath functions like format-date for transforming web service responses. The Get_Job_Profiles operation returns job profile data, including effective dates, in ISO format, and XSLT transformations are commonly used in EIBs to reformat data. The format-date function’s syntax and picture string patterns (e.g., [D01], [M01], [Y0001]) are standard in XPath 2.0, as implemented in Workday’s integration tools.

Workday Pro Integrations Study Guide Reference

Section: XSLT Transformations in EIBs C Describes using XSLT to transform web service responses, including date formatting with format-date.

Section: Workday Web Services C Details the Get_Job_Profiles operation and its XML output structure, including <wd: Effective_Date>.

Section: XPath Functions C Explains the syntax and usage of format-date($value, $picture), including picture string patterns like [D01], [M01], and [Y0001].

Workday Community SOAP API Reference C Provides examples of date formatting in XSLT for Workday web services.

Option B is the verified answer, as it correctly applies the format-date function to format the <wd: Effective_Date> in the required day-month-year format.

Question #16

Refer to the scenario. You are configuring a Core Connector: Worker integration to extract worker demographic and contact information. The integration uses the Data Initialization Service (DIS) and must include worker fields such as name, address, and a calculated field identifying workers eligible for a phone allowance.

During a Full File test run, the output file is missing all address-related information, even though the Address Line Data, Municipality, Region, and Postal Code fields were configured in the Configure Integration Field Attributes step. You also confirmed that the Worker Personal Data Section is marked as Include in Output.

What should you do to resolve this issue?

A . Mark each address field in the Address Data subfolder as Required in Configure Integration Field Attributes.
B . Enable the Address Data subfolder in Configure Integration Field Attributes and then reselect the address fields.
C . Enable the Worker Personal Data Section Fields integration service within the Configure Integration Services step.
D . Within the Configure Integration Services task, select the Enable All Services checkbox.

Reveal Solution Hide Solution

Question #17

What is the purpose of the <xsl: template> element?

A . Determine the output file type.
B . Grant access to the XSLT language.
C . Provide rules to apply to a specified node.
D . Generate an output file name.

Reveal Solution Hide Solution

Question #18

Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled. The integration must extract worker contact details and job information, including a calculated field override that determines phone allowance eligibility.

When testing, you run the Test Security Related Action from the Configure Integration Field Override step. Several field overrides display “No” in the Available by User column.

To ensure the ISSG has access to these field overrides and that “Yes” is displayed in the Test Security step, what configuration should you review?

A . Provide the ISSG View permissions to the domain security policies securing each overridden field.
B . Assign the ISSG to the domain security policies that govern the web service operations with Get access.
C . Grant View permissions to the ISSG for the domain security policies that secure the web service operations.
D . Identify the domain security policies securing the field overrides and grant Modify permissions.

Reveal Solution Hide Solution

Question #19

You are creating an outbound connector using the Core Connector: Job Postings template .

The vendor has provided the following specification for worker subtype values:

The vendor has also requested that any output file have the following format "CC_Job_Postings_dd-mm-yy_#.xml".

Where the dd is the current day at runtime, mm is the current month at runtime, yy is the last two digits of the current year at runtime, and # is the current value of the sequencer at runtime.

What configuration step(s) must you complete to meet the vender requirements?

A . • Enable the Sequence Generator Field Attribute
• Configure the Sequence Generator
• Configure the Worker Sub Type Integration Mapping leaving the default value blank
B . • Enable the Integration Mapping Field Attribute
• Configure the Worker Sub Type Integration Mapping leaving the default value blank
• Configure the Sequence Generator
C . • Enable the Integration Mapping Integration Service
• Configure the Worker Sub Type Integration Mapping and include a default value of "U"
• Configure the Sequence Generator
D . • Enable the Sequence Generator Integration Service
• Configure the Sequence Generator
• Configure the Worker Sub Type Integration Mapping and include a default value of "U"

Reveal Solution Hide Solution

Question #20

You are configuring an EIB that uses a custom report as its data source. When attempting to transfer ownership of the report to the Integration System User (ISU), the ISU does not appear as an option for new report owners. You confirm that the ISU already has the necessary access to the report data source and related fields.

Within the Custom Report Creation domain, which security configuration should you update to allow the ISU to appear as a valid report owner?

A . Assign the ISSG to a row within the Report/Task Permissions table that has Modify access enabled.
B . Assign the ISSG to a row within the Integration Permissions table that has Get access enabled.
C . Assign the ISSG to a row within the Report/Task Permissions table that has View access enabled.
D . Assign the ISSG to a row within the Integration Permissions table that has Put access enabled.

Reveal Solution Hide Solution

1 2 3 4

Exams