Exam Workday Workday-Pro-Integrations Collection | Reliable Workday-Pro-Integrations Guide Files
2025 Latest PassLeader Workday-Pro-Integrations PDF Dumps and Workday-Pro-Integrations Exam Engine Free Share: https://drive.google.com/open?id=1kygbnYp-xVIahYWCaHFvtg7giOrpRgUc
Passing the Workday-Pro-Integrations exam certification will be easy and fast, if you have the right resources at your fingertips. As the advanced and reliable website, PassLeader will offer you the best study material and help you 100% pass. Workday-Pro-Integrations online test engine can simulate the actual test, which will help you familiar with the environment of the Workday-Pro-Integrations real test. The Workday-Pro-Integrations self-assessment features can bring you some convenience. The 24/7 customer service will be waiting for you, if you have any questions.
Owning PassLeader is to have a key to pass Workday-Pro-Integrations exam certification. PassLeader's Workday-Pro-Integrations exam certification training materials is the achievement that our IT elite team take advantage of their own knowledge and experience, and grope for rapid development and achievements of the IT industry. Its authority is undeniable. Before purchase PassLeader's Workday-Pro-Integrations Braindumps, you can download Workday-Pro-Integrations free demo and answers on probation on PassLeader.COM.
>> Exam Workday Workday-Pro-Integrations Collection <<
Reliable Workday-Pro-Integrations Guide Files, Workday-Pro-Integrations Valid Braindumps
Workday-Pro-Integrations exam dumps save your study and preparation time. Our experts have added hundreds of Workday Pro Integrations Certification Exam (Workday-Pro-Integrations) questions similar to the real exam. You can prepare for the Workday Pro Integrations Certification Exam (Workday-Pro-Integrations) exam dumps during your job. You don't need to visit the market or any store because PassLeader Workday Pro Integrations Certification Exam (Workday-Pro-Integrations) exam questions are easily accessible from the website.
Workday Pro Integrations Certification Exam Sample Questions (Q66-Q71):
NEW QUESTION # 66
Refer to the scenario. You are implementing a Core Connector: Worker integration to send employee data to a third-party active employee directory. The external vendor requires the following:
* The Employee's Active Directory User Principal Name.
* A mapping from Worker Type values to external worker type codes.
* A specific filename format that includes a timestamp and sequence number.
You also need to ensure the document transformation occurs before the file is delivered to the endpoint. You must include an Employee's Active Directory User Principal Name (generated by a Calculated Field).
How do you ensure this field is pulled into the output?
Answer: C
Explanation:
To surface a Calculated Field in a Core Connector: Worker (CCW) outbound, you use an Integration Field Override to substitute the connector's default source with your calculated value. An integration map (Option A) is intended to translate or normalize code values (for example, mapping internal Worker Type codes to the vendor's codes), not to replace the source of a field. Integration attributes (Option D) and integration field attributes (Option C) manage connector behavior and attributes, but they do not replace a field's data source with a calculated field. Therefore, the correct method to "pull" a calculated field into the CCW output is an Integration Field Override (Option B).
Why the other elements in the scenario matter (and how they're handled) - with exact extracts from your materials:
* Mapping Worker Type to external codes # Integration Maps (supports, but not the asked action):Your deployment guides call out maintaining and using Integration System Maps for code translations. This is exactly where you'd map "Worker Type" to the external system's codes, but it is not how you inject a calculated field into the payload.
"Maintenance of Integration System Maps"
"WORKDAY SETUP - NON STATIC MAPS" and "WORKDAY SETUP - STATIC MAPS" (table of contents for configuration of maps)
* Filename requires timestamp/sequence number # Sequence Generator (supports the scenario):Your Time Tracking/PECI deployment guide explicitly includes a Sequence Generator configuration that's used with certified connectors to build compliant, unique file names (often with timestamps and/or sequence numbers) before delivery.
"3.6 Sequence Generator" (configuration item for certified integrations used in file naming)
* Transformation before delivery # Standard integration flow (transform then deliver):The same deployment materials describe document/file delivery mechanics (for example, SFTP), which occur after the integration produces/transforms the document. This supports the scenario requirement that transformation happens prior to transmission.
"4. FILE DELIVERY SERVICE ... 4.4 SFTP Configuration" (document delivery occurs after the integration generates/transforms the output)
* Security posture for integrations (context):For outbound/system users and secure delivery, the Workday Authentication & Security guide documents integration-appropriate authentication (e.g., X.509) and general integration security steps - relevant background for productionizing CCW but not directly affecting how to bring a calculated field into the payload.
"X509 Recommended for web services users and integrations that use an integration system user account." Putting it all together for the scenario:
* Use Integration Field Override to point the CCW field to your Calculated Field for UPN # (Correct answer: B).
* Use Integration Maps to translate Worker Type to the vendor's codes (supports the mapping requirement).
* Configure filename rules via Sequence Generator to include timestamp and sequence in the produced file name (supports the file-naming requirement).
* Ensure the document transformation runs as part of the integration generation step and then deliver via SFTP (file delivery service).
References (Workday Pro: Integrations-aligned materials):
* GPC_PECI_TimeTracking_DeploymentGuide_CloudPay.pdf - Sections "3.6 Sequence Generator" and "4. File Delivery Service" (delivery occurs after file generation/transform).
* GPC_PECI_DeploymentGuide_CloudPay_2.9.pdf - Map configuration sections ("WORKDAY SETUP - NON STATIC MAPS", "WORKDAY SETUP - STATIC MAPS").
* GPC_PECI_UserGuide_CloudPay_2.1.1.pdf - "Maintenance of Integration System Maps."
* Admin-Guide-Authentication-and-Security.pdf - Integration security notes, including X.509 recommendation for integrations.
NEW QUESTION # 67
You have successfully configured an ISU and an ISSG with the correct security policies and have assigned them to an EIB.
What task do you need to run before you can launch the EIB?
Answer: C
Explanation:
In Workday, after configuring an Integration System User (ISU) and an Integration System Security Group (ISSG) with the appropriate security policies and assigning them to an Enterprise Interface Builder (EIB) integration, there is a critical step required before the EIB can be launched successfully. This step ensures that all security configurations and permissions assigned to the ISSG take effect in the Workday tenant. Let's analyze the question and evaluate each option systematically to determine the correct task, ensuring the answer aligns with Workday's documented processes and the Workday Pro Integrations Study Guide.
Context of the Scenario
You've completed the following:
Created an ISU and configured it (e.g., with "Do Not Allow UI Sessions" checked for web service-only access).
Set up an ISSG and assigned the ISU to it.
Defined the necessary security policies (e.g., domain security policies with "Get" and/or "Put" access) for the ISSG to support the EIB's operations.
Assigned the ISU and ISSG to the EIB integration system.
The question now is what must be done before launching the EIB to ensure it functions as intended. In Workday, changes to security policies-such as adding permissions to an ISSG-do not take effect immediately. They remain in a "pending" state until activated, which is a key aspect of Workday's security administration process.
Evaluation of Options
Option A: Activate Pending Security Policy ChangesIn Workday, whenever you modify security policies (e.g., granting domain permissions like "Integration Build" or "Custom Report Creation" to an ISSG), these changes are staged as "pending." To apply them to the tenant and make them active, you must run the "Activate Pending Security Policy Changes" task. This task reviews all pending security updates, allows you to add a comment for audit purposes, and, upon confirmation, activates the changes. Without this step, the ISSG will not have the effective permissions required for the EIB to access data or execute its operations, potentially causing the launch to fail due to insufficient authorization. This aligns directly with the scenario, as security policies have been configured and assigned, but not yet activated.
Option B: View Security for Securable ItemThe "View Security for Securable Item" report is a diagnostic tool in Workday that allows you to inspect the security configuration for a specific object (e.g., a web service operation, report, or task). It shows which security groups have access and what permissions (e.g., "Get," "Put," "View," "Modify") are granted. While this is useful for verifying that the ISSG has the correct policies assigned, it is a passive report-it does not modify or activate anything. Running this task would not enable the EIB to launch, as it doesn't affect the pending security changes. Thus, it's not the required step before launching the EIB.
Option C: Assign the ISSG to only one security policyThis option suggests limiting the ISSG to a single security policy, but this is neither a standard Workday requirement nor a task that exists as a standalone action. ISSGs can and often do have multiple security policies assigned (e.g., permissions for various domains like "Integration Build," "Custom Report Access," etc.), depending on the integration's needs. Moreover, the question states that the ISSG has already been configured with the "correct security policies" and assigned to the EIB, implying this step is complete. Restricting the ISSG to one policy after the fact would require editing permissions again, triggering more pending changes, and still necessitate activation-making this option illogical and incorrect.
Option D: Maintain Integration Security PoliciesThere is no specific task in Workday called "Maintain Integration Security Policies." This option seems to be a misnomer or a conflation of other tasks, such as "Maintain Domain Permissions for Security Group" (used to assign permissions to an ISSG) or broader security maintenance activities. However, the question indicates that the security policies are already correctly configured and assigned. If this option intended to imply further configuration, it would still result in pending changes requiring activation via Option A. As a standalone action, it does not represent a valid or necessary task to enable the EIB launch.
Why Option A is Correct
The "Activate Pending Security Policy Changes" task is a mandatory step in Workday's security workflow after modifying security policies, such as those assigned to an ISSG for an EIB. Workday's security model uses a pending changes queue to ensure that updates are reviewed and deliberately applied, maintaining control and auditability. Without activating these changes:
The ISSG will lack the effective permissions needed for the EIB to access required domains or perform its operations (e.g., retrieving data from a custom report or delivering a file).
The EIB launch could fail with errors like "Insufficient Privileges" or "Access Denied." Running this task ensures that the security configuration is live, allowing the ISU (via the ISSG) to authenticate and execute the EIB successfully. This is a standard practice in Workday integration setup, as emphasized in the Workday Pro Integrations curriculum.
Practical Steps to Perform Option A
Log into the Workday tenant with a security administrator role.
Search for and select the "Activate Pending Security Policy Changes" task.
Review the list of pending changes (e.g., new permissions added to the ISSG).
Enter a comment (e.g., "Activating security for EIB launch - ISSG permissions").
Check the "Confirm" box and click "OK" to activate the changes.
Once completed, the security policies are live, and the EIB can be launched.
Verification with Workday Documentation
The Workday Pro Integrations Study Guide and related training materials confirm that activating pending security policy changes is a prerequisite after configuring security for integrations. This step ensures that all permissions are in effect, enabling the ISU and ISSG to support the EIB's functionality. Community resources and implementation guides also consistently highlight this task as the final step before launching integrations that rely on updated security settings.
Workday Pro Integrations Study Guide Reference
Section: Integration Security Configuration - Explains the process of assigning security policies to ISSGs and the need to activate changes to operationalize them.
Section: Enterprise Interface Builder (EIB) - Notes that security updates for EIBs must be activated before launching to ensure proper access.
Section: Security Administration - Details the "Activate Pending Security Policy Changes" task as the mechanism to apply pending security modifications across the tenant.
NEW QUESTION # 68
You have successfully configured an ISU and an ISSG with the correct security policies and have assigned them to an EIB.
What task do you need to run before you can launch the EIB?
Answer: C
Explanation:
In Workday, after configuring an Integration System User (ISU) and an Integration System Security Group (ISSG) with the appropriate security policies and assigning them to an Enterprise Interface Builder (EIB) integration, there is a critical step required before the EIB can be launched successfully. This step ensures that all security configurations and permissions assigned to the ISSG take effect in the Workday tenant. Let's analyze the question and evaluate each option systematically to determine the correct task, ensuring the answer aligns with Workday's documented processes and the Workday Pro Integrations Study Guide.
Context of the Scenario
You've completed the following:
* Created an ISU and configured it (e.g., with "Do Not Allow UI Sessions" checked for web service-only access).
* Set up an ISSG and assigned the ISU to it.
* Defined the necessary security policies (e.g., domain security policies with "Get" and/or "Put" access) for the ISSG to support the EIB's operations.
* Assigned the ISU and ISSG to the EIB integration system.
The question now is what must be done before launching the EIB to ensure it functions as intended. In Workday, changes to security policies-such as adding permissions to an ISSG-do not take effect immediately. They remain in a "pending" state until activated, which is a key aspect of Workday's security administration process.
Evaluation of Options
* Option A: Activate Pending Security Policy ChangesIn Workday, whenever you modify security policies (e.g., granting domain permissions like "Integration Build" or "Custom Report Creation" to an ISSG), these changes are staged as "pending." To apply them to the tenant and make them active, you must run the "Activate Pending Security Policy Changes" task. This task reviews all pending security updates, allows you to add a comment for audit purposes, and, upon confirmation, activates the changes. Without this step, the ISSG will not have the effective permissions required for the EIB to access data or execute its operations, potentially causing the launch to fail due to insufficient authorization. This aligns directly with the scenario, as security policies have been configured and assigned, but not yet activated.
* Option B: View Security for Securable ItemThe "View Security for Securable Item" report is a diagnostic tool in Workday that allows you to inspect the security configuration for a specific object (e.
g., a web service operation, report, or task). It shows which security groups have access and what permissions (e.g., "Get," "Put," "View," "Modify") are granted. While this is useful for verifying that the ISSG has the correct policies assigned, it is a passive report-it does not modify or activate anything. Running this task would not enable the EIB to launch, as it doesn't affect the pending security changes. Thus, it's not the required step before launching the EIB.
* Option C: Assign the ISSG to only one security policyThis option suggests limiting the ISSG to a single security policy, but this is neither a standard Workday requirement nor a task that exists as a standalone action. ISSGs can and often do havemultiple security policies assigned (e.g., permissions for various domains like "Integration Build," "Custom Report Access," etc.), depending on the integration's needs. Moreover, the question states that the ISSG has already been configured with the "correct security policies" and assigned to the EIB, implying this step is complete. Restricting the ISSG to one policy after the fact would require editing permissions again, triggering more pending changes, and still necessitate activation-making this option illogical and incorrect.
* Option D: Maintain Integration Security PoliciesThere is no specific task in Workday called
"Maintain Integration Security Policies." This option seems to be a misnomer or a conflation of other tasks, such as "Maintain Domain Permissions for Security Group" (used to assign permissions to an ISSG) or broader security maintenance activities. However, the question indicates that the security policies are already correctly configured and assigned. If this option intended to imply further configuration, it would still result in pending changes requiring activation via Option A. As a standalone action, it does not represent a valid or necessary task to enable the EIB launch.
Why Option A is Correct
The "Activate Pending Security Policy Changes" task is a mandatory step in Workday's security workflow after modifying security policies, such as those assigned to an ISSG for an EIB. Workday's security model uses a pending changes queue to ensure that updates are reviewed and deliberately applied, maintaining control and auditability. Without activating these changes:
* The ISSG will lack the effective permissions needed for the EIB to access required domains or perform its operations (e.g., retrieving data from a custom report or delivering a file).
* The EIB launch could fail with errors like "Insufficient Privileges" or "Access Denied." Running this task ensures that the security configuration is live, allowing the ISU (via the ISSG) to authenticate and execute the EIB successfully. This is a standard practice in Workday integration setup, as emphasized in the Workday Pro Integrations curriculum.
Practical Steps to Perform Option A
* Log into the Workday tenant with a security administrator role.
* Search for and select the "Activate Pending Security Policy Changes" task.
* Review the list of pending changes (e.g., new permissions added to the ISSG).
* Enter a comment (e.g., "Activating security for EIB launch - ISSG permissions").
* Check the "Confirm" box and click "OK" to activate the changes.
* Once completed, the security policies are live, and the EIB can be launched.
Verification with Workday Documentation
The Workday Pro Integrations Study Guide and related training materials confirm that activating pending security policy changes is a prerequisite after configuring security for integrations. This step ensures that all permissions are in effect, enabling the ISU and ISSG to support the EIB's functionality. Community resources and implementation guides also consistently highlight this task as the final step before launching integrations that rely on updated security settings.
Workday Pro Integrations Study Guide References
* Section: Integration Security Configuration- Explains the process of assigning security policies to ISSGs and the need to activate changes to operationalize them.
* Section: Enterprise Interface Builder (EIB)- Notes that security updates for EIBs must be activated before launching to ensure proper access.
* Section: Security Administration- Details the "Activate Pending Security Policy Changes" task as the mechanism to apply pending security modifications across the tenant.
NEW QUESTION # 69
Refer to the following scenario to answer the question below. Your integration has the following runs in the integration events report (Date format of MM/DD/YYYY):
Run #1
* Core Connector: Worker Integration System was launched on May 15, 2024 at 3:00:00 AM
* As of Entry Moment: 05/15/2024 3:00:00 AM
* Effective Date: 05/15/2024
* Last Successful As of Entry Moment: 05/01/2024 3:00:00 AM
* Last Successful Effective Date: 05/01/2024
Run #2
* Core Connector: Worker Integration System was launched on May 31, 2024 at 3:00:00 AM
* As of Entry Moment: 05/31/2024 3:00:00 AM
* Effective Date: 05/31/2024
* Last Successful As of Entry Moment: 05/15/2024 3:00:00 AM
* Last Successful Effective Date: 05/15/2024
On May 13, 2024 Brian Hill receives a salary increase. The new salary amount is set to $90,000.00 with an effective date of May 22, 2024. Which of these runs will include Brian Hill's compensation change?
Answer: C
Explanation:
The scenario involves a Core Connector: Worker integration with two runs detailed in the integration events report. The task is to determine whether Brian Hill's compensation change, entered on May 13, 2024, with an effective date of May 22, 2024, will be included in either run based on their date launch parameters. Let's analyze each run against the change details.
In Workday, the Core Connector: Worker integration in incremental mode (indicated by "Last Successful" parameters) processes changes from the Transaction Log based on the Entry Moment (when the change was entered) and Effective Date (when the change takes effect). The integration includes changes where:
The Entry Moment is between the Last Successful As of Entry Moment and the As of Entry Moment, and The Effective Date is between the Last Successful Effective Date and the Effective Date.
Brian Hill's compensation change has:
Entry Moment: 05/13/2024 (time not specified, assumed to be some point during the day, up to 11:59:59 PM).
Effective Date: 05/22/2024.
Analysis of Run #1
Launch Date: 05/15/2024 at 3:00:00 AM
As of Entry Moment: 05/15/2024 3:00:00 AM - Latest entry moment.
Effective Date: 05/15/2024 - Latest effective date.
Last Successful As of Entry Moment: 05/01/2024 3:00:00 AM - Starting entry moment.
Last Successful Effective Date: 05/01/2024 - Starting effective date.
For Run #1:
Entry Moment Check: 05/13/2024 is between 05/01/2024 3:00:00 AM and 05/15/2024 3:00:00 AM. This condition is met.
Effective Date Check: 05/22/2024 is after 05/15/2024 (Effective Date). This condition is not met.
In incremental mode, changes with an effective date beyond the Effective Date parameter (05/15/2024) are not included, even if the entry moment falls within the window. Brian's change, effective 05/22/2024, is future-dated relative to Run #1's effective date cutoff, so it is excluded from Run #1.
Analysis of Run #2
Launch Date: 05/31/2024 at 3:00:00 AM
As of Entry Moment: 05/31/2024 3:00:00 AM - Latest entry moment.
Effective Date: 05/31/2024 - Latest effective date.
Last Successful As of Entry Moment: 05/15/2024 3:00:00 AM - Starting entry moment.
Last Successful Effective Date: 05/15/2024 - Starting effective date.
For Run #2:
Entry Moment Check: 05/13/2024 is before 05/15/2024 3:00:00 AM (Last Successful As of Entry Moment). This condition is not met in a strict sense.
Effective Date Check: 05/22/2024 is between 05/15/2024 and 05/31/2024. This condition is met.
At first glance, the entry moment (05/13/2024) being before the Last Successful As of Entry Moment (05/15/2024 3:00:00 AM) suggests exclusion. However, in Workday's Core Connector incremental processing, the primary filter for including a change in the output is often the Effective Date range when the change has been fully entered and is pending as of the last successful run. Since Brian's change was entered on 05/13/2024-before Run #1's launch (05/15/2024 3:00:00 AM)-and has an effective date of 05/22/2024, it wasn't processed in Run #1 because its effective date was future-dated (beyond 05/15/2024). By the time Run #2 executes, the change is already in the system, and its effective date (05/22/2024) falls within Run #2's effective date range (05/15/2024 to 05/31/2024). Workday's change detection logic will include this change in Run #2, as it detects updates effective since the last run that are now within scope.
Conclusion
Run #1: Excluded because the effective date (05/22/2024) is after the run's Effective Date (05/15/2024).
Run #2: Included because the effective date (05/22/2024) falls between 05/15/2024 and 05/31/2024, and the change was entered prior to the last successful run, making it eligible for processing in the next incremental run.
Thus, C. Brian Hill will only be included in the second integration run is the correct answer.
Workday Pro Integrations Study Guide Reference
Workday Integrations Study Guide: Core Connector: Worker - Section on "Incremental Processing" explains how effective date ranges determine inclusion, especially for future-dated changes.
Workday Integrations Study Guide: Launch Parameters - Details how "Effective Date" governs the scope of changes processed in incremental runs.
Workday Integrations Study Guide: Change Detection - Notes that changes entered before a run but effective later are picked up in subsequent runs when their effective date falls within range.
NEW QUESTION # 70
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?
Answer: A
Explanation:
Understanding the Requirement
The question involves scheduling an integration in Workday to deliver a file containing recent compensation changes to an external system. The key requirements are:
* The file must be delivered routinely at 5 PM Eastern Standard Time (EST).
* The recurrence should exclude weekends (i.e., run only on weekdays: Monday through Friday).
* The file should include compensation changes since the last integration run, implying an incremental data pull, though this does not directly affect the recurrence type.
The task is to identify the correct recurrence type for the integration schedule from the given options:
A). Recurs every 12 hours
B). Recurs every weekday
C). Dependent recurrence
D). Recurs every 1 day(s)
Analysis of the Workflow and Recurrence Options
In Workday, integrations are scheduled using the Integration Schedule functionality, typically within tools like Enterprise Interface Builder (EIB) or Workday Studio, though this scenario aligns closely with EIB for routine file-based integrations. The recurrence type determines how frequently and under what conditions the integration runs. Let's evaluate each option against the requirements:
Step-by-Step Breakdown
* Time Specification (5 PM EST):
* Workday allows scheduling integrations at a specific time of day (e.g., 5 PM EST). This is set in the schedule configuration and is independent of the recurrence type but confirms the need for a daily-based recurrence with a specific time slot.
* Exclusion of Weekends:
* The requirement explicitly states the integration should not run on weekends (Saturday and Sunday), meaning it should only execute on weekdays (Monday through Friday). This is a critical filter for choosing the recurrence type.
* Incremental Data (Since Last Run):
* The file must include compensation changes since the last integration run. In Workday, this is typically handled by configuring the integration (e.g., via a data source filter or "changed since" parameter in EIB), not the recurrence type. Thus, this requirement does not directly influence the recurrence type but confirms the integration runs periodically.
NEW QUESTION # 71
......
Buying our Workday-Pro-Integrations study materials can help you pass the test easily and successfully. We provide the Workday-Pro-Integrations learning braindumps which are easy to be mastered, professional expert team and first-rate service to make you get an easy and efficient learning and preparation for the Workday-Pro-Integrations test. If you study with our Workday-Pro-Integrations exam questions for 20 to 30 hours, you will be bound to pass the exam smoothly. So what are you waiting for? Just come and buy our Workday-Pro-Integrations practice guide!
Reliable Workday-Pro-Integrations Guide Files: https://www.passleader.top/Workday/Workday-Pro-Integrations-exam-braindumps.html
Read on to find more important details about the Workday Workday-Pro-Integrations Exam Questions, Workday-Pro-Integrations exam torrent of us will help you pass the exam successfully, Workday Exam Workday-Pro-Integrations Collection 1005 valid guaranteed, Workday Exam Workday-Pro-Integrations Collection You send the failure score certification to our support email, In a short time of using Workday-Pro-Integrations updated study material, you can 100% pass the exam.
Children's books find a way to accomplish that simplicity and Workday-Pro-Integrations can inspire you to do the same, You will continue to have the chapter number precede the chapters and appendixes.
Read on to find more important details about the Workday Workday-Pro-Integrations Exam Questions, Workday-Pro-Integrations exam torrent of us will help you pass the exam successfully, 1005 valid guaranteed.
Pass Guaranteed Workday - Workday-Pro-Integrations –High-quality Exam Collection
You send the failure score certification to our support email, In a short time of using Workday-Pro-Integrations updated study material, you can 100% pass the exam.
BONUS!!! Download part of PassLeader Workday-Pro-Integrations dumps for free: https://drive.google.com/open?id=1kygbnYp-xVIahYWCaHFvtg7giOrpRgUc