In Workday HCM, business process definitions consist of multiple steps that may include approvals, notifications, integrations, or system actions. Some steps are configured to initiate a subprocess , meaning that when the step runs, it launches another related business process, such as compensation changes, provisioning, or document generation. Identifying whether a step triggers a subprocess is essential for troubleshooting, impact analysis, and process design.
The correct tab to determine whether a step initiates a subprocess is Allowed Services . The Allowed Services tab displays the services (subprocesses) that can be launched from a specific step within the business process definition. If a step is configured to initiate a subprocess, it will be clearly listed on this tab, indicating which downstream business processes may be triggered when the step executes.
The other options do not provide this information. Available Rules and Fields lists condition rules and data fields that can be used for routing or validations but does not show subprocess initiation. Allowed Actions by Role defines what actions security roles can perform during the business process, such as approve or cancel, and is unrelated to subprocess execution. Notifications shows alert and message configurations but does not indicate subprocess behavior.
From a Workday Pro HCM perspective, the Allowed Services tab is a critical tool for understanding process orchestration within Workday. It helps administrators visualize dependencies between business processes and ensures that changes to one process do not unintentionally impact others.
Therefore, the correct and Workday-verified answer is Allowed Services , as it identifies whether a business process step initiates a subprocess.

TheEmployee Compensation Auditreport is specifically designed to identifymismatches between compensation plan eligibility and actual plan assignment. It highlights situations where employees are assigned compensation plans theyshould not have, as well as cases where employees are eligible but not assigned.
In this scenario, the goal is to identify employees who areassigned to bonus plans despite not meeting eligibility rules. The Employee Compensation Audit report includes a dedicated section forAssigned Ineligible Compensation Components, making it the most accurate and efficient reporting tool for this requirement.
Other reports do not serve this purpose:
* The Compensation Plan Rollout Process is transactional and informational only.
* Employees Assigned Multiple Bonus Plans focuses on duplication, not eligibility.
* Compensation Spreadsheets are manual and lack eligibility validation logic.
Therefore, the correct report isEmployee Compensation Audit, making optionDcorrect.

Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core - Security and Business Process Framework Guide, 2023R2):
When a worker who is part of aRole-Based Security Group (RBSG)transfers to a different position, Workday automatically reviews the roles associated with theirsupervisory organizationthrough theAssign Rolessubprocess.
TheAssign Rolessubprocess within theChange Jobbusiness process ensures that role assignments (such as HR Partner, Manager, or Payroll Partner) are updated according to the new supervisory organization's configuration. This automation helps maintain proper security access and prevents users from retaining permissions tied to their previous role or organization.
Option A (Assign Pay Group) manages payroll assignment, not security.
Option B (Manage Job History) records past job data, unrelated to role security.
Option D (Manage Business Processes for Worker) handles process configurations, not security group updates.
Thus,Assign Rolesis the correct subprocess to maintain accurate security group membership during position changes.
Reference (Paraphrased Source):
Workday Pro HCM Core - Security and Business Process Configuration Guide (2023R2), Section: "Role Assignments in Staffing Events."

After a business process completes in Workday, the valid corrective action that can be taken is toRescindthe process. TheRescindaction allows an authorized user (typically with HR Partner or BP Administrator access) to reverse the completed business process, effectively undoing the transaction and restoring the system to its prior state.
This is often used when incorrect data was entered, or when the transaction was completed prematurely.
Rescinding a process automatically generates related rescind events and notifications, ensuring system integrity.
Option A (Cancel) applies toin-progressbusiness processes only - it stops a process before completion.
Option B (Reassign) allows task ownership changes while a process is active but not after completion.
Option D (Delegate) is a security feature for work delegation, not a post-completion action.
Thus,Rescindis the only valid corrective action once a BP is finalized.
Reference (Paraphrased Source):
Workday Pro HCM Core - Business Process Framework and Transaction Correction Guide (2023R2), Section: "Rescind and Cancel Business Processes."

Advanced routing restrictions are used when a normal role-based routing rule would create an inappropriate assignment, such as routing a review step back to the person who initiated the transaction. In this scenario, the review step is assigned to the HR Partner, but if the HR Partner starts the Termination event, that same HR Partner should not complete the review. The requirement is to route the step to the terminated worker's manager, which means the alternate assignee must be determined from the transaction target, not from the initiator's own supervisory relationship. Therefore, the correct configuration is to exclude the initiator and specify the manager relative to the transaction as the alternate security group. Excluding the initiator without an alternate would leave the step without a valid participant in some cases. Specifying the manager of the excluded user could route to the HR Partner's manager, which is not the business requirement. Excluding the prior approver addresses a different segregation-of-duties scenario. Reference topics: Business Processes, Advanced Routing Restrictions, Exclude Initiator, Alternate Security Group, and transaction-relative routing.