The Workday Pro HCM Core Certification Exam (Workday-Pro-HCM-Core)

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 HCM, approval authority is granted through business process security policies , not by assigning individual users directly to steps within a business process definition. Business process definitions determine what steps exist, while business process security policies determine who can perform actions on those steps.

When an employee is promoted, compensation changes are handled through the Propose Compensation Change business process. Even though the promotion itself occurs within the Change Job business process, the approval of compensation changes is controlled separately. This separation allows organizations to assign different approvers for job changes and compensation decisions, supporting strong governance and segregation of duties.

To grant a user the ability to approve compensation changes related to promotions, the user must be assigned to a security group that has permission to perform the Approve action on the Propose Compensation Change business process security policy . Once the user is a member of that security group and the changes are activated, Workday will route compensation approval tasks to them when applicable.

Options B and D are incorrect because users are never assigned directly to individual steps within a business process definition. Step routing is driven by security groups, not individual users. Option A is incorrect because the Change Job business process controls job-related actions, not compensation approval.

From a Workday Pro HCM best-practice standpoint, always grant approval access by updating the appropriate business process security policy and assigning users to the correct security groups . This ensures scalable, auditable, and role-based access control.

Therefore, the correct and Workday-verified answer is Assign the user to a security group with permissions to the Approve action on the Propose Compensation Change business process security policy .

The correct answer is A – Job Family/Job Family Group.

In Workday, Job Families and Job Family Groups are used to organize Job Profiles into logical categories for reporting, analysis, and security. This structure helps organizations group related roles, such as “HR Generalist” and “HR Business Partner” under the Human Resources Job Family , and all HR-related families under the Corporate Services Job Family Group .

When creating or editing a Job Profile, assigning a Job Family allows Workday to automatically associate it with the corresponding Job Family Group . These relationships are vital for talent management, compensation structures, and reporting purposes (for example, grouping compensation grades by department).

In Workday HCM, the ability to run reports , including Workday-delivered standard reports , is governed by domain security , not by report writer or administrator roles. Domain security controls access to the data itself , and without access to the underlying domains referenced by a report, a user cannot run the report—even if the report is standard and delivered by Workday.

Standard reports are prebuilt and do not require report creation or modification privileges. Therefore, users do not need to be members of the Report Writer or Report Administrator security groups to run them. Those roles are only required for creating, copying, modifying, or administering reports—not for execution.

Additionally, access to a business process is unrelated to report execution. Business process security determines who can initiate or participate in transactions such as Hire or Termination, but it does not control visibility into report data.

Workday evaluates a user’s domain security policies at runtime to determine whether they can access the data objects used in the report. If the user lacks permission to one or more required domains, the report will either fail to run or return incomplete or restricted results. This applies equally to standard and custom reports.

From a Workday Pro HCM best-practice standpoint, ensuring users have the appropriate domain access —typically through role-based or user-based security groups—is the correct way to enable report execution. Report access groups alone are insufficient without the necessary domain permissions.

Therefore, the correct and Workday-verified reason a user cannot run a Workday Standard Report is that the user does not have access to the appropriate domain .

In Workday, compensation plans remain active through the Actual End Date entered on the plan. The system removes the plan the day after the Actual End Date, ensuring the employee receives compensation through the final eligible day.

This behavior supports accurate payroll calculation and avoids prematurely ending compensation. Workday does not delay removal to the end of the pay period or month unless explicitly configured elsewhere.

Therefore, the plan is removed on the actual end date plus one day , making option A correct.

The correct answer is C – Offers greater control on each position open within an organization.

The Position Management staffing model is designed for organizations that require precise headcount control and visibility into staffing levels. Each position represents a discrete role that must be created, approved, and tracked before a hire occurs.

This model provides a high degree of control over:

Vacancies and filled positions

Position attributes (FTE, job profile, location, etc.)

Time-to-fill metrics for open roles

Because every hire is linked to a specific position, administrators can effectively monitor workforce planning, budgeting, and resource allocation.

In Workday HCM, access to worklets , including delivered worklets such as the Pay App , is governed by domain security , not business process security. Worklets display data and provide navigation to reports, tasks, and applications, all of which rely on domain-level permissions to control visibility and access.

To prevent Contingent Workers from seeing or accessing the Pay App on their Home landing page, you must remove their associated security group from the domain security policy that grants access to pay-related data. Once domain access is removed, the Pay App will no longer appear for those users because Workday dynamically displays worklets based on the user’s domain permissions.

Business process security policies control who can participate in transactional processes —such as initiating or approving a Hire, Change Job, or Termination—and do not influence whether a worklet appears on the Home page. Therefore, options B and D are incorrect because modifying business process security would not affect worklet visibility.

Option C is also incorrect because adding a security group to a domain security policy would grant access, not restrict it.

From a Workday Pro HCM best-practice perspective, restricting access to delivered worklets is always achieved through domain security policy configuration . This ensures consistent behavior across dashboards, reports, and applications tied to sensitive data such as compensation and payroll.

Therefore, the correct and Workday-verified way to prevent Contingent Workers from accessing the Pay App is to remove the security group from the domain security policy .

In Workday, when multiple configurable compensation bases qualify for an employee, the system determines the primary compensation basis using ranking precedence . The compensation basis with the lowest numerical ranking takes priority, provided the employee meets its eligibility criteria. Unranked compensation bases are only used when no ranked bases apply.

In this scenario, the employee is:

Full-time

Not in sales

Located in Mexico

Based on eligibility:

Total Compensation Non-Sales applies (full-time, non-sales).

Total Pay (Mexico) applies (Mexican employees).

Salary and Seniority applies (all employees).

Among these, Total Compensation Non-Sales has the highest priority because it has the lowest ranking value (20) . Although Total Pay (Mexico) is country-specific, its ranking (40) gives it lower precedence. Salary and Seniority is unranked and therefore only applies if no ranked basis qualifies, which is not the case here.

Workday’s compensation basis evaluation logic always selects the highest-ranked (lowest number) qualifying basis as the primary basis for compensation calculations and validations.

Therefore, the correct answer is Total Compensation Non-Sales .

The Set Up Allowance Plan Adjustment task is specifically designed to update allowance plan amounts for existing employee assignments when plan targets change. Simply editing the allowance plan amount ensures new employees receive the updated value, but it does not automatically update existing employees already assigned to the plan.

By running the Allowance Plan Adjustment task and selecting Adjust to New Defaults , Workday evaluates all employees assigned to the plan and updates their allowance amounts to match the new default value of $3,500.

Manually updating employees through Request Compensation Change is inefficient and error-prone. Creating a new plan introduces unnecessary complexity and disrupts reporting continuity.

Therefore, the correct and Workday-recommended approach is to run Set Up Allowance Plan Adjustment and adjust to new defaults, making option D correct.