매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Workday Pro Integrations Certification Exam 온라인 연습
최종 업데이트 시간: 2026년06월29일
당신은 온라인 연습 문제를 통해 Workday Workday Pro Integrations 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Workday Pro Integrations 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 77개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Comprehensive and Detailed 100 to 150 words of Explanation From Workday Pro Integration topics: The one-time payment change is excluded because its business process status is still In Progress. Core connector change detection processes completed and eligible transactions based on the configured transaction subscriptions and launch parameters. Even though the transaction appears in worker history and its dates may fall within the relevant launch window, Workday should not send incomplete business process results to an external system. An in-progress compensation event has not reached a final approved or successfully completed state, so the connector does not treat it as ready for outbound delivery. The due date is not the controlling factor, and there is no evidence that the change was rescinded. The effective date is also not the main issue here. The exclusion is caused by the transaction’s incomplete status.
정답:
Explanation:
Predicated templates use XPath predicates inside square brackets to match only specific source nodes. The template must match the wd: Report_Entry node and then apply a predicate against the child value wd: Country_Code.
Option A correctly creates three separate template matches: one for USA records, one for GBR records, and one fallback template for records where the country code is neither USA nor GBR. This is the cleanest XSLT pattern because each template processes a specific population of report entries.
Options B and D incorrectly place the predicate or comparison after navigating directly to wd: Country_Code, which does not properly match the full report entry node.
Option C combines USA and GBR in the first template and would not separate processing correctly.
정답:
Explanation:
The correct XSLT structure for conditional branching is xsl: choose, with one or more xsl: when conditions and an optional xsl: otherwise fallback. In this scenario, the transformation must test whether wd: Dependents_Group exists. If it exists, the code counts the number of dependent group nodes by using count (wd: Dependents_Group) and appends the word “Dependents.” If it does not exist, the fallback text must be output.
Option C is the only valid structure because xsl: otherwise is correctly nested inside xsl: choose and does not incorrectly include a test attribute.
Options A and B misuse xsl: otherwise, and option D incorrectly places xsl: if inside xsl: choose instead of using xsl: when.
정답:
Explanation:
The requirement combines CSV output formatting with a required-value check for date fields. For Workday transformation formatting classes, XTT is the correct attribute family. xtt: class defines reusable transformation formatting rules, xtt: name names the class, and xtt: dateFormat controls the rendered date pattern. The required US format is MM/dd/yyyy, and the EU format is dd.MM.yyyy. xtt: required
정답:
Explanation:
This is a validation requirement, not a fixed-width formatting requirement. The goal is to confirm that required XML elements are not empty and to raise custom error messages with a defined severity. Workday’s ETV attributes are used for this type of validation behavior. etv: required
정답:
Explanation:
This requirement is fixed-width formatting, so the Workday XTT attributes are the correct family of attributes. xtt: fixedLength defines the padding character. To pad on the left, the value must be right-aligned, so xtt: align
정답:
Explanation:
The required XSLT component is xsl: template. XSLT transformations are driven by templates, which define the transformation rules that apply to matched XML nodes. A template can match a source element or be called by name, and it contains the instructions that produce the transformed output. xsl: apply-template is not the correct element name; the correct XSLT instruction is xsl: apply-templates, and it is used to invoke template processing on selected nodes. xsl: call-template calls a named template but does not by itself define the rule being executed. xsl: output controls serialization settings such as output method or encoding. For valid transformation logic, the core executable rule container is xsl: template.
정답:
Explanation:
When troubleshooting Workday integration security, the key question is often which domain security policies secure a particular field, report, web service, or task. View Security for Securable Item is designed for that purpose. It allows the administrator to inspect how a specific securable item is protected and identify the security domains and permissions involved. Security Analysis for Security Groups focuses on a security group’s access, and Security Analysis for Workday Account focuses on what a user account can access. Maintain Permissions for Security Group is used to manage permissions, not to diagnose how a specific item is secured. Since the requirement is to investigate security for a given item, View Security for Securable Item is the correct diagnostic tool.
정답:
Explanation:
When an integration is moved to an Integration System User, ownership must support unattended execution. The integration system itself can be owned by the ISU, but if an integration schedule exists, that schedule also needs to be owned by the ISU or transferred appropriately. Otherwise, the automated run can fail or continue to depend on the original human owner’s security context. Integration Maps, Integration Attributes, and Integration Field Attributes are configuration components inside the integration; they do not independently control scheduled execution ownership. The schedule is the object responsible for recurring automated launches, so it must align with the service account that owns and runs the integration. This is a security and operational control for stable Workday integration execution.
정답:
Explanation:
A calculated field that already exists in the tenant is not automatically emitted in a Core Connector output. For this requirement, the connector must be extended so the custom value becomes available and is then placed into the outbound structure. Creating a Custom Field Override service makes the calculated License ID available for the connector output, and the integration field override then adds that calculated field into the file. Integration Maps are used to translate values, such as converting one code set to another; they do not add a new calculated field. Field Attributes mainly control delivered field inclusion and field behavior. Since the requirement is to add a custom calculated output value, the custom field override service plus field override configuration is the correct workflow.
정답:
Explanation:
For Core Connector: Worker, selecting fields in Integration Field Attributes is not always enough if the related integration service is not enabled. Worker qualification information, including education-related data, is controlled by the Worker Qualification Data Section Fields Service. If that service is not enabled, the connector does not extract the section’s data, even when individual field attributes appear to be selected or the section is marked for output. Enabling every service is excessive and not the controlled configuration choice. Marking fields as required affects validation or required output behavior, but it does not activate the underlying qualification service. The correct fix is to enable the specific service that supplies the worker qualification data to the connector output.
정답:
Explanation:
The schedule requirement is every 48 hours, which is handled as a daily recurrence pattern with an interval of two days. Workday scheduling separates the general run frequency from the more specific recurrence interval. The run frequency is therefore Daily Recurrence, while the recurrence detail would define the integration to recur every two days. Hourly Recurrence would be used when the integration runs at hourly intervals, not every two calendar days. Minute Recurrence is far too granular for this requirement. Custom Recurrence is unnecessary because the stated pattern can be handled by the standard daily recurrence configuration. Since the file must include changes since the last run, this schedule supports incremental processing while keeping the cadence predictable.
정답:
Explanation:
The requirement is to run the integration every 48 hours at a fixed time. In schedule configuration terms, 48 hours is equivalent to every two days. Therefore, the correct recurrence type is “Recurs every 2 day(s).” “Recurs every 48 hours” sounds mathematically equivalent, but it is not the schedule recurrence type shown for this configuration. Custom Recurrence would only be needed if the schedule pattern could not be represented by the standard recurrence options. Dependent Recurrence is used when an integration should run based on another process or dependency, which is not stated here. Since the file must include changes since the last run, the two-day recurrence controls how often incremental job changes are extracted.
정답:
Explanation:
Creating or associating a filename sequence generator is not enough by itself. The EIB must be configured so the File Name launch parameter determines its value at runtime from the sequence generator utility. The correct runtime field is Next Sequence for Integration File Utility. If the launch parameter is not set this way, Workday can still use a static or manually supplied filename, which means the configured sequence generator will not drive the final output filename. Typing the sequence generator name as a static value would not invoke the generator. The issue is also not simply a transformation problem or delivery endpoint problem. The key configuration gap is that the runtime filename value was not linked to the sequence generator output.
정답:
Explanation:
The schedule must run every weekday and exclude weekends. “Configure to recur every weekday” is the only option that directly matches Monday through Friday processing. Configuring the schedule to recur every one day would run seven days a week unless additional restrictions were added, so it does not meet the “not on weekends” requirement. Recurring every five days is also incorrect because it creates a rolling five-day interval, not a Monday-to-Friday pattern. Recurring every seven days would run weekly, not every weekday. The phrase “since the last integration run” indicates incremental change processing, but the question is specifically asking for run frequency. Therefore, the weekday recurrence is the correct scheduling configuration.