Workday Workday-Pro-HCM-Core - Workday Pro HCM Core Certification Exam

The correct answers are C – Position Management and D – Job Management.

In Workday, supervisory organizations can only use one of two delivered staffing models:

Position Management : Each position is a distinct entity that must be created and approved before hiring. It supports detailed tracking of vacancies and headcount.

Job Management : Hiring is managed at the job level, allowing multiple workers to be hired under a single job requisition without individual position control.

Workday does not deliver “Headcount Management” or “Customer Defined Staffing Models” as valid options. The staffing model is selected when creating or editing a supervisory organization and determines how headcount, hiring, and reporting are managed.

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.

In Workday, the Manage Basis Total configuration enables organizations to enter a single total compensation amount , which Workday then allocates across multiple compensation plans according to predefined rules, percentages, or limits. This is particularly useful in countries like Italy, where compensation discussions often focus on total compensation rather than individual components.

When Manage Basis Total is enabled on a compensation basis, administrators or managers can enter one total amount during a staffing or compensation event. Workday automatically distributes that amount across salary, allowances, and other included plans based on the compensation basis configuration.

Eligible Earnings Override is a payroll-specific tool and does not control compensation entry behavior. Total Base Pay and Total Salary & Allowances are reporting or calculation concepts, not data entry mechanisms.

By using Manage Basis Total , the company ensures consistency, simplifies compensation entry, and enforces internal rules for Milan-based employees.

Therefore, the correct answer is Manage Basis Total .

In Workday HCM, period salary plans are specifically designed to support compensation structures where base pay is distributed over a defined number of periods that may not align with standard monthly or annual salary conventions. This is particularly important for countries such as Italy, where statutory or customary compensation practices include additional salary payments , often referred to as the 13th and 14th month salaries . These additional payments result in employees receiving more than 12 months of pay within a year.

A period salary plan allows organizations to define the number of salary periods per year , such as 12, 13, 14, or other values like 14.9, without altering the employee’s annualized base pay. This ensures compliance with local labor laws while maintaining consistent reporting, budgeting, and payroll calculations. Workday then prorates or distributes the annual amount appropriately across the defined periods.

Other plan types do not support this requirement. A salary plan assumes a standard annual salary without accommodating extra pay periods. Hourly plans are designed for workers paid based on time worked, and unit salary plans are used when pay is based on output or units produced, neither of which align with Italy’s statutory base pay structure.

Therefore, a period salary plan is the correct and Workday-recommended solution for handling additional months of base pay in countries with localized pay practices, making option A the correct answer.

The Compensation Spreadsheet is a powerful Workday reporting and analysis tool that allows managers and HR partners to view detailed compensation information for employees across one or more organizations they manage or support. It supports side-by-side viewing of key metrics, including:

Total base pay

Compensation package

Compa-ratio

Position in range

Allowances and bonuses

The spreadsheet format is specifically designed for managerial review, planning, and analysis , with optional inclusion of subordinate organizations. It is widely used during compensation review cycles and off-cycle analysis.

Other reports have more limited scope:

Employee Compensation Audit focuses on eligibility mismatches

Job Profile reports focus on structure, not worker-level pay

Total Rewards is employee-facing and not manager-analytic

Therefore, the correct answer is Compensation Spreadsheet , making option D correct.

In Workday, a Business Process (BP) defines how specific business events are executed within the system. The true statement among the options is that you can create business process definitions based on rules . Workday allows you to maintain rule-based BP definitions , meaning that a single BP can have multiple versions triggered under different conditions (for example, based on supervisory organization, company, location, or job profile).

This functionality enhances configuration flexibility by allowing organizations to adapt process flow depending on contextual attributes — without duplicating processes. Each version operates under a defined condition rule , evaluated at runtime to determine which BP definition applies.

Options A, B, and C are incorrect:

A is false because not every action step can be added to every process — the available step types depend on the BP template (for example, Hire, Change Job, or Request Compensation Change).

B is false since condition rules can only be applied to specific steps where the system allows configuration (for instance, approvals and to-dos).

C is false because only a designated Completion Step marks the end of the process, and it cannot be assigned arbitrarily to any step.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework and Configuration Guide (2023R2, Workday Learning).

Sections: “Rule-Based Business Process Definitions,” “Business Process Configuration Best Practices,” and “Condition Rule Framework.”

Workday delivers Overdue Notifications automatically to remind users that a step or task within a business process has not been completed within the expected time frame. These notifications are part of Workday’s built-in process monitoring and are generated by the system based on defined due dates or completion delays.

Overdue notifications ensure accountability by alerting users when a step is pending beyond its due date, helping maintain compliance with HR and operational timelines.

Options A ( Custom ) and C ( Alert ) refer to user-configurable messages and rule-based triggers that administrators create, but they are not delivered automatically by Workday unless specifically configured. Option D ( System ) refers to general system messages, not process-driven notifications.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework Configuration Guide (2023R2), Section: “Workday-Delivered Notifications and Overdue Task Alerts.”

In Workday HCM, business process security controls which security groups can participate in specific steps within a business process definition. Each step type—such as approval, review, or To Do—requires explicit permission for a security group to be eligible for selection. If a security group does not appear as an option when configuring a review step , it means the group has not been granted permission to act on that type of step.

To resolve this issue, you must update Who Can Do Action Steps in the Business Process . This section of the business process security policy defines which security groups are authorized to perform step-level actions , including review, approve, or to-do actions. Once the appropriate security group is added here and the changes are activated, the group becomes available for selection on the review step.

The other options do not address this requirement. Policy Restrictions control conditional logic and constraints, not step eligibility. Who Can Start the Business Process governs initiation permissions only and does not affect step assignment. Who Can Do Actions on Entire Business Process grants high-level actions such as cancel or rescind but does not authorize participation in individual steps like reviews.

From a Workday Pro HCM best-practice perspective, configuring Who Can Do Action Steps in the Business Process ensures precise control over step participation while maintaining separation of duties. After updating this section, administrators must remember to run Activate Pending Security Policy Changes for the update to take effect.

Therefore, the correct and Workday-verified answer is Who Can Do Action Steps in the Business Process .

A consolidated approval task combines multiple approval actions into a single approval experience, but the user who receives that consolidated task still needs the correct business process security permissions for each underlying process being approved. In this scenario, the HR Administrator must approve the termination details, retiree status, and service date changes. Therefore, the HR Administrator must be added to the Approve section for each relevant business process security policy: Termination, Add Retiree Status, and Service Dates Change. Ad Hoc Approve is not correct because the requirement is not to allow ad hoc approval routing; it is to permit the HR Administrator to perform the standard approval actions included in the consolidated approval. Initiating Action is also incorrect because initiating a process and approving a process are separate security actions. Granting initiate access would not authorize the user to approve the consolidated approval step. The security must match the action presented in the consolidated task. Therefore, adding the HR Administrator to the Approve section on all three processes is correct. Reference topics: Security, Business Process Security Policies, Consolidated Approval, Approve Permissions, and Termination subprocess security.