Workday-Pro-HCM-Core Exam Dumps - Workday Human Capital Management Questions and Answers

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.

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.

In Workday, when an organization needs to change only compensation details —such as base salary—without affecting job, position, organization, or other worker attributes, the correct task is Request Compensation Change . This task is specifically designed for standalone compensation updates .

The Transfer, Promote or Change Job task is used when job-related attributes change and should not be used for compensation-only updates. Request Grade Change modifies the employee’s compensation grade but does not directly update salary amounts. Request One-Time Payment is limited to non-recurring payments and does not affect base pay.

Request Compensation Change ensures:

No job or organizational data is altered

Proper compensation validations and guidelines apply

Accurate audit tracking and approvals are enforced

Therefore, Request Compensation Change is the correct and Workday-recommended task for ad hoc salary changes.

The correct answer is C – Maintain Staffing Models.

In Workday, the Maintain Staffing Models task enables administrators to update or modify the staffing model assignments for multiple supervisory organizations simultaneously. This task provides a consolidated interface to review which organizations use Position Management or Job Management , and allows bulk updates where necessary.

While the Edit Staffing Model task is used to change the staffing model for a single supervisory organization, Maintain Staffing Models is the correct and efficient method for multi-org updates—especially during tenant configuration or large-scale reorganizations.

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.

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, access to reports—whether standard or custom—is controlled by domain security permissions . Domain security governs what data a user can see or interact with, and different permission levels determine whether the user can only view data or also create, update, or retrieve it through integrations.

The Location Directory is a Workday-delivered standard report that displays location-related data, such as business sites, addresses, and associated attributes. Because this report is read-only and does not involve creating or updating data, the HR Auditor security group only needs View permission on the relevant Location domain to run the report successfully.

The View permission allows users to see data and run reports that reference that domain. It is the minimum permission required for reporting access and aligns with the typical responsibilities of an HR Auditor, whose role is to review and validate data rather than modify it.

The other permissions are not appropriate in this context. Modify and Put permissions would allow changes to location data, which exceeds auditor responsibilities and violates the principle of least privilege. Get permission is typically used for web services and integrations and does not apply to interactive report execution in the Workday user interface.

From a Workday Pro HCM security best-practice standpoint, assigning only View access ensures auditors can perform their oversight duties without risking unintended data changes. This approach supports compliance, audit integrity, and strong internal controls.

Therefore, the correct and Workday-verified domain permission required for an HR Auditor to run the Location Directory report is View .

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 HCM, job management supervisory organizations rely on hiring restrictions to control which workers can be hired. These restrictions can be set at the organization level to govern hiring eligibility based on attributes such as job profile, location, worker type, and time type. When an organization anticipates hiring workers across multiple locations and multiple job profiles , Workday Pro HCM best practices emphasize configuring hiring restrictions to allow the greatest flexibility while avoiding unnecessary administrative maintenance.

Selecting the No Job Restrictions checkbox when setting the organization’s hiring restrictions is the most effective approach in this scenario. This option removes job-based limitations, allowing the organization to hire workers into any job profile and location without repeatedly updating restrictions. It is especially appropriate for new or growing organizations where hiring needs are expected to change frequently.

The other options introduce inefficiency and risk. Updating each position’s hiring restrictions is not applicable in job management, as job management does not use discrete position objects. Selecting all locations and job profiles during position creation is both impractical and restrictive, as it requires constant updates when new jobs or locations are added. Updating the organization’s hiring restrictions every time a new worker is hired increases administrative overhead and raises the likelihood of errors or delayed hires.

From a Workday Pro HCM perspective, the No Job Restrictions setting is designed specifically to support broad, flexible hiring needs while still allowing downstream processes—such as recruiting, compensation, and reporting—to function correctly. Therefore, choosing this option ensures maximum hiring flexibility and aligns with Workday’s recommended configuration approach for job management organizations.

In Workday HCM, a Job Profile stores the common job architecture attributes that describe the nature and level of work performed. Management Level is one of the fields maintained on the Job Profile because it classifies the organizational level of the role, such as individual contributor, manager, director, or executive. This value supports staffing, reporting, compensation eligibility, business process routing, and job catalog consistency. Location is not stored as a fixed Job Profile attribute because workers or positions using the same Job Profile may exist in different locations. Compensation Package is not the correct answer because compensation eligibility is configured through compensation plans, grades, eligibility rules, and related compensation structures rather than as a core Job Profile field in this context. Worker Type is also not stored on the Job Profile; it is selected or constrained during staffing and position/hiring restrictions. Therefore, Management Level is the field stored on the Job Profile. Reference topics: Staffing, Job Profiles, Job Profile Attributes, and Job Architecture configuration.