Instant Access Workday.Workday-Pro-Integrations.v2026-06-16.q85 Actual Practice Test Engine for Free (Page 11)

Question 46

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 Jared Ellis who is assigned to the manager role for the IT Help Desk department. You perform an Edit Position on Jared and update the Job Profile of the position to a new value. Jared Ellis' 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 Jared Ellis does not show up in your output.
What configuration element would have to be modified for the integration to include Jared Ellis in the output?

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

Correct Answer: C

The scenario describes a Core Connector: Worker integration configured to output specific fields (Position Title and Business Title) for workers who meet the Integration Population Eligibility criteria (Is Manager = true) and where the Transaction Log service is subscribed to the "Position Edit Event." The integration is launched with specific date parameters, and a test edit is made to Jared Ellis' position, who is a manager.
However, despite the edit being completed with an effective date of 05/24/2024 and an entry moment of 05/24
/2024 07:58:53 AM, Jared does not appear in the output. Let's analyze why and determine the correct configuration element to modify.
In Workday integrations, the Core Connector: Worker uses change detection mechanisms to identify and process updates based on the Transaction Log and date launch parameters. The Transaction Log service captures events such as the "Position Edit Event" and records them with an Effective Date (when the change takes effect) and an Entry Moment (when the change was entered into the system). The integration's date launch parameters define the time window for which changes are retrieved:
* As of Entry Moment: 05/25/2024 12:00:00 AM - This specifies the latest point in time for when changes were entered into Workday.
* Effective Date: 05/25/2024 - This defines the date for which the changes are effective.
* Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM - This indicates the starting point for entry moments from the last successful run.
* Last Successful Effective Date: 05/23/2024 - This indicates the starting point for effective dates from the last successful run.
For an incremental run (like this one, since "Last Successful" parameters are provided), Workday processes changes where the Entry Moment falls between the Last Successful As of Entry Moment (05/23/2024 12:00:
00 AM) and the As of Entry Moment (05/25/2024 12:00:00 AM), and where the Effective Date falls between the Last Successful Effective Date (05/23/2024) and the Effective Date (05/25/2024).
Now, let's evaluate Jared Ellis' edit:
* Entry Moment: 05/24/2024 07:58:53 AM - This falls within the range of 05/23/2024 12:00:00 AM to 05
/25/2024 12:00:00 AM.
* Effective Date: 05/24/2024 - This falls within the range of 05/23/2024 to 05/25/2024.
At first glance, Jared's edit seems to fit the date parameter window. However, the issue lies in the time component of the date launch parameters. Workday interprets these parameters with precision down to the second. The As of Entry Moment is set to 05/25/2024 12:00:00 AM (midnight), which is the very start of May
25, 2024. Jared's Entry Moment of 05/24/2024 07:58:53 AM is correctly within the range from 05/23/2024
12:00:00 AM to 05/25/2024 12:00:00 AM. However, the Transaction Log subscription to "Position Edit Event" relies on the change being fully processed and available in the log by the time the integration runs.
The integration might have run at a point where the effective date window or the subscription logic did not correctly capture the event due to a mismatch in how the Effective Date is evaluated against the Last Successful Effective Date. Specifically, if the integration only processes changes with an Effective Date strictly after the Last Successful Effective Date (05/23/2024) up to the Effective Date (05/25/2024), and the logic excludes changes effective exactly on 05/24/2024 due to a boundary condition or a timing issue in the transaction log, Jared's change might not be picked up.
To resolve this, modifying the Date launch parameters is necessary. Adjusting the As of Entry Moment to a later time (e.g., 05/25/2024 11:59:59 PM) or ensuring the Effective Date range explicitly includes all changes effective on or after 05/23/2024 through 05/25/2024 would ensure Jared's edit is captured. This adjustment aligns the time window to include all relevant transactions logged before the integration run.
Let's evaluate the other options:
* A. Integration Population Eligibility: This is set to "Is Manager = true," and Jared is a manager. This filter is working correctly and does not need modification.
* B. Integration Field Attributes: These are configured to output Position Title and Business Title, and the edit was to the Job Profile (part of Position Data). The fields are appropriately configured, so this is not the issue.
* D. Transaction Log Subscription: The subscription is set to "Position Edit Event," which matches Jared' s edit. The subscription type is correct, so no change is needed here.
Thus, the issue stems from the date launch parameters not fully encompassing the timing of Jared's edit in the Transaction Log, making C. Date launch parameters the correct answer.
Workday Pro Integrations Study Guide References
* Workday Integrations Study Guide: Core Connector: Worker - Section on "Change Detection Using Transaction Log" explains how Transaction Log subscriptions filter events based on date parameters.
* Workday Integrations Study Guide: Launch Parameters - Details the role of "As of Entry Moment" and
"Effective Date" in defining the scope of incremental runs.
* Workday Integrations Study Guide: Incremental Processing - Describes how "Last Successful" parameters establish the baseline for detecting changes in subsequent runs.

Question 47

You have been asked to refine a report which outputs one row per worker and is being used in an integration that sends worker data to one of your third-party systems. The integration should only send workers who have been hired in the last 30 days. Where in the custom report definition can you specify a condition that would include only workers who have been hired in the last 30 days?

A.Subfilter
B.Output
C.Columns
D.Filter

Correct Answer: D

In Workday, when refining a custom report to include specific conditions such as limiting the output to workers hired in the last 30 days, the appropriate place to specify this condition is within theFiltertab of the custom report definition. The Filter tab allows you to define criteria that determine which instances of the primary business object (in this case, "Worker") are included in the report output. This is critical for integrations, as the filtered data ensures that only relevant records are sent to the third-party system.
The requirement here is to restrict the report to workers hired within the last 30 days. In Workday reporting, this can be achieved by adding a filter condition on the "Hire Date" field of the Worker business object.
Specifically, you would configure the filter to compare the "Hire Date" against a dynamic date range, such as
"Current Date minus 30 days" to "Current Date." This ensures the report dynamically adjusts to include only workers hired in the last 30 days each time it runs, which aligns with the needs of an integration sending real- time data to a third-party system.
Here's why the other options are incorrect:
* A. Subfilter: Subfilters in Workday are used to further refine data within a related business object or a subset of data already filtered by the primary filter. They are not the primary mechanism for applying a condition to the main dataset (e.g., all workers). For this scenario, asubfilter would be unnecessary since the condition applies directly to the Worker business object, not a related object.
* B. Output: The Output section of a custom report definition controls how the report is displayed or delivered (e.g., file format, scheduling), not the data selection criteria. It does not allow for specifying conditions like hire date ranges.
* C. Columns: The Columns tab defines which fields are displayed in the report output (e.g., Worker ID, Name, Hire Date). While you can add the "Hire Date" field here for visibility, it does not control which workers are included in the report-that is the role of the Filter tab.
To implement this in practice:
* In the custom report definition, go to theFiltertab.
* Add a new filter condition.
* Select the "Hire Date" field from the Worker business object.
* Set the operator to "in the range" and define the range as "Current Date - 30 days" to "Current Date" (using dynamic date functions available in Workday).
* Save and test the report to ensure it returns only workers hired within the last 30 days.
This filtered report can then be enabled as a web service (via the Advanced tab) or used in an Enterprise Interface Builder (EIB) or Workday Studio integration to send the data to the third-party system, meeting the integration requirement.
References from Workday Pro Integrations Study Guide:
* Workday Report Writer Fundamentals: Section on "Creating and Managing Filters" explains how filters are used to limit report data based on specific conditions, such as date ranges.
* Integration System Fundamentals: Discusses how custom reports serve as data sources for integrations and the importance of filters in defining the dataset.
* Core Connectors & Document Transformation: Highlights the use of filtered custom reports in outbound integrations to third-party systems.

Question 48

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.

Correct Answer: B

This question concerns a Full File test of a Core Connector: Worker integration where address fields (Address Line, Municipality, Region, Postal Code) are missing from the output, despite being configured in Configure Integration Field Attributes. Additionally, the Worker Personal Data Section is marked as Include in Output.
This issue commonly stems from a missed Enablement of the Address Data subfolder, which acts as a container for the address-related fields. Even if individual fields are selected, they will not appear in the output if their parent subfolder is not enabled.
From the Workday Pro Integrations documentation:
"Each subfolder in the integration field hierarchy, such as Address Data under Worker Personal Data, must be explicitly enabled. If the subfolder itself is not enabled, the fields within it, even if marked as Required or Included, will not be rendered in the output." To resolve this:
Navigate to Configure Integration Field Attributes
Expand the Worker Personal Data > Address Data subfolder
Enable the subfolder
Then reselect the required address fields
Incorrect Options Explained:
A . Mark each address field as RequiredMarking fields as Required is only effective if the parent subfolder is enabled. Without enabling the subfolder, fields remain excluded.
C . Enable the Worker Personal Data Section Fields integration serviceThis pertains to service execution, not field visibility. The issue lies in field hierarchy and inclusion, not the service configuration.
D . Enable All Services in Configure Integration ServicesThis enables all integration services but does not impact field inclusion or subfolder visibility within field attribute configuration.
Reference:
Workday Pro: Integrations - Field Attributes Configuration and Subfolder Enablement Workday Community: Integration Field Attributes - Common Issues with Address Data Core Connector Deployment Guide - Field Selection and Troubleshooting

Question 49

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. The vendor receiving the file requires marital status values to be sent using a list of codes that they have provided instead of the text values that Workday uses internally and if a text value in Workday does not align with the vendors list of codes the integration should report "OTHER".
What configuration is required to output the list of codes required from by the vendor instead of Workday's values in this integration?

A.Configure Integration Maps with a blank Default
B.Configure Integration Attributes with a blank Default
C.Configure Integration Maps with "OTHER" as a Default
D.Configure Integration Attributes with "OTHER" as a Default

Correct Answer: C

The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data. The vendor requires marital status values to be transformed from Workday's internal text values (e.g., "Married," "Single") to a specific list of codes (e.g., "M," "S"), and any Workday value not matching the vendor's list should output "OTHER." Let's analyze the configuration:
Requirement:Transform the "Marital Status" field values into vendor-specific codes, with a fallback to "OTHER" for unmapped values. This is a field-level transformation, common in Core Connectors when aligning Workday data with external system requirements.
Integration Maps:In Core Connectors, Integration Maps are the primary tool for transforming field values. You create a map that defines source values (Workday's marital status text) and target values (vendor's codes). The "Default" setting in an integration map specifies what value to output if a Workday value isn't explicitly mapped. Here, setting the default to "OTHER" ensures that any marital status not in the vendor's list (e.g., a new Workday value like "Civil Union" not recognized by the vendor) is output as "OTHER." Option Analysis:
A . Configure Integration Maps with a blank Default: Incorrect. A blank default would leave the field empty or pass the original Workday value for unmapped cases, not "OTHER," failing the requirement.
B . Configure Integration Attributes with a blank Default: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery method), not field value transformations. They don't support mapping or defaults for specific fields like marital status.
C . Configure Integration Maps with "OTHER" as a Default: Correct. This uses Integration Maps to map Workday values to vendor codes and sets "OTHER" as the default for unmapped values, meeting the requirement fully.
D . Configure Integration Attributes with "OTHER" as a Default: Incorrect. Integration Attributes don't handle field-level transformations or defaults for data values, making this option inapplicable.
Implementation:
Edit the Core Connector: Worker integration.
Use the related action Configure Integration Maps.
Create a map for the "Marital Status" field (e.g., "Married" → "M," "Single" → "S").
Set the Default Value to "OTHER" in the map configuration.
Test the output to ensure mapped values use vendor codes and unmapped values return "OTHER." Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on "Configuring Integration Maps" explains mapping field values and using defaults for unmapped cases.
Integration System Fundamentals: Highlights how Core Connectors transform data to meet vendor specifications.

Question 50

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 a value on the output file which contains the average number of jobs a candidate applied to. This value is not delivered by Workday so you have identified that you will need to build a calculated field to generate this value.
What steps do you follow to output the calculated field?

A.Configure a custom field override service to output the calculation.
B.Configure integration attributes to output the calculation.
C.Configure integration field attributes to output the calculation.
D.Configure integration field overrides to output the calculation.

Correct Answer: D

The scenario involves a Core Connector: Candidate Outbound integration requiring a calculated field for the average number of jobs a candidate applied to, which isn't a delivered Workday field. The task is to output this calculated field in the integration file. Core Connectors in Workday use predefined templates but allow customization through various configuration options. Let's evaluate the steps:
Context:
Core Connector: Candidate Outbound uses the Data Initialization Service (DIS) to extract candidate data.
A calculated field must be created (e.g., averaging the "Number of Job Applications" field across a candidate's records).
This value needs to be included in the output file sent to the vendor.
Integration Field Overrides:In Core Connectors, calculated fields are typically incorporated into the output by defining integration field overrides. This feature allows you to map a calculated field to a specific field in the connector's output structure, overriding the default delivered value (or adding a new field). The calculated field is built separately (e.g., in Report Writer or Calculated Fields) and then referenced in the integration configuration.
Option Analysis:
A . Configure a custom field override service to output the calculation: Incorrect. There's no "custom field override service" in Workday Core Connectors. This might confuse with integration field overrides, but it's not a distinct service.
B . Configure integration attributes to output the calculation: Incorrect. Integration attributes define metadata or settings for the integration (e.g., file name, delivery method), not specific field mappings for output data.
C . Configure integration field attributes to output the calculation: Incorrect. "Integration field attributes" isn't a precise Workday term for this purpose; it may confuse with field-level settings, but field overrides are the correct mechanism.
D . Configure integration field overrides to output the calculation: Correct. This is the standard method in Core Connectors to include calculated fields in the output file by overriding or adding to the delivered field structure.
Implementation:
Create a calculated field (e.g., "Average Job Applications") using functions like Arithmetic Calculation to average job application counts.
In the Core Connector configuration, navigate to the Integration Field Overrides section.
Define a new field or override an existing one, mapping it to the calculated field.
Test the integration to ensure the calculated value appears in the output file.
Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on "Configuring Integration Field Overrides" explains mapping calculated fields to output files.
Integration System Fundamentals: Details how Core Connectors extend delivered functionality with custom calculations.

Question 46

Question 47

Question 48

Question 49

Question 50

Download PDF File