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

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.

In Workday HCM, approval authority is granted through business process security policies , not by assigning individual users directly to steps within a business process definition. Business process definitions determine what steps exist, while business process security policies determine who can perform actions on those steps.

When an employee is promoted, compensation changes are handled through the Propose Compensation Change business process. Even though the promotion itself occurs within the Change Job business process, the approval of compensation changes is controlled separately. This separation allows organizations to assign different approvers for job changes and compensation decisions, supporting strong governance and segregation of duties.

To grant a user the ability to approve compensation changes related to promotions, the user must be assigned to a security group that has permission to perform the Approve action on the Propose Compensation Change business process security policy . Once the user is a member of that security group and the changes are activated, Workday will route compensation approval tasks to them when applicable.

Options B and D are incorrect because users are never assigned directly to individual steps within a business process definition. Step routing is driven by security groups, not individual users. Option A is incorrect because the Change Job business process controls job-related actions, not compensation approval.

From a Workday Pro HCM best-practice standpoint, always grant approval access by updating the appropriate business process security policy and assigning users to the correct security groups . This ensures scalable, auditable, and role-based access control.

Therefore, the correct and Workday-verified answer is Assign the user to a security group with permissions to the Approve action on the Propose Compensation Change business process security policy .

In Workday HCM, job profiles are foundational configuration objects that define the structure of work across the organization, including job responsibilities, job family, job family group, management level, worker type eligibility, and other job architecture attributes. Because job profiles are shared across many workers, positions, and business processes, Workday strictly controls how they are updated to preserve data integrity and reporting accuracy.

The correct task used to update existing job profiles is Maintain Job Profile . This task is specifically designed to allow authorized users to modify job profile attributes in a controlled and auditable way. Using Maintain Job Profile ensures that updates—such as changes to job titles, job family assignments, compensation eligibility, or reporting attributes—are applied consistently across the system wherever the job profile is referenced.

The Create Job Profile task is only used to create new job profiles and cannot be used to update existing ones. Edit Job Profile is not a standard Workday-delivered task for job profile maintenance and is therefore not a valid option. View Job Profile provides read-only access and does not allow any changes to be made.

From a Workday Pro HCM best-practice perspective, separating creation, maintenance, and viewing tasks ensures proper governance, security role control, and auditability. The Maintain Job Profile task also supports effective job architecture management by enabling organizations to evolve roles over time without disrupting worker assignments or downstream processes.

Therefore, the correct and Workday-verified task used to update job profiles is Maintain Job Profile .

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

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

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

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

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

When a Change Job event includes a compensation impact, Workday triggers the Propose Compensation Change subprocess. This subprocess allows users to review and update compensation plans, amounts, and guidelines as part of the job change.

Request Compensation Change is a standalone process used when compensation changes occur without a job change. Propose Compensation Offer and Propose Compensation Hire are tied to recruiting and hiring events, not internal transfers.

The Propose Compensation Change process ensures that compensation updates are evaluated with proper eligibility rules, guidelines, approvals, and audit tracking within the context of the job change.

Therefore, option D is the correct answer.

The correct way to localize allowance amounts in Workday without impacting other populations is through the use of plan profiles . Plan profiles allow administrators to define country-specific or location-specific values using eligibility rules, ensuring that employees automatically receive the correct amount during hire and other staffing events.

In this scenario, adding a new plan profile for Ireland with a value of €90 EUR ensures that employees hired in Ireland automatically receive the correct allowance. This approach preserves the existing default value of $100 USD for employees in the US and avoids unintended downstream impacts.

Updating the default value would affect all employees who do not meet profile eligibility, including US employees. Allowance Plan Adjustments are used to update existing assignments, not to control defaulting logic during hire. Manual compensation changes are inefficient, error-prone, and contradict Workday best practices for scalable configuration.

Therefore, adding a new allowance plan profile for Ireland is the correct, controlled, and Workday-recommended solution, making option C the correct answer.

The Compensation Rule Assignment report is designed to provide a configuration-level view of compensation components and the eligibility rules assigned to them . This report lists all compensation plans—such as salary plans, allowance plans, bonus plans, and one-time payments—that reference an eligibility rule.

This report is especially useful for:

Impact analysis before modifying eligibility rules

Auditing which compensation components rely on shared rules

Understanding eligibility dependencies across compensation configuration

The Employee Compensation Audit focuses on worker assignments, not configuration. Compensation Changes tracks transactional history. Compensation Spreadsheets are manual tools and do not reflect rule usage.

Therefore, the correct report for identifying all compensation components using eligibility rules is Compensation Rule Assignment , making option B correct.

Default compensation on a job requisition allows organizations to predefine compensation plans and values that automatically flow into the Offer event. The primary advantage is consistency —every candidate hired from the same requisition starts with the same baseline compensation configuration.

This ensures fairness, reduces recruiter error, and accelerates the offer process by minimizing manual data entry. Default compensation on requisitions is especially valuable when hiring multiple candidates for the same role, location, and level.

Position-based compensation is configured separately and applies regardless of requisition. Viewing eligible plans is unrelated to default compensation. While employees hired into a position may share compensation, requisition defaulting specifically governs applicant and offer behavior .

Therefore, option B is the correct answer.

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 .

The Gross Up option on a one-time payment plan instructs Workday to calculate and add additional earnings so that the employee receives a net amount equal to the target value , after applicable taxes are withheld. This is commonly used for bonuses, relocation payments, or awards where the employer agrees to cover the tax impact.

When Gross Up is enabled, Workday works with Payroll to determine the required gross amount that results in the desired net payment. Taxes are always applied by payroll regardless of this setting; the checkbox simply controls whether Workday compensates for them.

Gross Up does not require manual adjustment, nor does it only display tax information. It is an automated calculation designed to meet net-pay commitments.

Therefore, option A is the correct answer.

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.

In Workday HCM, it is critical to understand the distinction between job management and position management , as worker movement and vacancy behavior differ significantly between the two staffing models. In a job management organization , workers are hired into jobs , not into discrete position objects. Jobs in this model do not represent fixed headcount slots; instead, they are simply descriptive attributes assigned to workers.

When a worker in a job management organization retires, the worker’s job assignment ends with the worker . Because job management does not maintain a separate position record, there is no concept of a job remaining open, being frozen, or awaiting backfill. Once the worker exits the or ganization, the job itself effectively no longer exists unless another worker is hired into the same job profile through a separate hiring event.

Option A is incorrect because leaving a role open for backfill applies only to position management , where positions are persistent objects that can remain vacant and be refilled. Option B is invalid, as Workday does not support overlapping jobs in this manner. Option D is also incorrect because freezing applies to positions, not jobs.

From a Workday Pro HCM best-practice perspective, this behavior reinforces why job management is often used for organizations that require greater flexibility , such as high-volume or seasonal hiring. There is no headcount lock tied to individual jobs, and staffing levels are managed through hiring rules and organizational limits rather than position vacancies.

Therefore, the correct and Workday-verified outcome is that the job no longer exists once the worker retires in a job management organization.

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 .

In Workday, eligibility rules are evaluated sequentially , and performance optimization is achieved by placing the most restrictive condition first . This minimizes the number of records evaluated in subsequent conditions.

In this scenario:

Only 5 employees meet the job family criterion

50 employees meet the organization criterion

To optimize performance, the rule should first evaluate job family , which immediately narrows the population to a smaller subset. The organization criterion is then evaluated against this reduced population.

Placing organizational membership first would cause unnecessary evaluation of a much larger group, negatively impacting performance. Workday does not automatically sequence eligibility conditions, and removing criteria would violate the business requirement.

Therefore, job family should precede organizational membership , making option D correct.

Workday’s Business Process Notification functionality enables administrators to configure custom notifications that are automatically sent to users when specific BP events occur. The correct statement is that you can use text and fields in the body of the notification message (Option B).

Notification templates support the insertion of business process fields , allowing dynamic content such as worker names, event types, or effective dates to be automatically populated in the message. This helps personalize communications and provide clear, actionable context.

Option A is incorrect because notifications can be sent to both internal users and external participants (such as vendors or contingent workers) if appropriately configured.

Option C is incorrect — you can configure multiple status triggers (e.g., In Progress, Denied, Completed).

Option D is incorrect since notification triggers are predefined by Workday , and while you can configure their messages and recipients, you cannot create entirely new trigger types.

Therefore, the main strength of this feature lies in its customizable content , dynamic field integration , and multi-status trigger support .

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Business Process Notifications,” and “Custom Message Configuration.”

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, allowance plans include a No Override configuration option that prevents users from manually changing the plan amount during staffing or compensation events. When this checkbox is selected, the plan amount is strictly controlled by the plan default or plan profile value.

Even if a recruiter has appropriate security and the candidate is eligible for the allowance, the presence of No Override enforces compensation governance and prevents deviations from defined policy.

Ineligibility would prevent the plan from appearing at all, and multiple plan profiles would cause defaulting issues—not override restrictions. If the plan were not included in the compensation package, it would not be visible.

Therefore, the recruiter cannot change the amount because the No Override checkbox is selected, making option A correct.

In Workday, period salary plans are specifically designed to support countries where employees are legally entitled to additional salary payments , such as a 13th or 14th month salary. These plans allow organizations to define compensation based on a number of salary periods , rather than assuming a standard 12-month structure.

By configuring a period salary plan with an additional month , Workday can correctly calculate and distribute base pay across the required number of periods while still maintaining accurate annualized compensation values. This approach ensures compliance with local legislation while preserving consistent reporting and budgeting.

Percent-based merit plans are used for increases and do not address structural pay requirements. Allowance plans are not considered base pay and are not appropriate for statutory salary obligations. One-time payment plans are ad hoc and do not satisfy recurring legislative requirements.

Period salary plans integrate seamlessly with payroll, compensation bases, and grade profiles, making them the correct and compliant solution for legislated additional pay months.

Therefore, option A is the correct answer.

In Workday HCM, business process definitions control how transactions such as hires, job changes, terminations, and approvals flow through the system. Each business process consists of multiple steps, including initiation, approvals, notifications, and system actions. Among these, the completion step plays a critical and often misunderstood role.

The primary purpose of the completion step is to indicate when Workday saves, finalizes, and commits the transaction data to the system. Until the completion step is reached, information entered during the business process remains in a pending state and is not fully written to the database. Once the completion step executes, the transaction becomes effective, and all related changes—such as worker status updates, organization assignments, compensation changes, or security updates—are officially applied.

Option A is incorrect because automatic completion of steps is controlled by step type and routing rules, not by the completion step itself. Option B is incorrect because exit condition rules are evaluated at various points during the process to determine whether steps should be skipped, not specifically at completion. Option D is unrelated, as the completion step does not control when specific roles receive approvals.

From a Workday Pro HCM perspective, the completion step is essential for ensuring data integrity and transactional accuracy . It marks the point at which the business process is considered finished and all downstream effects—such as reporting, payroll, benefits eligibility, and security changes—can occur reliably.

Therefore, the correct and Workday-verified purpose of the completion step is to indicate when Workday saves or commits information .

In Workday HCM, supervisory organizations form a hierarchical structure that governs reporting relationships, staffing behavior, and headcount control. When a subordinate supervisory organization is created, certain attributes may be inherited from the superior organization to ensure consistency and operational alignment across the hierarchy.

The field that inherits from the superior supervisory organization is the Staffing Model . Workday enforces this inheritance because the staffing model—either position management or job management —determines how workers are staffed, how headcount is controlled, and which staffing rules apply. Allowing subordinate organizations to inherit the staffing model ensures consistent staffing behavior throughout the supervisory hierarchy and prevents configuration conflicts.

The other options do not inherit from the superior organization. Organization Subtype is explicitly selected during creation and can differ between supervisory organizations. Availability Date is defined individually for each organization and controls when it becomes active. Organization Code is a unique identifier and must be manually entered; it does not inherit to avoid duplication.

From a Workday Pro HCM best-practice perspective, enforcing staffing model inheritance simplifies organization management and supports accurate headcount and staffing governance. It also ensures that subordinate organizations cannot inadvertently introduce incompatible staffing configurations within the same reporting structure.

Therefore, the correct and Workday-verified answer is Staffing Model , as it is the field that inherits from the superior supervisory organization.

In Workday HCM, consolidated approvals are used within business process definitions to reduce approval fatigue by grouping multiple related approval steps into a single task for the approver. This is especially useful for senior leaders, such as HR executives, who otherwise might receive several separate approval tasks for the same transaction—such as hire details, compensation, and organization assignments.

When you add a Consolidated Approval step to a business process, that step alone does not define what information is presented to the approver. To complete the configuration and make the consolidated approval functional, you must also complete the Configure Consolidated Template task. This task defines the approval layout and content , specifying which sections, fields, and business process steps are grouped and displayed together in the single approval task.

Without configuring the consolidated template, Workday does not know how to combine the approval content, and the consolidation will not behave as intended. The template controls the user experience for the approver and ensures all required information is reviewed in one place.

The other options do not meet this requirement. Maintain Step Conditions controls when a step runs but does not define consolidation behavior. Configure Consolidated Approval is not a delivered standalone task; consolidation is driven by the step and its template. Maintain Step Delay controls timing, not task grouping.

From a Workday Pro HCM best-practice perspective, adding a consolidated approval step must always be paired with Configure Consolidated Template to complete the setup. Therefore, the correct and Workday-verified answer is Configure Consolidated Template .

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.

Single Assignment in organization role assignments identifies which assignee should be treated as the single representative for reporting and integration output when more than one person may hold a role. Organizations can have role assignments such as manager, HR partner, finance partner, or other support roles. In some cases, multiple workers may be assigned to the same role or related role configuration, but downstream reports and integrations may require one named value. Single Assignment provides that designated value for report fields and integrations. It does not determine the manager who appears on the organizational chart; org charts are primarily driven by supervisory organization and manager relationships. It also does not select the most senior manager automatically, nor does it decide who receives business process tasks. Business process routing is controlled by role-based security, routing rules, condition rules, and business process configuration. The term Single Assignment is specifically about identifying the single role assignment value used when Workday must display or export one assignee. Therefore, option B is correct. Reference topics: Organizations, Assign Roles, Role Assignments, Single Assignment, reporting fields, and integration output behavior.

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

When creating a new supervisory organization that should inherit attributes such as staffing model, company, and cost center from an existing organization, you use the Create Subordinate task.

This task creates the new subordinate organization directly under a superior supervisory organization. It automatically copies inherited settings such as visibility, organization assignments, and staffing model, ensuring hierarchical alignment and simplifying setup.

Option B ( Create Supervisory Organization ) creates a brand-new top-level supervisory org without inheritance.

Option A ( Assign Roles ) only assigns role-based permissions after creation.

Option C ( Assign Included Organizations ) is used for related org relationships, not for hierarchical creation.

Thus, Create Subordinate is the correct task when the new org must inherit settings from a superior one.

Reference (Paraphrased Source):

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

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, role-based (constrained) security groups control access to business pro cesses and data based on an individual’s organizational assignments. The Access Rights to Organizations setting determines which organizations—and therefore which workers—fall within the scope of responsibility for users assigned to that security role.

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

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

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

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

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

The correct answer is D – Edit Hiring Restrictions.

In this scenario, the supervisory organization uses the Job Management staffing model (“no limit on the number of jobs”). Because there are no discrete positions, you control staffing limits through Hiring Restrictions rather than position-level restrictions.

The Edit Hiring Restrictions task allows administrators to specify criteria such as:

Worker Type (Employee, Contingent Worker)

Location

Job Family / Job Profile

Time Type (Full-time, Part-time)

This ensures that hiring aligns with organizational policy even when positions are not individually managed. For organizations using Position Management , the corresponding task would be Edit Position Restrictions instead.

The correct answer is C – Offers greater control on each position open within an organization.

The Position Management staffing model is designed for organizations that require precise headcount control and visibility into staffing levels. Each position represents a discrete role that must be created, approved, and tracked before a hire occurs.

This model provides a high degree of control over:

Vacancies and filled positions

Position attributes (FTE, job profile, location, etc.)

Time-to-fill metrics for open roles

Because every hire is linked to a specific position, administrators can effectively monitor workforce planning, budgeting, and resource allocation.

In Workday HCM, user-based security groups grant access to specific individuals rather than to positions or organizations. These security groups are designed to provide permissions directly to a Workday user account , making them appropriate when access should not change automatically based on position changes or organizational movement.

To include a new hire in an existing user-based security group, you must associate the group with the individual’s Workday Account . A Workday Account represents the system login identity for a worker and is the object that security groups reference when assigning user-based access. Once the new hire’s Workday Account is created as part of the Hire business process, the account can be added to the user-based security group, immediately granting the associated permissions.

The other options are incorrect because they apply to different security models. Worker Position is used for role-based security groups, where access follows the position rather than the individual. Worker Location and Job Profile are organizational and job architecture attributes and are not valid association objects for user-based security groups.

From a Workday Pro HCM best-practice perspective, user-based security groups should be used sparingly, typically for exceptions, administrators, or roles that require access independent of organizational structure. Because access does not automatically transfer when a worker changes jobs or positions, administrators must manually manage membership by adding or removing Workday Accounts as needed.

Therefore, the correct and Workday-verified way to include a new hire in an existing user-based security group is to associate the Workday Account with the security group.

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, compensation packages are used to group compensation plans that are presented and assigned during staffing events , such as Hire or Change Job. These packages are designed to include plans that are transactionally assigned and visible during compensation proposals.

A one-time payment plan is explicitly supported within compensation packages and is commonly used for sign-on bonuses, relocation payments, or other ad hoc payments offered during hiring.

Calculated plans and retirement plans are not assigned directly through compensation packages. Calculated plans are system-derived and depend on other plans, while retirement plans are managed through Benefits configuration. Future payment plans are handled separately and are not eligible for inclusion in compensation packages.

Therefore, the only valid option is One-time payment plan , making option D 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 report is View Security for Securable Item .

In Workday, each task, report, or domain is considered a securable item that is protected by one or more security policies . When an administrator needs to identify which policy governs access to a particular task—such as Change My Photo —they use the View Security for Securable Item report.

This report provides detailed insight into:

The domain or business process associated with the securable item,

The related security policies ,

Which security groups currently have access, and

The permissions (view, modify, initiate, etc.) assigned.

Using this report helps determine the correct security domain to update when granting or revoking access.

A Workday standard report refers to a delivered, predefined report that is built and maintained by Workday. These reports are available out-of-the-box and are designed to support common and essential business processes and analytics across HCM, Finance, and other Workday modules. Users can run standard reports immediately without needing to create them from scratch, and they often serve as a base for custom reporting when further refinement or filtering is necessary.

Workday provides hundreds of these reports covering a broad range of functionality—examples include " Employee Roster " , " All Positions " , " Business Process Transactions " , etc. These reports are typically domain-secured , which means access to them is governed by user security and data access permissions.

As per the Workday Pro HCM Reporting Study Guide, standard reports are also known as " delivered reports " and often include pre-configured prompts and formatting that align with Workday best practices.

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 HCM, grade profiles define how total base pay is calculated and evaluated for employees by specifying which compensation elements are included in the base pay range. The Base Pay Elements field on the grade profile is the authoritative configuration that determines which compensation elements contribute to total base pay minimums, midpoints, and maximums.

In this scenario, Mexico employees already have a grade profile that includes Base Pay and 13th Month compensation elements. To ensure the family allowance is included in total base pay—and therefore considered when validating pay ranges and equity—the family allowance compensation element must be explicitly added to the Base Pay Elements field on the Mexico grade profiles.

Compensation element groups are used primarily for reporting and do not affect how base pay is calculated. EIBs are data load tools and do not control structural compensation logic. Compensation bases are used for plan calculations and eligibility, not for defining what counts toward base pay in a grade profile.

By updating the Base Pay Elements field, Workday automatically includes the family allowance in base pay comparisons, validations, and reporting for Mexico employees. This is the correct and Workday-supported approach.

In Workday HCM, hiring restrictions define the allowable values a manager can select when hiring into a position or job management organization. These restrictions are enforced strictly to ensure governance, compliance, and consistency in staffing decisions. When a value is explicitly restricted, only the values defined in the restriction are valid during the hire process.

In this scenario, the position has hiring restrictions configured for Location , allowing only New York and San Francisco . Although other attributes such as time type are not restricted and therefore remain flexible, location is explicitly constrained. When the manager attempts to hire a worker with the location set to London , Workday prevents the transaction from continuing because London is not included in the allowed location values for the position.

The job profile requirement is met, as both the position and the hire specify Staff HR Representative , and the worker type also aligns with the restriction of Employee . The Time Type: Full Time does not cause an issue because time type is not restricted, meaning any valid time type can be selected.

Option A is incorrect because managers are allowed to specify values beyond the restricted fields, as long as they comply with any existing restrictions. Option B is unrelated to the scenario, as the issue is not related to hire reason configuration. Option D is incorrect because unrestricted fields do not block hiring.

From a Workday Pro HCM perspective, this scenario reinforces the importance of reviewing position hiring restrictions carefully. Any attempt to select a value outside a defined restriction—such as an unauthorized location—will result in the hire being blocked. Therefore, the correct answer is the manager cannot select London because it is not in the list of hiring restrictions for location .

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 .

To ensure the HR Partner reviews and updates a new hire’s Company and Cost Center , you add the Change Organization Assignments action step to the Hire business process.

This action allows the HR Partner (or assigned role) to validate and modify organizational assignments, such as Company, Cost Center, Region, or Location, before the Hire event is finalized. It is typically positioned after the Review Employee Hire step to confirm that all organization-level data aligns with the new worker’s role and supervisory org defaults.

Option A ( Review Employee Hire ) is a completion-type review step and does not update organization data.

Option B ( Onboarding Setup ) prepares onboarding tasks, not organizational details.

Option C ( Edit Workday Account ) deals with account credentials and system access.

Thus, Change Organization Assignments is the correct step for updating or confirming company and cost center information during the hiring process.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Adding and Configuring Organization Assignment Steps in Staffing BPs.”

Compensation elements in Workday serve as the critical integration point between HCM compensation plans and Payroll earnings . To ensure that a car allowance plan is paid correctly through payroll, the compensation element must be created before it can be assigned to the allowance plan.

The correct process begins with the Maintain Compensation Elements task, which is used to define the element itself, including its payroll characteristics and earning behavior. Once the compensation element is created, it can then be selected directly when creating the car allowance plan , ensuring that the allowance is properly mapped to payroll.

Compensation Element Groups are used only to logically organize elements and do not create elements themselves. Additionally, administrators do not need to manually add elements to allowance plans through Edit Tenant Setup. Instead, elements are associated directly at the plan level during plan creation or configuration.

Options A, B, and C introduce unnecessary or incorrect steps that are not supported by Workday configuration best practices.

Therefore, the correct and efficient approach is to create the compensation element first using Maintain Compensation Elements, then create the allowance plan with that element , making option D the correct answer.

Workday provides the Remove Compensation Plans from Employees task as the most efficient and scalable method for removing an existing compensation plan from a large population. This task allows administrators to select a compensation eligibility rule that identifies all employees currently assigned to the plan and remove it in bulk.

Marking a plan as Inactive only prevents future assignments; it does not remove the plan from employees who are already assigned. Using Change Job events would require individual transactions and is not operationally efficient. The Request Bonus Payment web service is used for issuing bonus payments, not removing bonus plan assignments.

The removal task ensures:

Clean and auditable removal

No unintended job or worker data changes

Correct end-dating of plan assignments

Therefore, option A is the correct and Workday-recommended approach.

In Workday HCM, it is common to configure organization-specific business process definitions , especially for high-impact processes such as Termination , where approval steps and routing may vary by supervisory organization. When multiple definitions exist for the same business process, administrators need a reliable way to determine which definition applies to which supervisory organization .

The correct report for this purpose is Business Process Configuration Options . This Workday-delivered report provides a consolidated view of all business process definitions for a given business process and clearly shows the organization-specific assignments . It displays which definition is active, the organizations it applies to, and the precedence rules used by Workday when evaluating which definition to apply during a transaction.

Workday evaluates business process definitions in a hierarchical order, typically starting with the most specific organization and moving up the supervisory hierarchy. The Business Process Configuration Options report allows administrators to validate this configuration and ensure the correct definition is being triggered for each supervisory organization.

The other options do not meet this requirement. View Business Process Template shows the delivered template structure but does not reflect tenant-specific configuration or organizational applicability. Business Object Details provides metadata about business objects but does not indicate applied business process definitions. Business Process Definitions for Business Object lists definitions associated with a business object but does not clearly map them to specific supervisory organizations.

From a Workday Pro HCM best-practice standpoint, Business Process Configuration Options is the authoritative report for auditing and troubleshooting organization-specific business process behavior. It ensures transparency, supports compliance, and helps administrators maintain accurate and predictable process execution.

Therefore, the correct and Workday-verified answer is Business Process Configuration Options .

Workday provides the Rollout Compensation Plans to Employees task to efficiently assign newly created compensation plans to employees who meet defined eligibility criteria. This task evaluates the eligibility rule attached to the plan and assigns the plan to all qualifying employees in bulk.

Manual approaches such as Request Compensation Change or Change Job events are inefficient and not scalable. The View Compensation Plan Rollout Process task is informational and does not perform assignments.

Using the rollout task ensures consistency, reduces administrative effort, and aligns with Workday best practices for plan deployment.

Therefore, option D is the correct answer.

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 .

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.