ちなみに、It-Passports Workday-Pro-Integrationsの一部をクラウドストレージからダウンロードできます：https://drive.google.com/open?id=1gW2Pw_9GF2bZuP17A31piM4_h5RnmIWC
It-Passportsは、すべての受験者にWorkday-Pro-Integrations試験の十分な知識を持つ専門家によってコンパイルされたWorkday-Pro-Integrationsテストトレントを提供し、Workday-Pro-Integrations学習教材のコンパイルに非常に専門的です。それだけでなく、テストトレントWorkday-Pro-Integrationsの最新情報を保持するために、チームは毎日更新を確認します。最新バージョンを入手したら、できるだけ早くメールボックスに送信します。試験に最適なWorkday-Pro-Integrations学習教材を提供するのに最適なプラットフォームである必要があります。
| Certification Vendor: | Workday |
|---|---|
| Exam Name: | Workday Pro Integrations Certification Exam |
| Exam Number: | Workday-Pro-Integrations |
| Available Languages: | English |
| Exam Duration: | 120 minutes |
| Related Certifications: | Workday Pro Certifications Workday Integrations Developer Path |
| Passing Score: | 80% |
| Real Exam Qty: | 77 (commonly reported; may vary by exam version) |
| Exam Price: | $99 (Workday Pro Exam registration, subject to event/region pricing) |
| Exam Format: | Multiple Choice, Single Select |
| Recommended Training: | Workday Integrations Training Path (Workday Education) |
| Exam Registration: | Workday Pro Certifications Registration Page |
| Sample Questions: | Workday Workday-Pro-Integrations Sample Questions |
| Exam Way: | Proctored, closed-book exam (onsite or online depending on Workday Pro exam event format) |
| Pre Condition: | Recommended prior experience with Workday fundamentals and integration concepts (EIB, calculated fields, and basic XML/XSLT understanding) |
| Official Syllabus URL: | https://www.workday.com/en-us/company/latest/events-webinars/devcon/workday-pro-certifications.html |
>> Workday-Pro-Integrations試験合格攻略 <<
Workday-Pro-Integrationsの科学技術の改善は、社会の将来の建設と進歩に計り知れない力を生み出します。 Workday-Pro-Integrations模擬試験は、緊急の課題に対処するための最適な選択および有用なツールとなります。 10年以上の努力により、当社のWorkday-Pro-Integrationsトレーニング資料は、業界で最も広く称賛され、待望の製品になりました。 Workday-Pro-Integrations模擬試験の計画と設計において、プロのエリートから完全な技術サポートを受けています。もうheしないでください。 Workday-Pro-Integrations学習エンジンの購入を後悔することはありません！
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 79
When creating an ISU, what should you do to ensure the user only authenticates via web services?
正解：B
解説：
When creating an Integration System User (ISU) in Workday, the goal is often to ensure that the user is restricted to performing tasks via web services (e.g., API calls or integrations) and cannot log into the Workday user interface (UI). This is a critical security measure to limit the ISU's access to only what is necessary for integration purposes, adhering to the principle of least privilege. Let's evaluate each option provided in the question to determine the correct approach based on Workday's functionality and best practices as outlined in official documentation and the Workday Pro Integrations program.
Option A: Choose a constrained security group.In Workday, security groups define the permissions and access levels for users, including ISUs. There are two types of Integration System Security Groups (ISSGs): constrained and unconstrained. A constrained ISSG limits access to specific organizations or data scopes, while an unconstrained ISSG provides broader access across the tenant. While choosing a constrained security group can enhance security by limiting the scope of data the ISU can access, it does not directly control whether the ISU authenticates via web services or the UI. The type of security group affects data access permissions, not the authentication method or UI access. Therefore, this option does not address the requirement of ensuring authentication only via web services.
Option B: Select the Do Not Allow UI Sessions checkbox.When creating an ISU in Workday, the "Create Integration System User" task presents an option labeled "Do Not Allow UI Sessions." Selecting this checkbox explicitly prevents the ISU from logging into the Workday UI using its credentials. This setting ensures that the ISU can only authenticate and operate through programmatic means, such as web service calls (e.g., SOAP or REST APIs), which is precisely the intent of the question. This is a standard security practice recommended by Workday to isolate integration activities from interactive user sessions, reducing the risk of misuse or unauthorized access through the UI. This option directly aligns with the requirement and is the correct answer.
Option C: Update the session timeout minutes.The "Session Timeout Minutes" field in the ISU creation task determines how long an ISU's session remains active before it expires. By default, this is set to 0, meaning the session does not expire, which is suitable for integrations that require continuous operation without interruption. Updating this value (e.g., setting it to a specific number of minutes) would cause the session to time out after that period, potentially disrupting long-running integrations. However, this setting pertains to session duration, not the method of authentication or whether UI access is allowed. It does not prevent the ISU from logging into the UI or ensure that authentication occurs only via web services, making this option irrelevant to the question.
Option D: Generate a random password.Generating a random password for the ISU is a good security practice to ensure the credentials are strong and not easily guessable. However, the password itself does not dictate how the ISU authenticates or whether it can access the UI. A random password enhances security but does not inherently restrict the ISU to web service authentication. Without selecting "Do Not Allow UI Sessions," the ISU could still log into the UI with that password, assuming no other restrictions are applied. Thus, this option does not fulfill the requirement of ensuring authentication only via web services.
Why Option B is Correct
The "Do Not Allow UI Sessions" checkbox is a specific configuration in the ISU setup process that directly enforces the restriction of authentication to web services. This setting is part of Workday's security framework for integrations, ensuring that ISUs-designed as non-human accounts for programmatic access-cannot be used interactively. This aligns with Workday's best practices for securing integrations, as outlined in the Workday Pro Integrations Study Guide and related documentation. For example, when an ISU is created with this checkbox selected, any attempt to log into the Workday UI with its credentials will fail, while web service requests (e.g., via SOAP or REST APIs) will succeed, assuming proper permissions are granted via an ISSG.
Practical Application
To implement this in Workday:
Log into your Workday tenant with administrative privileges.
Search for and select the "Create Integration System User" task.
Enter a username and password for the ISU.
Check the "Do Not Allow UI Sessions" checkbox.
Leave "Session Timeout Minutes" at 0 (default) to avoid session expiration during integrations.
Save the ISU and assign it to an appropriate ISSG (constrained or unconstrained, depending on the integration's needs).
This configuration ensures the ISU is locked to web service authentication, meeting the question's objective.
Verification with Workday Documentation
The Workday Pro Integrations Study Guide emphasizes securing ISUs by restricting them to integration-specific tasks. The "Do Not Allow UI Sessions" option is highlighted as a key control for preventing UI access, ensuring that ISUs operate solely through web services. This is also consistent with broader Workday security training materials, such as those available on Workday Community, which stress isolating integration accounts from human user activities.
Workday Pro Integrations Study Guide Reference
Section: Integration Security Fundamentals - Discusses the role of ISUs and the importance of restricting their access to programmatic interactions.
Section: Configuring Integration System Users - Details the "Create Integration System User" task, including the "Do Not Allow UI Sessions" checkbox as a security control.
Section: Best Practices for Integration Security - Recommends using this setting to enforce least privilege and protect the tenant from unauthorized UI access by integration accounts.
質問 # 80
What is the task used to upload a new XSLT file for a pre-existing document transformation integration system?
正解：B
質問 # 81
After you transfer ownership of an Integration System to an ISU, what other component, if it exists, must you transfer ownership of to ensure the integration continues to run in an automated fashion?
正解：D
解説：
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.
質問 # 82
Which features must all XSLT files contain to be considered valid?
正解：B
解説：
A valid XSLT file must include the following key components:
Root Element: <xsl:stylesheet> or <xsl:transform>
Namespace Declaration: Usually xmlns:xsl="http://www.w3.org/1999/XSL/Transform" At Least One <xsl:template> to define transformation behavior From W3C and Workday documentation:
"A valid XSLT file must contain a stylesheet root element, a namespace, and at least one template to be considered executable." Why others are incorrect:
A . Prefix and header are not structural requirements.
B . "Transformation" is vague; it's the template that implements it.
C . Headers and footers are not required or defined elements in XSLT.
質問 # 83
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 output the value of a calculated field which you created for inclusion in this integration?
正解：C
解説：
The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data, with a requirement to include a calculated field in the output. Core Connectors rely on predefined field mappings, but custom calculated fields need specific configuration to be included. Let's analyze the solution:
Requirement:Output the value of a calculated field created for this integration. In Workday, calculated fields are custom-built (e.g., using Report Writer or Calculated Fields) and not part of the standard Core Connector template, so they must be explicitly added to the output.
Integration Field Overrides:In Core Connectors, Integration Field Overrides allow you to replace a delivered field's value or add a new field to the output by mapping it to a calculated field. This is the standard method to include custom calculated fields in the integration file. You create the calculated field separately, then use overrides to specify where its value appears in the output structure (e.g., as a new column or replacing an existing field).
Option Analysis:
A . Configure Integration Field Attributes: Incorrect. Integration Field Attributes refine how delivered fields are output (e.g., filtering multi-instance data like phone type), but they don't support adding or mapping calculated fields.
B . Configure Integration Field Overrides: Correct. This configuration maps the calculated field to the output, ensuring its value is included in the exported file.
C . Configure Integration Attributes: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery protocol), not field-specific outputs like calculated fields.
D . Configure Integration Maps: Incorrect. Integration Maps transform existing field values (e.g., "Married" to "M"), but they don't add new fields or directly output calculated fields.
Implementation:
Create the calculated field in Workday (e.g., via Create Calculated Field task).
Edit the Core Connector: Worker integration.
Navigate to the Integration Field Overrides section.
Add a new override, selecting the calculated field and specifying its output position (e.g., a new field ID or overriding an existing one).
Test the integration to confirm the calculated field value appears in the output file.
Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on "Configuring Integration Field Overrides" explains how to include calculated fields in Core Connector outputs.
Integration System Fundamentals: Notes the use of overrides for custom data in predefined integration templates.
質問 # 84
......
Workday-Pro-Integrations合格資料: https://www.it-passports.com/Workday-Pro-Integrations.html
BONUS！！！ It-Passports Workday-Pro-Integrationsダンプの一部を無料でダウンロード：https://drive.google.com/open?id=1gW2Pw_9GF2bZuP17A31piM4_h5RnmIWC