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

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 ensure that only employees, and not contingent workers, are output by this integration?

The following XML code was generated using Core Connector: Location.
You need to produce a fixed length file to enforce a 25-character length for the locc:Location_Name, padded with * on the left if shorter, and issue a warning if it exceeds this length.
What combination of XSLT attributes and values do you use?

What is the limitation when assigning ISUs to integration systems?

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 want to receive the Institution Name, Institution Type, and Degrees.
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.
What configuration step should you modify to ensure the integration only includes Active workers in the Clinical Staff job family?

Refer to the following scenario to answer the question below.
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.
You need to review and correct the security configuration so that all overrides are secured appropriately and data is successfully extracted, resolving any security issues that arise when testing runs of the integration.
While troubleshooting issues with the connector, you are looking for a report which allows you to see how a given item is secured.
What report or task would assist you in this?

What is the purpose of granting an ISU modify access to the Integration Event domain via an ISSG?

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] = 2022, [yy] = 22
Month: [MMM] = Sep, [MM] = 09, [M] = 9
Day: [d] = 21, [E] = Wed, [D] = 265
Hours: [k] = 13, [h] = 1
Minutes: [m] = 35
Seconds: [s] = 59
Milliseconds: [S] = 123
What configuration would generate a filename matching the day month year format for "File-14-1-2024.xml"?