The Employee Compensation Audit report in Workday is designed to identify discrepancies between eligibility and actual plan assignment . It compares whether employees should be assigned to compensation plans based on eligibility rules versus whether they are currently assigned.

In this scenario, the Sales Analyst job profile was newly added to the Sales job family . As a result, Sales Analysts now meet the eligibility criteria for the Sales allowance plan. However, unless a compensation event (such as Hire, Job Change, or Compensation Change) has occurred, the allowance plan may not yet be assigned .

When an employee is eligible for a plan but not currently assigned , Workday flags this discrepancy under Unassigned Eligible Compensation Components . This column highlights compensation plans that should be assigned based on current eligibility but are missing.

Assigned Ineligible Compensation Components would only apply if the employee had the plan but no longer qualified. The plan will appear on the report because eligibility exists.

Therefore, the correct column is Unassigned Eligible Compensation Components , making option A correct.

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, Workday restricts users to entering one one-time payment per event when the reason and effective date are the same. To support scenarios where multiple one-time payments are required—such as bonuses, awards, or stipends paid on different dates—the tenant-level setting Enable Multiple One-Time Payments must be enabled.

This configuration is found in Edit Tenant Setup – HCM and allows users to enter multiple one-time payment rows within the same event, even when the effective date and reason are identical.

Business process steps, eligibility rules, and UI help text do not control the system’s ability to accept multiple one-time payments in a single transaction. Without this tenant setting enabled, Workday enforces a single-payment limitation.

Therefore, enabling Enable Multiple One-Time Payments is required, making option A correct.

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.

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.

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, 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.

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 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 HCM, period salary plans are specifically designed to support compensation structures where base pay is distributed over a defined number of periods that may not align with standard monthly or annual salary conventions. This is particularly important for countries such as Italy, where statutory or customary compensation practices include additional salary payments , often referred to as the 13th and 14th month salaries . These additional payments result in employees receiving more than 12 months of pay within a year.

A period salary plan allows organizations to define the number of salary periods per year , such as 12, 13, 14, or other values like 14.9, without altering the employee’s annualized base pay. This ensures compliance with local labor laws while maintaining consistent reporting, budgeting, and payroll calculations. Workday then prorates or distributes the annual amount appropriately across the defined periods.

Other plan types do not support this requirement. A salary plan assumes a standard annual salary without accommodating extra pay periods. Hourly plans are designed for workers paid based on time worked, and unit salary plans are used when pay is based on output or units produced, neither of which align with Italy’s statutory base pay structure.

Therefore, a period salary plan is the correct and Workday-recommended solution for handling additional months of base pay in countries with localized pay practices, making option A the correct answer.