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

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 option is Routing Modifier.

In Workday, Routing Modifiers are used to dynamically adjust the routing of approval or review steps within a business process based on contextual changes, such as whether a worker’s supervisory organization or manager is changing. This configuration allows the system to intelligently determine whether the approval or notification step should go to the current manager (before the change) or the proposed manager (after the change).

For example, in the Job Change business process, when an employee is transferring to a new organization or manager, a routing modifier ensures that pre-transfer approvals route to the current manager, while post-transfer approvals route to the new (proposed) manager. This ensures accurate accountability and process flow alignment.

In Workday, custom validations are evaluated based on business process context , including the event type that triggered the process. The Request One-Time Payment and Request One-Time Payment for Self are separate event types, even though they share similar functionality.

To prevent existing validations from running for employee self-service requests, administrators must explicitly exclude the self-service event type within the validation logic. This is done using the Maintain Custom Validations task, where conditions can be added to evaluate the One-Time Payment Event for Self field.

Security changes are not appropriate because the requirement is to allow the process but exclude validations. Optional field configuration does not control validation execution. Creating additional validations does not stop existing ones from firing.

By excluding the One-Time Payment Event for Self event type within the validation, Workday ensures validations continue to apply to administrator-initiated requests but not to employee self-service requests.

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

In Workday HCM, business process templates define the foundational structure of a business process, including the types of steps that are available to be configured. When administrators need to determine which action steps —such as approvals, To Do steps, notifications, integrations, or subprocesses—can be added to a specific business process, the correct Workday-delivered report to use is View Business Process Template .

The View Business Process Template report displays the delivered template for a given business process and outlines all supported step types and actions that Workday allows for that process. Because templates are system-delivered and cannot be modified, this report serves as the authoritative reference for understanding what configuration options are available before adding or modifying steps in a business process definition.

The other options do not fulfill this purpose. Business Process Security Policy for Functional Area and Domain Security Policies for Functional Area focus on security access and permissions, not step availability. Business Process Configuration Options is used to identify which business process definition applies to specific organizations, not which step types can be added.

From a Workday Pro HCM best-practice perspective, administrators should always consult the View Business Process Template report before designing or troubleshooting business process configurations. This ensures that changes align with Workday’s delivered framework and prevents configuration errors caused by attempting to add unsupported step types.

Therefore, the correct and Workday-verified answer is View Business Process Template , as it identifies which action steps can be added to a business process.

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 .

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.

The Employee Compensation Audit report is the primary Workday-delivered report designed to analyze the relationship between compensation eligibility rules and actual plan assignments . It explicitly categorizes compensation components into three critical groupings:

Assigned Eligible Compensation Components

Unassigned Eligible Compensation Components

Assigned Ineligible Compensation Components

This makes the report uniquely suited for identifying configuration gaps, data integrity issues, and compliance risks. Compensation administrators commonly use this report to validate allowance, bonus, and salary plan assignments after eligibility rule changes, organizational updates, or mass events.

Other reports do not provide this level of eligibility comparison. Compensation Summary focuses on current compensation amounts only. Employee Compensation Details by Job Profile provides structural views without eligibility analysis. Compensation Rule Assignment lists rules, not worker-level assignment outcomes.

Therefore, the correct answer is Employee Compensation Audit , making option C 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, 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.

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 HCM, business process security controls which security groups can participate in specific steps within a business process definition. Each step type—such as approval, review, or To Do—requires explicit permission for a security group to be eligible for selection. If a security group does not appear as an option when configuring a review step , it means the group has not been granted permission to act on that type of step.

To resolve this issue, you must update Who Can Do Action Steps in the Business Process . This section of the business process security policy defines which security groups are authorized to perform step-level actions , including review, approve, or to-do actions. Once the appropriate security group is added here and the changes are activated, the group becomes available for selection on the review step.

The other options do not address this requirement. Policy Restrictions control conditional logic and constraints, not step eligibility. Who Can Start the Business Process governs initiation permissions only and does not affect step assignment. Who Can Do Actions on Entire Business Process grants high-level actions such as cancel or rescind but does not authorize participation in individual steps like reviews.

From a Workday Pro HCM best-practice perspective, configuring Who Can Do Action Steps in the Business Process ensures precise control over step participation while maintaining separation of duties. After updating this section, administrators must remember to run Activate Pending Security Policy Changes for the update to take effect.

Therefore, the correct and Workday-verified answer is Who Can Do Action Steps in the Business Process .

In Workday, amount-based allowance plans are used when a fixed monetary value is paid on a recurring basis, independent of base pay, units worked, or expenses incurred. Since the requirement is a flat $500 monthly allowance , an amount-based allowance plan is the most appropriate and straightforward configuration.

This plan type allows administrators to define:

A fixed amount ($500)

A payment frequency (monthly)

An eligibility rule limiting the plan to employees in the Sales job family

Percent-based plans fluctuate with base pay and are not suitable for flat allowances. Reimbursable plans are used for expense reimbursement and require submitted expenses. Unit-based plans are intended for variable, output-driven compensation and would unnecessarily complicate the configuration.

By combining an amount-based allowance plan with a Sales job family eligibility rule , Workday ensures that only eligible employees receive the allowance and that it is paid consistently through payroll.

Therefore, option B is the correct and Workday-recommended solution.

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.

The Employee Compensation Step Progression Audit report identifies employees who are eligible for step progression but have not yet been progressed . When employees appear on this report, it indicates that step progression logic is configured correctly, but the progression has not yet been executed.

The appropriate action is to run the Schedule Automatic Step Progression task. This task evaluates eligibility rules, durations, and progression criteria, and then automatically moves eligible employees to the next compensation step.

Modifying compensation steps or grades is unnecessary and incorrect if progression logic already exists. Change Job events should not be used for step progression, and grade job profile adjustments are unrelated.

Therefore, the correct action is to schedule automatic step progression , making option D correct.

When configuring Business Process Notifications in Workday, administrators can define the recipient based on a specific Workday Account . This allows precise targeting of individuals or security groups (e.g., HR Partner, Manager, or specific role-based accounts) who should receive the notification.

Option D is correct because “Recipient based on Workday Account” ensures the system routes the notification to the appropriate user or group dynamically, based on the context of the business event. This is essential for process transparency and timely action.

Option A ( Sender based on Workday Account ) is incorrect — the sender is system-defined (“Workday Notification”), not configurable by user account.

Option B ( On exit ) and Option C ( Trigger on In Progress ) are not valid notification configuration options; triggers are defined by process status changes such as “Awaiting Action,” “Completed,” or “Denied.”

Reference (Paraphrased Source):

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

The correct report to determine which tasks occur after the Completion Step in a business process is the “Business Process Definitions” report.

In Workday, the Business Process Definitions report provides a comprehensive view of all steps, conditions, and routing rules configured within a specific business process definition. This includes identifying the sequence of steps, whether they occur before or after the completion step, and the associated responsible roles or security groups.

This report is critical for administrators and Workday Pro users to validate workflow sequencing, especially when troubleshooting process behavior or verifying compliance with organizational approval structures. Other reports, such as Business Process Definitions for Business Object, are broader and list all business processes tied to a given object, but they do not detail the post-completion steps.

The correct answer is D – HR partners need to be able to view documents but only those assigned to the Performance Review category.

Segment-based security groups are used in Workday to grant access to specific subsets of data within a domain , based on defined “segments” such as document category, location, or other defined dimensions. Unlike role-based or organization-based groups, segment-based security provides fine-grained access control that limits visibility within a specific domain.

In this case, the HR partners should only be able to view documents categorized under “Performance Review” , not all employee documents. A segment-based group is ideal here because it restricts access based on the document category segment defined in the Document Review domain .

In Workday, when updating allowance plan target amounts, administrators must carefully manage how the change impacts employees who are assigned override amounts . Overrides represent intentional deviations from the plan default, and preserving those differences is often a business requirement.

The Set Up Allowance Plan Adjustment task provides specific options for handling overrides. The option Adjust by Same Amounts for Employees Using Override increases each employee’s allowance by the same delta as the change to the plan default. In this scenario, the default increases from $150 to $200, a difference of $50 . Employees with override amounts will also receive a $50 increase, thereby preserving their original variance from the default.

Selecting Adjust to New Defaults would eliminate the override difference by resetting employees to the new default amount, which contradicts the requirement. Removing or re-rolling out the plan introduces unnecessary disruption and risk.

Therefore, the correct approach is to use the Set Up Allowance Plan Adjustment task and select Adjust by Same Amounts for Employees Using Override , making option D correct.

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 HCM, changes made to security policies , including business process security policies , follow a two-step lifecycle: save and activate . When you edit a business process security policy—such as granting a security group permission to initiate a business process event—those changes are initially saved only . At this stage, the changes exist in the tenant but are not yet active or enforced .

Workday requires administrators to explicitly run the Activate Pending Security Policy Changes task to make any saved security updates effective. This design ensures controlled deployment of security changes and allows administrators to review, bundle, and activate multiple security updates at once. Until activation occurs, users will not experience any change in access or behavior.

Option B is incorrect because Workday does not automatically activate security policy changes. Option A is incorrect because saving a security policy does not generate an error; it simply leaves the changes inactive. Option D is incorrect because Security Evaluation Moments are system-defined events used by Workday to re-evaluate security, but they are not created automatically as a result of editing a policy.

From a Workday Pro HCM best-practice standpoint, administrators should always validate security updates by confirming that pending changes are activated and tested. Failing to activate pending changes is a common reason why expected access updates do not take effect.

Therefore, without further action, the correct and Workday-verified status is that your changes are saved, but not in effect until they are activated.

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, allowance plan profiles are designed to localize plan targets based on eligibility criteria. However, a key rule is that each employee can match only one profile . When an employee meets the eligibility criteria for multiple plan profiles , Workday cannot determine which profile amount to apply and therefore defaults to the plan’s base default value , which in this case is zero.

In this scenario, the plan uses both management level and location as eligibility criteria across multiple profiles. If these criteria overlap and are not mutually exclusive, employees may qualify for more than one profile simultaneously.

Workday does not throw an error in this situation; instead, it applies the plan’s default value to avoid ambiguity. In-progress compensation events do not affect defaulting logic, and having multiple compensation packages does not cause zero defaulting. A missing eligibility rule would apply the default to everyone, not just some employees.

To resolve this issue, administrators must ensure that plan profile eligibility rules are mutually exclusive so that each employee qualifies for exactly one profile.

Therefore, option B is the correct answer.

The correct answer is C – Domain Security Policy.

In Workday, reports and data access are controlled by domain security policies , whereas business process security policies control who can initiate or act on transactions. The Find Workers report accesses worker data fields that are part of the Worker Data: Public, Personal, and Employment domains.

To restrict the HR Partner security group from accessing the Find Workers report, you must update the domain security policy that governs the worker data used by that report. By removing the HR Partner group from the View permissions of the relevant domains, you effectively prevent them from retrieving worker information through that report.

When configuring a business process, if the requirement is to exclude the initiator from completing a step , the correct configuration point is within Maintain Advanced Routing . This task allows administrators to control and customize routing restrictions and participant logic for each step.

Using the Maintain Advanced Routing task, you can define whether the initiator should be included or excluded as a potential assignee for the step. This ensures segregation of duties and compliance — for example, preventing an employee who initiated a Change Job event from approving or reviewing their own transaction.

Options A, B, and D are incorrect:

Maintain Step Conditions (A) is used to apply condition rules to control whether a step executes but not who performs it.

Maintain Step Help-Text (B) is used only to provide user instructions within the BP interface.

Maintain Step Delay (D) controls timing between steps, not participant assignment.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Advanced Routing and Participant Restrictions” and “Business Process Step Configuration Options.”

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, 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 an swer is the manager cannot select London because it is not in the list of hiring restrictions for location .

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

The correct answers are B and C.

Organization-based security groups derive membership automatically from an organizational structure in Workday—such as supervisory , cost center , region , or location hierarchies . Users are included in the group based on their association with that organization or hierarchy.

B. If a user is part of the Europe Location Hierarchy , they automatically gain access assigned to that organization-based security group.

C. Similarly, users belonging to the Information Technology cost center hierarchy are included in the corresponding cost center-based security group.

Options A and D are incorrect because location membership alone (without organizational hierarchy) or job family assignment does not control membership in an organization-based group.

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.

The correct answers are C – Position Management and D – Job Management.

In Workday, supervisory organizations can only use one of two delivered staffing models:

Position Management : Each position is a distinct entity that must be created and approved before hiring. It supports detailed tracking of vacancies and headcount.

Job Management : Hiring is managed at the job level, allowing multiple workers to be hired under a single job requisition without individual position control.

Workday does not deliver “Headcount Management” or “Customer Defined Staffing Models” as valid options. The staffing model is selected when creating or editing a supervisory organization and determines how headcount, hiring, and reporting are managed.

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.

During a Change Job event, Workday re-evaluates compensation plan eligibility based on the employee’s updated attributes, such as location. Even if an allowance plan has no eligibility rules, it can still be removed during the Propose Compensation Change step if not explicitly retained.

The correct way to ensure that an intentionally assigned allowance plan remains on the employee’s record is for the compensation partner to restore or re-add the plan during the Propose Compensation Change subprocess of the Change Job transaction. This keeps the correction within the same business process and ensures accurate audit tracking.

Request Compensation Change is a standalone process and should not be used mid-transaction. Plan adjustments and rollouts are bulk tools and are not appropriate for correcting a single employee during an in-flight job change.

Therefore, restoring the plan during Propose Compensation Change is the correct and Workday-supported approach, making option D correct.

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.

By default, Workday allows only one one-time payment per event when the Enable Multiple One-Time Payments tenant setting is not enabled . This behavior ensures strict control over one-time payment submissions and prevents multiple payments from being entered within the same transaction.

The Enable Multiple One-Time Payments setting in Edit Tenant Setup – HCM > Compensation explicitly removes this restriction and allows users to submit multiple one-time payments with the same reason and effective date. Since the business requirement is to limit submissions to a single payment , this setting must remain disabled .

Security configuration and business process rules do not control the number of one-time payment rows allowed in an event. They only manage access and approval flow.

Therefore, to enforce a single one-time payment per event, administrators must not enable the Multiple One-Time Payments setting , making option B correct.

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

Workday provides a wide range of standard delivered reports to support workforce analysis, job architecture review, and organizational planning. When the requirement is to view job profile details , the correct Workday-delivered standard report is the Job Catalog . The Job Catalog report is specifically designed to display detailed information about job profiles that exist in the tenant.

The Job Catalog report presents comprehensive job profile attributes such as job title, job family, job family group, job category, management level, worker type eligibility, and other job architecture–related fields. This report is commonly used by HR administrators, compensation teams, and organizational design partners to review and validate job structures across the enterprise. Because job profiles are foundational objects in Workday HCM, the Job Catalog serves as the primary reporting tool to analyze and audit these profiles.

Other options do not meet this requirement. Find Workers focuses on worker data and employment details, not job profile configuration. Job History reports historical job changes for workers and does not display standalone job profile definitions. All Jobs typically reflects jobs held by workers or staffing data rather than the underlying job profile setup.

From a Workday Pro HCM perspective, understanding the distinction between job profiles and worker job assignments is critical. The Job Catalog report aligns directly with job architecture governance and supports reporting needs related to job design, standardization, and compliance. Therefore, the correct and fully Workday-verified answer is Job Catalog , as it is the standard report that displays detailed job profile information.

In Workday HCM, understanding and reviewing the organizational structure is essential for workforce planning, management reporting, and operational decision-making. Workday delivers several standard reports and tasks, but only one is specifically designed to visually display organizational hierarchies in an intuitive and navigable format: Navigate Hierarchy .

The Navigate Hierarchy report allows users to visually explore organizational structures such as supervisory organizations, company structures, cost centers, and other hierarchy-based organiza tions. This report presents parent-child relationships clearly, enabling users to drill up and down the hierarchy to understand reporting lines, organizational ownership, and structural alignment. It is especially useful for HR partners, managers, and business leaders who need a quick visual representation of how the organization is structured.

Other options do not meet this requirement. Find Events focuses on business process events and transactions, not organizational relationships. Job Catalog displays job profile details and job architecture information, not organizational hierarchies. Find Workers returns worker records and employment details but does not visualize how organizations are structured.

From a Workday Pro HCM perspective, Navigate Hierarchy is the correct tool when the objective is visualization rather than data extraction. It supports real-time navigation and provides immediate insight into how organizations relate to one another within the tenant. This makes it the preferred and Workday-verified report for reviewing and understanding organizational structures.

Therefore, the correct answer is Navigate Hierarchy , as it is specifically designed to visualize organizational hierarchies in Workday.