Workday Pro Integrations Certification Workday-Pro-Integrations Exam Practice Test

Page: 1 / 14
Total 77 questions
Question 1

What is a key function and primary benefit of using a Document Transformation Connector within the integration capabilities of Workday?



Answer : C

The Document Transformation Connector is used in Workday to process and reformat XML outputs --- often from Core Connector or EIB integrations --- into custom formats like CSV, JSON, or flattened XML.

''The primary role of the Document Transformation Connector is to apply XSLT-based formatting, data reorganization, and validation to the output of Workday integrations before delivery to downstream systems.''

This is especially useful when third-party vendors require a specific format not natively supported by the integration system.

Why the other options are incorrect:

A . Managing business processes is not a DT Connector's function.

B . Calculations are not the main purpose --- that's more for Calculated Fields or Studio.

D . While security is essential, secure connections are managed through Workday's integration system and transport configuration, not the DT connector.


Question 2

A vendor needs an EIB that uses a custom report to output a list of new hires and the date they are eligible for benefits. You have been asked to create a calculated field that adds each worker's hire date + 85 days and displays the result in YYYY-MM-DD format.

Which calculated field functions do you need to accomplish this?



Answer : D

You are asked to create a calculated field that:

Takes the Hire Date

Adds 85 days

Formats it as YYYY-MM-DD

To accomplish this in Workday, you need the following calculated field functions:

Numeric Constant define 85

Increment or Decrement Date add 85 days to the Hire Date

Format Date convert the resulting date to YYYY-MM-DD

Why other options are incorrect:

A . Date Constant would define a fixed date, not a dynamic calculation.

B . Date Difference is for subtraction between two dates.

C . Date Constant is still incorrect for offsetting a variable date.


Question 3

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?



Answer : A

The Test Security Related Action shows Available by User = No when the security group running the integration lacks View permissions to the fields used in the override logic.

From Workday documentation:

Field Overrides require the ISSG to have View access to the domain policies securing each field referenced in the override, otherwise Workday blocks the field from execution.

Therefore, the appropriate fix is to:

* Identify the domains that secure the calculated fields and overridden fields

* Grant the ISSG View access in those domain security policies

* Activate pending changes

Options B and C incorrectly focus only on web service operations.

Option D incorrectly suggests Modify access --- but View is the required minimum.


Question 4

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.

While testing, the output contains no records, and the Messages tab shows exception logs stating you don't have access to the Exempt field. You note this is the same field being used for Population Eligibility in the integration.

What must you configure to resolve this security issue?



Answer : D

The Exempt field is being used in Population Eligibility, and eligibility fields must be readable by the ISSG. If the domain security policy for a field denies View access, Workday cannot evaluate the eligibility and returns no data.

From Workday security governance:

''For integrations using Population Eligibility, the ISSG must have View permission on all fields referenced in eligibility rules.''

If View is missing, the eligibility rule cannot execute No workers are considered eligible Output contains zero records Error logged for denied field access.

Therefore, the solution is:

* Grant the ISSG View access to the domain that secures the Population Eligibility field

Modify access (A/C) is not needed --- eligibility only needs read-access.


Question 5

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



Answer : C

This question is about the correct order of Workday security assignment for integrations. Workday clearly specifies the security structure:

''You assign the ISU to the Integration System Security Group (ISSG).

Then you assign the ISSG to the domain security policies.''

This is because domain security policies apply to security groups, not directly to ISUs.

Correct Relationship Order:

Create ISU

Create/assign ISU to ISSG

Assign ISSG to the domain security policies (Get/Put/View)

That aligns exactly to option C.


Question 6

You need to filter a custom report to only show workers that have been terminated after a user-prompted date.

How do you combine conditions in the filter to meet this requirement?



Answer : D

The requirement is to filter a custom report to show only workers terminated after a user-prompted date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions can be combined using AND/OR logic to refine the dataset. Let's analyze the requirement and options:

Key Conditions:

Workers must be terminated, so the 'Worker Status' field must equal 'Terminated.'

The termination must occur after a user-specified date, so the 'Termination Date' must be greater than the prompted value.

Both conditions must be true for a worker to appear in the report, requiring an AND combination.

Option Analysis:

A . Worker Status is equal to the value 'Terminated' OR Termination Date is greater than a value retrieved from a prompt: Incorrect. Using OR means the report would include workers who are terminated (regardless of date) OR workers with a termination date after the prompt (even if not terminated), which doesn't meet the strict requirement of terminated workers after a specific date.

B . Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a value retrieved from a prompt: Incorrect. Worker Status shouldn't be a prompted value (it's fixed as 'Terminated'), and 'less than' would show terminations before the date, not after.

C . Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a value retrieved from a prompt: Incorrect. Worker Status shouldn't be prompted, and 'equal to' limits the filter to exact matches, not 'after' the date. OR logic also broadens the scope incorrectly.

D . Worker Status is equal to the value 'Terminated' AND Termination Date is greater than a value retrieved from a prompt: Correct. This ensures workers are terminated (fixed value) AND their termination date is after the user-entered date, precisely meeting the requirement.

Implementation:

In the custom report's Filter tab, add two conditions:

Field: Worker Status, Operator: equals, Value: 'Terminated'.

Field: Termination Date, Operator: greater than, Value: Prompt for Date (configured as a report prompt).

Set the logical operator between conditions to AND.

Test with a sample date to verify only terminated workers after that date appear.

Reference from Workday Pro Integrations Study Guide:

Workday Report Writer Fundamentals: Section on 'Creating and Managing Filters' details combining conditions with AND/OR logic and using prompts.

Integration System Fundamentals: Notes how filtered reports support integration data sources with dynamic user inputs.


Question 7

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?



Answer : C

This question pertains to a Core Connector: Worker integration configured with Data Initialization Service (DIS) enabled and scheduled to run once daily. The integration is set to extract only those worker records where changes have occurred in compensation, home address, or business title since the last execution --- leveraging Workday's change detection to avoid full file extracts.

In testing, when a home address update occurs, the integration fails to capture this change in its output. However, all other components --- such as worker eligibility, integration field attributes, and Full-Diff parameters --- are confirmed to be correctly configured.

The critical element missing here is the event subscription. In Workday, for a Core Connector to recognize changes via Full-Diff or delta mode, it must be properly subscribed to the specific change events that should trigger inclusion in the output. This is done using the Edit Subscriptions configuration.

From the Workday Pro: Integrations documentation:

''The Edit Subscriptions task defines the set of data changes (e.g., job changes, address changes, compensation updates) that the integration system listens for. If an event type is not included in the subscription, changes related to that event will not be picked up in either delta or Full-Diff mode, regardless of other configuration.''

In this scenario, although the integration is configured for Full-Diff, failure to include 'Home Address Change' in the subscription list prevents the system from recognizing the update, thereby omitting it from the output file.

Incorrect Options Explained:

A . Configure Integration Field OverridesThis option is used to override or map integration field values but has no impact on whether a change is detected or included in the output.

B . Maintain Integration AttributesWhile this configuration manages connector behavior and filtering rules, it does not control the detection of specific event changes.

D . Configure Integration Transaction LogThis is used for tracking and audit purposes but does not affect change detection or output inclusion.


Workday Pro: Integrations Curriculum -- Core Connector: Worker

Workday Community Article: Configuring Core Connectors and Change Detection with Edit Subscriptions

GPC_PECI_DeploymentGuide_CloudPay_2.9.pdf -- Section: Integration Configuration & Subscriptions

Page:    1 / 14   
Total 77 questions