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

A unit salary plan in Workday is specifically designed to support compensation that varies based on a measurable unit of output , such as miles driven, items produced, or— in this case— kilometers flown . This plan type allows compensation to scale proportionally with the quantity of units, making it ideal for roles where pay increases directly with activity or performance volume.

For airplane pilots, compensation based on kilometers flown is not a fixed allowance or a one-time payment. Instead, it represents variable earnings tied to ongoing work output , which aligns exactly with the purpose of a unit salary plan. Workday allows administrators to define a rate per unit , and the system can calculate estimated compensation by multiplying the rate by the expected number of units. This calculated amount can then be displayed in offer letters, providing transparency and clarity to candidates.

A period salary plan is used for fixed salaries distributed over defined pay periods and cannot model variable, unit-driven earnings. A one-time payment plan is intended for bonuses or ad-hoc payments and does not support ongoing estimation. A unit-based allowance plan is typically used for reimbursements or allowances, not base compensation tied to work output.

Therefore, the unit salary plan is the correct choice for modeling and presenting estimated wages based on kilometers flown, making option B the correct answer.

The correct answer is D – User-based.

User-based security groups are manually assigned to specific users and are typically used for administrative or audit-level access . They can be configured as unconstrained , granting full visibility across all organizations and data in the tenant.

For users responsible for security oversight or auditing , a user-based group (such as Security Administrator or Security Auditor ) is appropriate. This group can be assigned to the necessary domain and business process security policies that control access to security reports and configuration data.

Other group types (e.g., role-based or segment-based) depend on organizational context and cannot provide unrestricted system-wide visibility, making a user-based group the correct option for full security monitoring.

The correct answer is Filter .

In Workday reporting, filters are used to narrow down report results based on specific data criteria, such as location, supervisory organization, or worker type. By applying a filter condition to include only workers whose location equals Toronto or Montreal , the report output dynamically restricts data to meet those parameters.

Filters can be added to both custom and advanced reports and can include multiple conditions combined with logical operators (AND/OR). Unlike Sort (which arranges results in a specific order) or Share (which defines who can view or edit the report), a Filter directly controls which data rows appear in the report output, ensuring that only relevant workers are displayed.

In Workday, when an employee qualifies for multiple compensation bases , the system determines the primary compensation basis using the ranking value . The rule is straightforward and consistently tested: the compensation basis with the lowest numerical ranking takes precedence .

In this scenario, the employee is eligible for three ranked compensation bases:

Management Compensation (ranking 1 )

International Compensation (ranking 2)

Sales Compensation (ranking 3)

Because ranking 1 has the highest priority, Management Compensation is selected as the employee’s primary compensation basis. This primary basis is used for compensation calculations, validations, guideline enforcement, and display during compensation events.

Delivered bases such as Total Base Pay are irrelevant unless explicitly eligible and ranked. Workday does not average or combine ranked bases—only one primary basis is selected based on ranking precedence.

Therefore, Management Compensation will display as the primary compensation basis, making option C correct.

In Workday HCM, job profiles are core configuration objects that define the general characteristics of work performed in the organization. Their primary function is to standardize and describe roles consistently across the enterprise, regardless of whether the organization uses job management , position management , or a hybrid staffing model. Job profiles capture high-level attributes such as job title, job family, job family group, management level, job category, worker type eligibility, and other structural elements that describe the nature of the work.

The correct statement is that job profiles include the general characteristics of position . In position management organizations, every position is associated with a job profile, which supplies these shared characteristics. This ensures that multiple positions performing the same type of work are aligned to the same job definition, supporting consistency in staffing, compensation, reporting, and organizational analysis.

Option A is incorrect because job profiles are not optional; they are foundational to staffing and compensation processes. Option B is inaccurate because job profiles are not assigned only to jobs—they are used across both job management and position management models. Option D is also incorrect because while job profiles are required for creating positions, that statement describes a dependency, not the function of job profiles.

From a Workday Pro HCM best-practice perspective, job profiles serve as the single source of truth for job architecture , enabling scalable workforce management, consistent reporting, and effective compensation governance. They allow organizations to evolve roles over time while maintaining structural alignment across workers and positions.

Therefore, the correct and Workday-verified function of job profiles is that they include the general characteristics of positions .

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.

Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core – Organizations Configuration Guide 2023R2):

When creating a new supervisory organization , Workday allows the subordinate organization to inherit key structural and configuration attributes from its superior organization. These inherited elements include:

Visibility (A): Determines who can view the organization and its members, inherited to maintain consistent access control.

Organization Assignments (B): Such as company, cost center, region, and custom organizations, ensuring hierarchical alignment.

Staffing Model (D): The staffing model (Position Management or Job Management) is inherited to ensure consistency in hiring and staffing control.

Subtype (C) and Name (E) are not inherited; they must be defined at the time of creation. Subtype determines the organization’s classification, while the name uniquely identifies it.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations and Hierarchy Configuration Guide (2023R2), Section: “Creating Subordinate Supervisory Organizations.”

" Subordinate supervisory organizations inherit configuration from their superior supervisory organization, including attributes such as the staffing model, organization assignments, and visibility settings. This ensures consistency and reduces administrative overhead. "

– Workday Module 2 Binder, Supervisory Organizations Section

In Workday HCM, selecting the correct security group type is critical to ensuring users have appropriate access while maintaining strong governance and data security. When HR representatives need access to workers within a specific supervisory organization , such as Sales, the most appropriate solution is a role-based constrained security group .

A role-based constrained security group limits access based on organizational assignment , such as a supervisory organization and its subordinate organizations. This means HR representatives assigned to this role will only have access to workers who belong to the Sales supervisory organization hierarchy. This targeted access aligns with the principle of least privilege and is a core Workday Pro HCM security best practice.

Organization-based (Unconstrained) and role-based (Unconstrained) security groups grant access across all organizations in the tenant. These options would provide broader access than required and could expose sensitive worker data outside the Sales organization. Therefore, they are not appropriate when access should be limited to a specific supervisory organization.

User-based security groups assign access to individual users , not organizational roles. While useful for exceptions or administrators, user-based groups do not scale well and require ongoing maintenance when users change roles or responsibilities.

By using a role-based constrained security group , access automatically follows the role assignment on the Sales supervisory organization. If HR representatives change or new HR staff are assigned, access is updated without reconfiguring security for individual users.

From a Workday Pro HCM perspective, role-based constrained security groups provide the optimal balance of flexibility, control, and scalability. Therefore, the correct and Workday-verified answer is Role-based (Constrained) .

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.

As per the Workday Module 2 Binder:

“Validation condition rules are used in approval steps to determine whether the step should occur or be skipped based on specific conditions.”

– Workday Module 2 Binder, Business Processes Section

Situation: In a business process in Workday, organizations want certain steps (like approvals) to occur only if specific conditions are met—for example, skipping approval if the amount is under a certain threshold.

Task: Implement logic that dynamically controls the flow of a business process based on conditions.

Action: You apply a validation condition rule within an approval step . This rule evaluates defined criteria and determines if the step should be executed or bypassed.

Result: This enhances automation, improves efficiency, and reduces manual intervention in workflow execution.

Hence, approval steps are the specific step type in which validation condition rules can be added.