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

The correct answer is B – Create Position.

In Workday, when a supervisory organization uses the Position Management staffing model, each hire must be associated with a specific position. Before initiating a hire, an administrator or HR partner must execute the Create Position business process to establish that position record.

This process defines critical attributes such as:

Job Profile (e.g., HR Analyst, Accountant),

Location,

Time Type (Full-time/Part-time),

Worker Type (Employee or Contingent Worker),

Availability Date and Earliest Hire Date, and

Position Restrictions that control who and how hiring can occur.

Once the position is created and approved through the configured workflow, it becomes available for hiring via the Hire Employee business process. Without an open, approved position, the system will not allow a hire in Position Management organizations.

In Workday, a configurable compensation basis is used when an organization needs to group multiple compensation plans—such as salary, commission, and bonus—for purposes of calculation, validation, guidelines, and reporting. This type of basis allows administrators to explicitly select which compensation plans are included and define how they interact.

For a sales team, compensation commonly consists of base salary, variable commission earnings, and incentive or bonus plans. A configurable compensation basis is the only option that supports combining these different plan types into a single, controlled compensation framework. It also allows ranking, eligibility rules, and advanced controls such as Manage Basis Total.

Compensation grades define pay ranges and are not used to aggregate compensation components. Calculated compensation bases derive values from formulas and are not appropriate when simply grouping plans. The delivered Total Salary and Allowances basis does not include commission plans and cannot be extended to meet this requirement.

Therefore, creating a configurable compensation basis that includes salary, commission, and bonus plans is the correct and Workday-recommended solution, making option A correct.

The Employee Compensation Step Progression Audit report identifies employees who are eligible for step progression but have not yet been progressed. When employees appear on this report, it indicates that step progression logic is configured correctly, but the progression has not yet been executed.

The appropriate action is to run the Schedule Automatic Step Progression task. This task evaluates eligibility rules, durations, and progression criteria, and then automatically moves eligible employees to the next compensation step.

Modifying compensation steps or grades is unnecessary and incorrect if progression logic already exists. Change Job events should not be used for step progression, and grade job profile adjustments are unrelated.

Therefore, the correct action is to schedule automatic step progression, making option D correct.

The correct option is Routing Modifier.

In Workday, Routing Modifiers are used to dynamically adjust the routing of approval or review steps within a business process based on contextual changes, such as whether a worker’s supervisory organization or manager is changing. This configuration allows the system to intelligently determine whether the approval or notification step should go to the current manager (before the change) or the proposed manager (after the change).

For example, in the Job Change business process, when an employee is transferring to a new organization or manager, a routing modifier ensures that pre-transfer approvals route to the current manager, while post-transfer approvals route to the new (proposed) manager. This ensures accurate accountability and process flow alignment.

In Workday HCM, role-based (constrained) security groups control access to business processes and data based on an individual’s organizational assignments. The Access Rights to Organizations setting determines which organizations—and therefore which workers—fall within the scope of responsibility for users assigned to that security role.

When the Access Rights to Organizations setting is configured as Current Organization and All Subordinates, the HR Partner assigned to a supervisory organization gains security access to that organization and every subordinate organization beneath it in the hierarchy. This access applies regardless of whether subordinate organizations have their own HR Partners assigned.

In the context of employee terminations, this means HR Partners are responsible for approving termination events for employees who belong to the organization they directly support as well as employees in any subordinate supervisory organizations. Workday evaluates the worker’s organizational membership at the time of the transaction and routes the business process approval accordingly.

Options B and C are incorrect because Workday does not limit approvals based on whether subordinate organizations have HR Partners or restrict access to a single subordinate. Option D is also incorrect because it ignores subordinate organizations entirely, which contradicts the selected access rights configuration.

From a Workday Pro HCM security design perspective, this setting ensures appropriate oversight and continuity by allowing HR Partners to support broader organizational segments without creating security gaps. It is commonly used in shared-services or regional HR models where HR Partners support entire organizational branches.

Therefore, the correct and Workday-verified answer is that HR Partners must approve termination events for employees in their assigned organization and all subordinate organizations.

The correct answer is C – Position Management.

In Workday, Position Management is the staffing model used when an organization needs to track headcount, vacancies, and time-to-fill for each position individually. Each position represents a distinct job slot that must be filled by a worker, providing clear visibility into when a position is open, filled, or closed.

This model is ideal for organizations that require detailed tracking of resource allocation, workforce planning, and recruiting metrics such as “time to fill”. Because each position must exist before a hire can occur, Workday automatically records the date the position is opened and the date it is filled, allowing accurate reporting on recruitment cycle times.

In contrast, Job Management groups workers under jobs rather than individual positions and does not provide vacancy-level tracking, making it unsuitable for time-to-fill analysis.

In Workday, field-level visibility during business processes—especially for self-service events—is controlled through Optional Fields configuration, not security domains. The Request One-Time Payment for Self process has its own optional field settings that allow administrators to show or hide specific fields for employees.

To prevent employees from modifying sensitive options such as Gross Up and Send to Payroll, administrators must configure Optional Fields specifically for the Request One-Time Payment for Self process and hide those checkboxes. This preserves the self-service capability while enforcing governance and preventing unintended financial impact.

Removing security domain access would block employees from initiating the process entirely, which does not meet the requirement. Configuring optional fields on the administrator-driven Request One-Time Payment process would not affect self-service behavior.

Therefore, the correct and precise solution is to configure Optional Fields for Request One-Time Payment for Self and hide the fields, making option D correct.

In Workday HCM, organizations such as cost centers are assigned to workers during hire and job change events. To ensure data accuracy and governance, Workday provides two key configuration controls for organizations: default organizations and allowed organizations. While default organizations prepopulate values, only allowed organizations control which values are selectable.

To limit the list of cost centers that managers can select during the hiring process, you must configure the allowed organization on the supervisory organization. This configuration defines the specific cost centers that are valid for workers hired into that supervisory organization. By restricting the allowed cost centers, Workday ensures managers can select only from an approved list, preventing incorrect or unauthorized cost center assignments.

Configuring a default organization—whether on the supervisory organization or from the position—only sets an initial value. It does not prevent the manager from changing the cost center to another valid option. Therefore, options B and C do not meet the requirement to limit selection. Option D is incorrect because job profiles are not used to control organizational assignments such as cost centers; they define job architecture, not financial or organizational governance.

From a Workday Pro HCM best-practice perspective, allowed organizations are the primary mechanism for enforcing organizational assignment rules at the time of hire. Applying this configuration at the supervisory organization level ensures consistent cost center usage for all workers hired into that organization while still allowing flexibility across different parts of the enterprise.

Therefore, the correct and fully Workday-verified answer is Configure the allowed organization on the supervisory organization.

In Workday, total base pay calculations are controlled by grade profiles, specifically through the Base Pay Elements field. This field determines which compensation elements are included when evaluating base pay ranges such as minimum, midpoint, and maximum.

In this scenario, employees are correctly assigned a period salary plan with the Brazil Holiday Pay compensation element, but that element is not included in total base pay. This indicates that the grade profiles for Brazil do not currently include this element in the Base Pay Elements configuration.

Compensation bases are used for plan calculations and validations, not for defining base pay composition. Compensation elements must be included in the grade profile to affect base pay ranges. Salary plans and period salary plans reference compensation elements but do not control base pay inclusion.

By adding Brazil Holiday Pay to the Base Pay Elements field on the Brazil grade profiles, Workday will include the 13th-month payment in total base pay calculations for employees in Brazil.

Therefore, option D is the correct and Workday-supported solution.

The correct answer is D – HR partners need to be able to view documents but only those assigned to the Performance Review category.

Segment-based security groups are used in Workday to grant access to specific subsets of data within a domain, based on defined “segments” such as document category, location, or other defined dimensions. Unlike role-based or organization-based groups, segment-based security provides fine-grained access control that limits visibility within a specific domain.

In this case, the HR partners should only be able to view documents categorized under “Performance Review”, not all employee documents. A segment-based group is ideal here because it restricts access based on the document category segment defined in the Document Review domain.