Workday Workday-Pro-Integrations : Workday Pro Integrations Certification Exam

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"?

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

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?

• A. Dependent recurrence
• B. Recurs every weekday
• C. Recurs every 12 hours
• D. Recurs every 1 day(s)

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 Integration Permissions table that has Put access enabled.
• B. Assign the ISSG to a row within the Report/Task Permissions table that has Modify 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 Get access enabled.

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

What attribute(s) can go into the xsl:stylesheet element?

• A. XSLT Version & Namespaces
• B. XML Version & Namespaces
• C. XSLT Version & Encoding
• D. Namespaces & Encoding