Workday-Pro-HCM-Core Workday Pro HCM Core Certification Exam Questions and Answers

The correct answer is C – Compensation Grade.

In Workday, the Compensation Grade field within the Job Profile configuration defines the default salary range or pay range for that profile. When a worker is hired, transferred, or promoted into a job that references a compensation grade, Workday automatically defaults the associated minimum, midpoint, and maximum pay ranges into the staffing or compensation event.

The Compensation Grade is typically tied to Compensation Grade Profiles , which further refine pay ranges based on factors such as location, job level, or eligibility rules . This ensures pay consistency and compliance with internal compensation structures.

Other fields such as Job Code or Job Classification are used primarily for external reporting or regulatory mapping (e.g., EEO, SOC codes) and do not control compensation defaults.

In Workday HCM, compensation elements serve as the critical link between compensation plans in HCM and earnings codes in Payroll. Their primary purpose is to ensure that compensation entered in Workday is correctly interpreted, calculated, and paid through payroll processing. Without compensation elements, payroll systems would not be able to distinguish how different types of compensation—such as base salary, allowances, or bonuses—should be treated for taxation, deductions, and reporting.

Compensation elements are applied to three key components within the compensation framework: plans, grades, and grade profiles . When assigned to compensation plans, elements define how the plan’s compensation is paid. When applied to grades and grade profiles, they support consistency and scalability by ensuring that compensation tied to a specific grade structure flows correctly to payroll, regardless of the job or position.

Compensation elements are not applied to eligibility rules, benefit deductions, or compensation packages. Eligibility rules determine who can receive compensation, not how it is paid. Benefit deductions are managed within benefits configuration, and packages are used primarily for grouping plans, not payroll integration.

By standardizing the payroll linkage across plans, grades, and grade profiles, compensation elements provide flexibility, global consistency, and accurate payroll results. This makes option C the correct answer according to Workday Pro HCM compensation and payroll integration best practices.

By default, when compensation is preconfigured on a job requisition , Workday carries those values forward into the Offer event without re-evaluating eligibility. This can cause issues when attributes such as location change, because eligibility rules tied to country, location, or other organizational attributes may no longer be valid.

The tenant-level setting Run Eligibility Rules when there is Requisition Compensation , found in Edit Tenant Setup – HCM , instructs Workday to re-run compensation eligibility rules during the Offer process , even if compensation has already defaulted from the requisition. This ensures that compensation elements are validated against the candidate’s current attributes, including location.

The eligibility performance enhancement setting affects processing speed only and does not change evaluation behavior. Guideline defaulting settings impact guideline recalculation, not eligibility. Security policy edits do not control eligibility rule execution.

Therefore, enabling Run Eligibility Rules when there is Requisition Compensation is the correct configuration, making option A correct.

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.

In Workday HCM, condition rules are used within business process definitions to control when steps start, continue, or stop executing. When working with consolidated approvals , it is common to define stopping points so that once a required level of approval is met—such as approval by a vice president—the approval chain does not continue unnecessarily.

To stop a consolidated approval chain after a vice president approves the task, you must use an Exit condition rule . Exit conditions are evaluated after a step completes and determine whether the business process should continue to subsequent steps or stop processing additional steps. When the exit condition evaluates to true, Workday exits the process flow at that point.

This behavior makes exit conditions ideal for scenarios where hierarchical or role-based approval chains should end once a certain authority level has approved. In this case, once the vice president approval is completed, the exit condition prevents additional approvers from receiving the task.

The other condition types do not meet this requirement. Entry conditions control whether a step starts at all but do not stop a process once it has begun. Validation conditions are used to enforce data accuracy and prevent submission if requirements are not met. While Running conditions are evaluated while a step is in progress and are typically used to cancel or reroute steps if circumstances change.

From a Workday Pro HCM best-practice perspective, exit condition rules are the correct and recommended method for ending approval chains early when business requirements are satisfied. Therefore, the correct and Workday-verified answer is Exit

In Workday, condition rules determine whether a step executes, routes, or triggers based on defined criteria such as job attributes, location, or organization. There are two primary ways to create or associate condition rules directly from a business process step:

Create Condition Rule (Option C) – allows a user to define a new condition rule directly from within the step configuration screen. This opens the condition rule editor where criteria can be defined using Workday attributes.

Maintain Step Conditions (Option D) – provides the option to assign existing condition rules or create new ones for the selected step. This is often used to ensure that certain steps run only when specific business conditions are met.

Options A and B are incorrect:

Maintain Advanced Routing Restrictions (A) is related to security routing and worktag-based participant logic, not condition rule creation.

Maintain Step Delay (B) controls timing (delaying execution by hours or days), unrelated to conditions.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework and Condition Rule Configuration Guide (2023R2) – Sections: “Creating and Maintaining Condition Rules” and “Step-Level Configuration.”

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.

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

In Workday, the ability to share a report depends on a user or group’s security access to the report’s data source and data source filters . This ensures that only authorized individuals can view the report’s content, even if they have the link or the report is shared with them directly.

Data sources define what underlying information a report can pull (e.g., Worker, Position, Organization). Security policies tied to those data sources control who can access or view specific data fields. Therefore, even if a report is shared broadly, users can only see results their security permissions allow.

Options A, B, and D are incorrect because Workday security doesn’t evaluate “business reasons” or “tags” for access — it enforces data-source–based controls. Field-level access is governed by the domain security policy within the data source.

Reference (Paraphrased Source):

Workday Pro HCM Core – Reporting Configuration Guide (2023R2), Section: “Report Sharing and Security Dependencies.”

In Workday, configurable compensation bases allow organizations to control how compensation plans relate to one another and to enforce limits or proportions within a total compensation structure. The Manage Basis Total option is specifically designed to impose constraints on how much certain plan types can contribute relative to the overall compensation basis.

In this scenario, the business requirement is to ensure that salary plans do not exceed 50% of the total compensation for Indian employees. This requirement is achieved by enabling Manage Basis Total on the Total Cost (India) compensation basis and setting a maximum percentage of 50 for salary plans . This configuration enforces the rule automatically during compensation proposals and validations.

Changing the ranking of the compensation basis has no impact on percentage enforcement; rankings only determine precedence when multiple bases apply. Fixed compensation bases do not support proportional controls and would remove flexibility. Removing retirement plans would alter the total compensation calculation but would not guarantee the 50% salary cap.

Therefore, configuring Manage Basis Total with a salary plan maximum of 50% is the correct and Workday-recommended solution to enforce this business rule, making option B the correct answer.

The correct answer is C – Hiring Restrictions.

When a supervisory organization uses the Job Management staffing model (which has no limit on the number of jobs that can be filled), hiring is controlled through Hiring Restrictions rather than position management.

The Edit Hiring Restrictions business process must be configured before initiating hires to define:

Worker Type (Employee or Contingent Worker)

Location

Job Family and Job Profile

Time Type (Full-time or Part-time)

These restrictions determine what roles and worker types can be staffed in that supervisory organization. Unlike Position Management , there is no need to create or approve individual positions beforehand.

The Dynamic Display for Compensation Plan Sections setting allows Workday to intelligently show or hide compensation plan sections during compensation events based on plan eligibility and security permissions of the user performing the transaction.

When enabled, Workday evaluates:

Whether the worker is eligible for a plan

Whether the user has security access to view or edit the plan

This results in a cleaner, more relevant user experience and reduces errors during compensation proposals.

Segment security controls access but does not dynamically hide sections. Eligibility performance enhancements affect rule evaluation speed, not UI behavior. Hiding Total Salary & Allowances is cosmetic and does not control plan section logic.

Therefore, option B is the correct and recommended configuration.

In Workday HCM, compensation grades are a core component of the job and grade framework , which belongs to organizational configuration rather than transactional staffing activities. The primary purpose of assigning a compensation grade to a job profile is to define and default the appropriate pay range —minimum, midpoint, and maximum—for employees performing that job.

When a compensation grade is attached to a job profile, Workday uses the associated grade profiles (which may vary by location, currency, or frequency) to automatically determine the salary or hourly range during hire, job change, and compensation change events. This ensures consistency, internal equity, and alignment with market data across the organization.

Compensation grades do not control compensation frequency, bonus eligibility, or target compensation amounts. Frequency is defined at the compensation plan level, bonus eligibility is governed by eligibility rules, and target compensation is typically managed through compensation plans and guidelines.

By separating job architecture (grades) from transactional compensation plans , Workday enables scalable global compensation structures that are easy to maintain and audit. Therefore, the correct and primary purpose of assigning a compensation grade to a job profile is to default the appropriate pay range , making option C correct.

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, compensation entered during the Offer event only carries forward to the Hire event if it is part of the compensation package associated with the job or position. Compensation packages define which plans—such as salary plans, allowance plans, and one-time payment plans —are eligible to flow through staffing events.

If a signing bonus is entered during Offer but not included in the compensation package, Workday treats it as an isolated entry that does not persist into Hire. This behavior is by design to ensure consistency and control over compensation structures.

Security policies, approval steps, and subprocess configuration do not control whether compensation carries forward between Offer and Hire. The determining factor is inclusion in the compensation package.

Therefore, to ensure the signing bonus carries forward, the Signing Bonus one-time payment plan must be included in the compensation package , making option A correct.

In Workday HCM, location usage determines how a location is used across business processes such as staffing, reporting, payroll, and compliance. Each location can have one or more usage types, and selecting the correct usage is critical to ensure accurate worker records and downstream processing.

The location usage that defines a worker’s physical work location is Business Site . A Business Site represents the actual, physical place where a worker performs their job duties, such as an office, plant, store, or warehouse. This usage is foundational in Workday and is commonly associated with employment details, including work address, tax reporting, payroll processing, and regulatory compliance. When a worker is hired or changes jobs, the Business Site is typically the location tied directly to the worker’s position or job assignment.

The other options do not fulfill this purpose. Campus is used to group multiple business sites together, often for reporting or organizational purposes, but it does not directly represent where an individual worker physically works. Job Posting locations are used exclusively in recruiting to indicate where a job is advertised and may not reflect the worker’s actual work location. Business Asset is used to associate physical assets, such as equipment or facilities, with a location and is not intended for worker assignment.

From a Workday Pro HCM perspective, correctly identifying the Business Site as the worker’s physical location ensures consistency across staffing, payroll, benefits, and compliance processes. It supports accurate reporting and enables Workday to apply location-based rules and calculations correctly.

Therefore, the correct and Workday-verified answer is Business Site .

In Workday HCM, it is essential to distinguish between domain security and business process security , as each controls different aspects of system access. Domain security governs data visibility , such as whether a user can view compensation information or run reports. Business process security, on the other hand, controls transactional actions , such as initiating or completing tasks like Create Compensation Package.

In this scenario, the worker is able to run the Compensation Package report , which indicates they have permission to view compensation-related data. However, they cannot access the Create Compensation Package task , which is a transactional action within a business process. This clearly shows the worker has view-only access to the domain but does not have business process initiation permissions.

The correct permission type is View on a domain security policy . This level of access allows users to view data and run reports associated with that domain, but it does not allow them to modify data or initiate related business processes.

Option A is incorrect because Initiate permissions on a business process security policy would allow the worker to start the Create Compensation Package task. Option B is incorrect because View and Modify domain access would allow data changes, which is not supported by the sce nario. Option C is incorrect because View All on a business process security policy would relate to visibility within business processes, not report execution.

From a Workday Pro HCM security design perspective, this scenario demonstrates the separation of duties principle: reporting access is granted through domain security, while transactional authority is tightly controlled through business process security. Therefore, the correct and Workday-verified answer is View on a domain security policy .

Compensation steps in Workday are designed to support structured, automatic pay progression based on time, service, or measurable criteria . To meet the requirement in this scenario, the configuration must enforce two separate conditions before the employee progresses to the next step: completion of 12 months of duration and accumulation of 400 worked hours .

In Workday, duration defines the minimum amount of time an employee must remain on a compensation step before becoming eligible for progression. Setting the duration to 12 months ensures the employee cannot advance earlier than one year of service. However, duration alone is insufficient when additional criteria—such as hours worked—must also be met.

This is where step progression rules are used. A step progression rule allows administrators to define measurable thresholds, such as hours worked, that must be satisfied before progression occurs. By configuring a rule that counts 400 hours worked , Workday ensures that employees who do not meet the hours requirement will not advance, even if they have completed 12 months.

Options A and B only configure one condition and do not satisfy the full requirement. Option C applies to initial step assignment, not progression eligibility.

Therefore, combining a 12-month duration with a step progression rule based on hours worked is the correct and Workday-supported configuration, making option D the correct answer.

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

The Reorganization Event in Workday is used to group and manage multiple organization changes that share a common effective date . This functionality ensures that all changes—such as reorganizing reporting structures, moving subordinates, or reassigning workers—are executed simultaneously as part of a controlled event.

It helps maintain organizational data integrity and ensures that all related updates occur in a coordinated and auditable way.

Options A, B, and C describe other organization functions:

A: Reporting on membership is done through standard reports.

B: Role inheritance occurs automatically via supervisory structure, not through reorganization events.

C: Maintaining settings is done through “Edit Organization” tasks.

Therefore, D correctly captures the purpose of a reorganization event.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Reorganization Events and Effective Dating.”

In Workday, position management and job management represent two different staffing models. In a position management organization, a worker is assigned to a specific position (a distinct headcount-controlled object with attributes like availability date, restrictions, and position details). When you initiate a job change that transfers the worker into a job management organization , the worker is no longer staffed against a position-managed role. Instead, the worker becomes staffed in a job management context, where staffing is generally based on the job/role and organization headcount rules rather than a discrete position object.

Because the worker is leaving a position-managed assignment , Workday treats the original position as vacated . The position itself typically remains in the position management organization (it does not “move” into job management), and it does not automatically cease to exist simply because the incumbent moved. As a result, the most accurate description is that the prior position becomes open and may be available for backfill , depending on how your tenant is configured (for example, whether the position is frozen, closed, or otherwise restricted by staffing rules or business process conditions). This aligns with Workday’s standard behavior: a worker transfer out of a filled position leaves an open position that can be recruited for and filled through normal staffing activities.

To meet seasonal demand, you need to hire cashiers, retail specialists, and customer service representatives.

What hiring restriction do you set to meet this need?

A. Job Family Group

B. Job Profile

C. Job Description

D. Job Category

Answer: A

In Workday HCM, hiring restrictions are used in job management organizations to control what types of jobs can be hired into a supervisory organization. Selecting the correct level of restriction is critical to balancing flexibility with governance. In this scenario, the organization needs to hire multiple distinct roles —cashiers, retail specialists, and customer service representatives—to address seasonal demand. These roles are different job profiles, but they typically belong to the same broader functional area within the organization.

The most appropriate hiring restriction to meet this requirement is the Job Family Group . A job family group allows organizations to group related job families under a common functional umbrella, such as Retail Operations or Customer Support. By setting the hiring restriction at the job family group level, the organization can hire multiple job profiles that fall within that group without needing to define each job profile individually. This provides flexibility, speeds up hiring during peak seasonal periods, and reduces administrative effort.

Restricting hiring by Job Profile would be too limiting because it allows only a single, specific role to be hired, which does not meet the need for multiple types of workers. Job Description is not used as a hiring restriction object in Workday staffing models, and Job Category is primarily used for reporting and classification purposes rather than controlling staffing eligibility.

Therefore, using a Job Family Group hiring restriction aligns with Workday Pro HCM best practices by enabling efficient, scalable hiring across multiple related roles while maintaining appropriate organizational control.

In Workday HCM, the Create Position task is used within the position management staffing model to establish discrete position records that represent headcount within an organization. One of the key fields in this task is Number of Openings , which is often misunderstood. This field does not indicate how many workers can occupy a single position; instead, it determines how many separate position records Workday will create at one time.

When you enter a value greater than one in the Number of Openings field, Workday automatically creates multiple positions with identical attributes . These attributes include job profile, location, time type, supervisory organization, and other position characteristics defined during the Create Position process. This functionality is designed to streamline administrative work when an organization needs several similar positions, such as during large-scale hiring or seasonal staffing initiatives.

Each position created is its own unique position object in the system, with its own position ID, lifecycle, and staffing history, even though the characteristics are the same. This ensures accurate tracking of headcount, budgeting, and reporting while minimizing repetitive data entry.

The field does not allow multiple workers to be placed into the same position, as position management enforces one worker per position at any given time. It also does not create multiple requisitions automatically; requisitions are created through a separate recruiting process. Additionally, it cannot be used to create positions with different characteristics, as all positions generated from a single Create Position event share the same configuration.

Therefore, the correct and Workday-verified purpose of the Number of Openings field is to create multiple positions with the same characteristics efficiently and consistently.

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 .

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.

In Workday HCM, compensation grades define pay structures, while grade profiles allow those grades to be localized by attributes such as country, location, currency, or frequency. This separation is intentional and supports scalable global job architecture.

The best practice for configuring location-specific pay ranges for the same job profile is to create one compensation grade and then define multiple grade profiles , each with its own eligibility rules and localized pay ranges. In this scenario, separate grade profiles would be created for London, New York, and Milan, each reflecting local market conditions, currencies, and regulations.

Creating multiple compensation grades would unnecessarily fragment the job architecture and increase maintenance effort. Eligibility rules alone are not sufficient because pay ranges differ by location and currency. Grade profiles are specifically designed to solve this use case.

Once the grade profiles are created, the single compensation grade is attached to the Software Engineer job profile , and Workday automatically selects the correct grade profile based on employee location.

This approach ensures consistency, reduces configuration complexity, and aligns with Workday Pro HCM organizational design best practices.

In Workday, the ability to assign compensation plans—regardless of employee eligibility—is controlled by security domains , not by business process steps or guidelines. The Worker Data: Compensation Plan Type security domain governs access to specific types of compensation plans, such as allowance plans, salary plans, or one-time payments.

When a user (such as a compensation partner) has broader access through this domain, they can assign compensation plans even when eligibility rules are not met . This is commonly granted to advanced compensation roles to allow exceptions, corrections, or special cases during approvals.

Manager roles are typically restricted by eligibility, which is why the manager can only assign the car allowance. The compensation partner’s elevated security allows them to override eligibility.

The “Select Any Compensation Package” option controls package selection, not plan-level overrides. Guidelines and manager domains do not grant override capability.

Therefore, the correct security domain is Worker Data: Compensation Plan Type , making option D correct.

In Workday HCM, advanced custom reports offer powerful filtering capabilities, but certain configuration options intentionally limit available fields to ensure optimal system performance. One such option is the Optimized for Performance checkbox. When this option is selected, Workday restricts filters to indexed fields only .

Indexed fields are pre-optimized by Workday to support faster query execution and efficient data retrieval, especially in large tenants with significant data volumes. By limiting filters to indexed fields, Workday ensures that reports run quickly and reliably without placing excessive load on the system. This design aligns with Workday’s performance and scalability standards.

When Optimized for Performance is enabled, non-indexed fields are excluded from filter selection because filtering on those fields could result in long-running queries or degraded system performance. This is expected and intended behavior, not a limitation of the report writer or data source.

The other options are incorrect. Using an indexed data source does not, by itself, restrict filters to indexed fields. The Temporary Report checkbox controls report persistence and availability, not filter behavior. A standard data source can still allow non-indexed fields unless performance optimization is explicitly enabled.

From a Workday Pro HCM best-practice perspective, the Optimized for Performance option should be used when reports are expected to run frequently, support dashboards, or be shared widely. While it reduces filter flexibility, it significantly improves execution efficiency and reliability.

Therefore, the correct and Workday-verified reason you can only select indexed fields is that the Optimized for Performance checkbox is selected .

In Workday HCM, proration based on an employee’s scheduled hours (such as part-time versus full-time workers) is controlled through the Apply FTE% configuration within a salary plan. FTE (Full-Time Equivalent) represents the ratio of an employee’s scheduled hours to the standard full-time schedule, and Workday uses this value to proportionally calculate compensation.

When the Apply FTE% box is checked on a salary plan, Workday automatically prorates the compensation amount based on the employee’s FTE. For example, if a salary plan amount is defined as $100,000 annually and the employee is working at 50% FTE, Workday will calculate and pay $50,000. This ensures fair and consistent compensation aligned with scheduled working hours.

Eligibility rules determine who can receive a plan, not how much they receive. The Exclude from Merit option only controls whether a plan is included in merit processes and has no impact on proration. Compensation elements connect compensation to payroll earnings but do not control proration logic.

Therefore, checking the Apply FTE% box is the correct and Workday-recommended method for configuring proration based on scheduled hours, making option D the correct answer.

In Workday, step-based grades use progression logic to control movement from one step to the next . Conditional logic is applied only to steps that an employee progresses through , not to the final step in the sequence.

In this scenario, the business requirement is to allow progression only if the employee does not have a poor performance rating (value 1) . This condition must be evaluated when the employee attempts to move from:

Step 1 → Step 2

Step 2 → Step 3

There is no progression after Step 3 , so conditional logic is not required for that step.

Conditional logic for step progression is configured at the step level , not at the grade profile level. The logic must explicitly evaluate that the performance review rating is not equal to selection list value 1 .

Options B and D are incorrect because grade profiles do not control step-level progression logic. Option C incorrectly allows progression only when performance is poor, which is the opposite of the requirement.

Therefore, conditional logic should be applied to Step 1 and Step 2 , evaluating that the rating is not in selection list value 1 , making Option A the correct answer.

In Workday staffing, position restrictions define which values are allowed when a worker is hired into a position. In this scenario, Worker Type is restricted to Employee, but Worker Subtype is blank. A blank optional restriction does not mean the manager cannot select a value; it means the value is not restricted by that specific field. Because Worker Type is restricted to Employee, the available subtypes must be valid subtypes under the Employee worker type. The manager can therefore select any Worker Subtype that belongs to Employee, such as Regular or another configured employee subtype. The answer is not Employee because Employee is a worker type, not a worker subtype. Contingent Worker is incorrect because it is a different worker type and is excluded by the Employee restriction. Any subtype of the Contingent Worker worker type is also incorrect because contingent worker subtypes are not valid when the position is restricted to Employee. The restriction framework narrows subtype choices through the selected worker type. Therefore, any subtype of the Employee Worker Type is correct. Reference topics: Staffing, Position Restrictions, Worker Type, Worker Subtype, and position-based hiring controls.

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, the Effective Date controls when the compensation change is legally and payroll-effective , while the Employee Visibility Date determines when employees can see the change in Workday.

In this scenario:

The increase must be effective March 1 for equity and payroll accuracy.

Employees should not see the change until after March 20 , when managers communicate it.

By setting:

Effective Date = March 1

Employee Visibility Date = March 21

Workday ensures the increase is included in payroll and historical records while remaining hidden from employees until the specified visibility date.

Using the transaction date or delaying the effective date would create payroll inaccuracies. Setting both dates to March 21 would make the increase effective too late.

Therefore, option D is the correct and compliant solution.

In Workday, pay rate type (Salaried or Hourly) is a foundational attribute used across staffing, compensation, and eligibility logic. When a salary plan’s eligibility rule evaluates pay rate type , that value must be consistently defined at the job profile level to avoid mismatches or incorrect eligibility results.

Assigning pay rate types directly to job profiles ensures that employees hired into those roles inherit the correct classification automatically. This reduces reliance on manual data entry and prevents discrepancies during hire, job change, or compensation events.

Assigning salary plans to job profiles does not guarantee accurate eligibility if the pay rate type itself is not consistently defined. Modifying the eligibility rule weakens the control logic. Job requisitions may temporarily hold pay rate types, but job profiles are the source of truth for long-term configuration.

Therefore, assigning pay rate types to job profiles is the correct and Workday-recommended next step, making option D correct.

The correct answer is A – Role-Based (Constrained) can approve compensation of workers they are assigned to support. User-Based can approve compensation of all workers.

In Workday, Role-Based (Constrained) security groups restrict access based on an assigned organization or supervisory hierarchy. Members of a constrained role (such as Compensation Partner ) can perform actions—like approving compensation changes—only for workers within their assigned supervisory organizations.

Conversely, User-Based security groups are not tied to an organization unless specifically constrained, and typically have unconstrained, tenant-wide access . When both security groups have access to the same domain or business process (e.g., “Approve Compensation Change”), the User-Based group can approve changes for all workers, while the Role-Based (Constrained) group’s access is limited by their assigned scope.

In Workday, plan profile eligibility rules control which employees qualify for a compensation plan during evaluation events , such as Hire, Job Change, or Compensation Change. When eligibility rules are updated, Workday does not immediately retroactively remove compensation . Instead, the system evaluates eligibility at the next compensation-related business process .

In this scenario, Sales employees were explicitly removed from the Sales / Australia plan profile eligibility. As a result, those employees no longer qualify for the allowance. During the next eligible event—such as a job change or compensation review—Workday will automatically remove the allowance from employees who no longer meet the eligibility criteria.

Workday does not generate system errors due to eligibility rule changes, nor does it automatically enroll unrelated populations. Additionally, allowances are not mass-added or removed immediately without a triggering event unless a mass operation is run.

Therefore, the correct outcome is that Sales employees will automatically be removed from the plan , making option D correct.

Revenue and expense-related financial transactions in Workday are normally tracked through financial organization structures such as cost centers. When a business needs to group members of multiple organizations for reporting on revenue and expense activity, a Cost Center Hierarchy is the correct organization type. Cost centers identify where costs, expenses, and financial accountability are assigned. A hierarchy allows multiple cost centers to be rolled up for consolidated reporting, financial analysis, budgeting, and management review. A Region Hierarchy can group geographic regions, but geography is not the primary driver for revenue and expense reporting in this scenario. A Supervisory Organization Hierarchy is used for worker reporting relationships and staffing, not financial transaction grouping. A Location Hierarchy groups physical locations and may support workforce or facilities reporting, but it is not the appropriate structure for tracking financial transactions by revenue and expense. Therefore, the correct organization type is Cost Center Hierarchy. Reference topics: Organizations, Cost Centers, Cost Center Hierarchies, Organization Assignments, and financial transaction reporting.

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, when security access must follow a position rather than a specific individual, the correct solution is to use a role-based constrained security group . This is especially important when the position is vacant, as assigning security to a person would not meet the requirement and would require reconfiguration once the role is filled.

The first step is to run the Maintain Assignable Roles task. This task enables administrators to define which role-based security groups can be assigned to organizations. Without completing this step, the role cannot be attached to an organization or used in an organizational context.

Next, a role-based constrained security group is created. Constrained security groups restrict access based on organizational assignments, allowing the role to support a specific organization and its subordinate organizations. This aligns precisely with the requirement for the HR Generalist position to support a new organization hierarchy while maintaining proper security boundaries.

Finally, the position is assigned to the new role on the organization. Assigning the role to the position—not the worker—ensures that security access automatically transfers to whoever occupies the HR Generalist position in the future. This supports scalability, reduces administrative effort, and follows Workday’s security best practices.

The other options are incorrect because user-based security groups require an incumbent and do not support vacant positions, while unconstrained security groups grant overly broad tenant-wide access. Activating pending security policy changes alone does not satisfy the requirement to scope access by organization.

Therefore, Option A is the only configuration that is accurate, scalable, and fully aligned with Workday Pro HCM security design principles.

In Workday HCM, access to direct reports’ data is primarily driven by managerial relationships within the supervisory organization hierarchy. The Maintain Assignable Roles task is used to define how role-based security groups can be assigned and how access is derived from organizational relationships.

The setting that grants managers access to their direct reports’ data is Is Leader . When a role-based security group is configured with the Is Leader designation, Workday evaluates the worker’s role as a manager (leader) of a supervisory organization. This enables leader-based security access, allowing managers to view and act on data for workers who report directly to them (and, depending on configuration, potentially their subordinates).

This setting is foundational for manager self-service and manager insights, such as viewing team profiles, compensation, performance data, and other worker-related information tied to reporting relationships. Without the Is Leader setting, Workday would not recognize the user as having leader-based authority over the workers in the supervisory organization.

The other options do not provide this access. Enabled for Location Hierarchy grants access based on location structure, not reporting relationships. Is Supporting is used for roles like HR Partners or Finance Partners who support an organization but are not managers. Enabled for Supervisory Organization controls where a role can be assigned, not whether it confers manager-level access.

From a Workday Pro HCM best-practice perspective, Is Leader is the critical configuration that ensures managers can view and manage their direct reports’ data appropriately. Therefore, the correct and Workday-verified answer is Is Leader .

The correct task to assign someone as a leader of a new organization is " Assign Roles. " In Workday, each organization (e.g., Cost Center, Company, Supervisory Organization) can have one or more roles assigned to manage that organization’s transactions and activities. These roles might include Manager, HR Partner, Finance Partner, etc.

When creating a new organization or modifying an existing one, the “Assign Roles” task is used to designate the individuals who will hold specific responsibilities over that organization. This action ensures proper workflow routing, approvals, and visibility across business processes like Staffing, Compensation, and Financials. This is essential for cross-functional reporting and financial oversight.

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.

Job families and job family groups provide a controlled hierarchy for organizing job profiles. In this structure, a job family is associated with a job family group, and the relationship supports consistent reporting and classification of jobs across the tenant. The correct statement is that you can associate a job family with only one job family group. This maintains a clean parent-child relationship and prevents the same job family from rolling up inconsistently into multiple higher-level groupings. The option stating that a job profile belongs to only one job family group is not the best configuration statement because job profiles are organized through job families rather than directly through family groups in this context. The option that a job family can be associated with multiple job family groups conflicts with the single-parent rollup behavior needed for consistent hierarchy reporting. The option that a job profile can be associated into only one job family is also not the correct statement being tested here. The key rule is the relationship between job family and job family group. Therefore, option A is correct. Reference topics: Staffing, Job Profiles, Job Families, Job Family Groups, and job architecture hierarchy configuration.

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

A Consolidated Approval Chain Step allows multiple approval actions within a business process to be combined into a single, streamlined approval task. However, this step must be the final step before the completion step in a business process.

If the Consolidated Approval Chain appears after the completion step , Workday will trigger a critical error because the step order violates the BP framework rules. The system expects the consolidated approval to act as the last step to ensure that all approvals are received before the event finalizes.

Therefore, Option C is correct — a critical error occurs because the Consolidated Approval Chain Step must immediately precede the completion step, not follow it.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Consolidated Approval Chains and Step Sequence Rules.”

The correct answer is D – Change Job.

The Change Job business process is used in Workday to update a worker’s job-related details within the same employment record. It applies to both Job Management and Position Management staffing models.

Common use cases for Change Job include:

Promotions or demotions (e.g., Business Process Analyst → Senior Business Process Analyst),

Transfers to a different supervisory organization,

Lateral moves between departments, or

Changes to job profile, location, or business title.

The process maintains continuity of employment while updating the job attributes. In contrast, Hire Employee is for new hires, and Propose Compensation Change only adjusts pay without changing the job attributes.

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

The Org Chart Report in Workday provides a visual hierarchical diagram displaying superior and subordinate supervisory organizations . It allows users to navigate through organizational layers, view reporting relationships, and understand the structure of the workforce within each supervisory organization.

This report is especially useful for HR and managers to visualize team structures, identify open positions, and confirm reporting lines.

Option A ( All Jobs Report ) lists worker job data, not organizational hierarchy.

Option B ( Reorganization Report ) provides details about reorganization events, not a visual hierarchy.

Option C ( Workday Touchpoints Kit ) is a set of integration and configuration tools, not a report.

Thus, Org Chart Report is the correct option, as it visually represents the hierarchical structure of supervisory organizations and their relationships.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Viewing Organizational Hierarchies and Using the Org Chart Report.”

In Workday, the Review Step within a business process is specifically designed to enable a user to review, edit, and approve information that was submitted by the initiator. This step allows designated participants to view the transaction details, make permissible edits, and approve or send it back for correction. It serves as an intermediate checkpoint before final approval or completion, ensuring data accuracy and compliance with policy.

By contrast, the Approval Step (Option C) only permits approval or denial — it does not allow data modification. The Consolidated Approval Step (Option B) groups multiple approval steps for simplification but also lacks edit functionality. The Integration Step (Option D) is used for system integrations and automated data transfers, not for user data review.

Thus, the Review Step uniquely provides both review and edit capabilities, which makes it ideal for validating and refining information early in the process lifecycle.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2) – Section: “Step Types and Participant Actions” and “Review Step Configuration.”

Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core – Reporting and Analytics Guide, 2023R2):

In Workday Reporting, to organize or arrange the display of report results based on specific criteria — such as the Supervisory Organization Name — you use the Sort configuration option.

Sorting determines the order in which records appear when the report is executed. In this case, by sorting on the Supervisory Organization Name field, all workers will be grouped together under their respective organization, making the output intuitive and structured for analysis.

Option B ( Share ) controls who has access to the report.

Option C ( Filter ) limits which records are included in the results.

Option D ( Subfilter ) refines filter logic but does not control display order.

Thus, Sort is the correct configuration feature to organize report results for any user running the report.

Reference (Paraphrased Source):

Workday Pro HCM Core – Reporting Configuration and Design Guide (2023R2), Section: “Sorting, Grouping, and Display Options in Custom Reports.”