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

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

In Workday, a subprocess is a step type used within a business process definition to initiate another, independent business process . The purpose of a subprocess is to trigger a set of predefined steps from a separate process that runs as part of the main (parent) process. This provides modularity and reusability across multiple BPs.

For example, when configuring a Hire process, you might add a Request Compensation Change subprocess to automatically launch once the hire is initiated. This avoids duplicating configuration work and ensures consistency in how related actions are handled across events.

Option A is incorrect because approvals are managed through Approval Steps , not subprocesses.

Option C is incorrect — background processes are system-managed and not user-configured through subprocesses.

Option D refers to To-Do or Notification Steps , which are informational, not subprocess-driven.

Thus, subprocesses are a way to embed or chain additional processes into an event flow, promoting flexibility and maintainability.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Subprocess Step Type and Configuration Best Practices.”

When a security group initiates a business process, what the group can do during that initiation is controlled through business process security for the relevant business process type. In this case, the Manager security group should be able to initiate Termination but only update limited termination information, specifically termination dates and reasons. That is a business process security configuration requirement, not a general domain-reporting issue. The appropriate configuration is to locate the Termination business process type and adjust the security permissions accordingly so that the Manager group has only the correct initiating action and section-level access. The consolidated template option is incorrect because the requirement is not about consolidating approval tasks. Domain security can control access to data broadly, but this question concerns what fields or sections can be used during a specific Termination initiation flow. View Security for Securable Item can help analyze a field’s security, but it is not the configuration task that grants or restricts the Termination initiation experience. Therefore, the Termination business process type security configuration is correct. Reference topics: Security, Business Process Security, Initiating Action, Termination, and section-level permissions.

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

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

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

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

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.

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 business process terminology, the subject of a business process event is the Target. The target is the person, position, organization, or object that the business process is acting on. For example, in a Hire event, the target is the worker being hired; in a Change Job event, the target is the worker whose job is being changed; and in an organization event, the target may be the organization being updated. The Initiator is the user or process that starts the event, so it describes who launched the process rather than what the process is about. Instance is a general Workday object occurrence and does not specifically identify the subject of a business process event. Primary Business Object refers to the underlying object type associated with a business process definition or template, but it is not the transactional subject term used in routing and event context. Understanding target is important because business process routing, security, notifications, and condition rules often evaluate fields relative to the target. Therefore, Target is the correct answer. Reference topics: Business Processes, Business Process Event Context, Target Object, Initiator, and Primary Business Object.

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

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

In Workday, a Business Process (BP) defines how specific business events are executed within the system. The true statement among the options is that you can create business process definitions based on rules . Workday allows you to maintain rule-based BP definitions , meaning that a single BP can have multiple versions triggered under different conditions (for example, based on supervisory organization, company, location, or job profile).

This functionality enhances configuration flexibility by allowing organizations to adapt process flow depending on contextual attributes — without duplicating processes. Each version operates under a defined condition rule , evaluated at runtime to determine which BP definition applies.

Options A, B, and C are incorrect:

A is false because not every action step can be added to every process — the available step types depend on the BP template (for example, Hire, Change Job, or Request Compensation Change).

B is false since condition rules can only be applied to specific steps where the system allows configuration (for instance, approvals and to-dos).

C is false because only a designated Completion Step marks the end of the process, and it cannot be assigned arbitrarily to any step.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework and Configuration Guide (2023R2, Workday Learning).

Sections: “Rule-Based Business Process Definitions,” “Business Process Configuration Best Practices,” and “Condition Rule Framework.”

The correct answer is B – Role-Based (Unconstrained) can view the Staffing tab of all supervisory organizations. User-Based can view the Staffing tab of supervisory organizations they are assigned to support.

A Role-Based (Unconstrained) security group provides broad, system-wide access to the data and functionality governed by its assigned domains and business processes. Unlike constrained groups, these are not limited by supervisory or organizational context. As a result, members can view the Staffing tab for all supervisory organizations across the tenant.

A User-Based security group, on the other hand, grants access only to specific data tied to the individual user’s security configuration. If the user is associated with certain organizations, their access will be limited accordingly.

Therefore, while unconstrained roles are ideal for high-level administrators who need full visibility, user-based access is suitable for specific or limited visibility.

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.

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

When a worker who is part of a Role-Based Security Group (RBSG) transfers to a different position, Workday automatically reviews the roles associated with their supervisory organization through the Assign Roles subprocess.

The Assign Roles subprocess within the Change Job business process ensures that role assignments (such as HR Partner, Manager, or Payroll Partner) are updated according to the new supervisory organization’s configuration. This automation helps maintain proper security access and prevents users from retaining permissions tied to their previous role or organization.

Option A ( Assign Pay Group ) manages payroll assignment, not security.

Option B ( Manage Job History ) records past job data, unrelated to role security.

Option D ( Manage Business Processes for Worker ) handles process configurations, not security group updates.

Thus, Assign Roles is the correct subprocess to maintain accurate security group membership during position changes.

Reference (Paraphrased Source):

Workday Pro HCM Core – Security and Business Process Configuration Guide (2023R2), Section: “Role Assignments in Staffing Events.”

In Workday HCM, business process definitions consist of multiple steps that may include approvals, notifications, integrations, or system actions. Some steps are configured to initiate a subprocess , meaning that when the step runs, it launches another related business process, such as compensation changes, provisioning, or document generation. Identifying whether a step triggers a subprocess is essential for troubleshooting, impact analysis, and process design.

The correct tab to determine whether a step initiates a subprocess is Allowed Services . The Allowed Services tab displays the services (subprocesses) that can be launched from a specific step within the business process definition. If a step is configured to initiate a subprocess, it will be clearly listed on this tab, indicating which downstream business processes may be triggered when the step executes.

The other options do not provide this information. Available Rules and Fields lists condition rules and data fields that can be used for routing or validations but does not show subprocess initiation. Allowed Actions by Role defines what actions security roles can perform during the business process, such as approve or cancel, and is unrelated to subprocess execution. Notifications shows alert and message configurations but does not indicate subprocess behavior.

From a Workday Pro HCM perspective, the Allowed Services tab is a critical tool for understanding process orchestration within Workday. It helps administrators visualize dependencies between business processes and ensures that changes to one process do not unintentionally impact others.

Therefore, the correct and Workday-verified answer is Allowed Services , as it identifies whether a business process step initiates a subprocess.

In Workday, the Manage Basis Total configuration enables organizations to enter a single total compensation amount , which Workday then allocates across multiple compensation plans according to predefined rules, percentages, or limits. This is particularly useful in countries like Italy, where compensation discussions often focus on total compensation rather than individual components.

When Manage Basis Total is enabled on a compensation basis, administrators or managers can enter one total amount during a staffing or compensation event. Workday automatically distributes that amount across salary, allowances, and other included plans based on the compensation basis configuration.

Eligible Earnings Override is a payroll-specific tool and does not control compensation entry behavior. Total Base Pay and Total Salary & Allowances are reporting or calculation concepts, not data entry mechanisms.

By using Manage Basis Total , the company ensures consistency, simplifies compensation entry, and enforces internal rules for Milan-based employees.

Therefore, the correct answer is Manage Basis Total .

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 – Organization Types and Structures Guide, 2023R2):

The correct organization type for managing temporary project-based teams is a Matrix Organization . Matrix organizations are designed to group employees from different supervisory organizations to work together on a temporary or functional basis, such as projects or task forces.

This structure allows the assignment of a temporary manager (Matrix Manager) who oversees project-related activities without changing employees’ primary supervisory reporting relationships. The matrix manager gains visibility into all assigned members, enabling effective project oversight.

Options A ( Location Hierarchy ) manages physical work locations, not project teams.

Option B ( Supervisory ) defines permanent reporting structures.

Option D ( Pay Group ) organizes workers for payroll purposes only.

Thus, Matrix Organization provides the flexibility and visibility required for cross-functional, project-based staffing.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Matrix Organizations and Project-Based Management.”

From the Workday Module 2 Binder :

“User-based security groups include roles such as Security Administrator and HR Administrator. These are assigned directly to individual users and determine their access and capabilities within the tenant.”

– Workday Module 2 Binder, Security Configuration Section

User-Based Security Groups are directly assigned to specific users , rather than based on roles or job positions.

Security Administrator and HR Administrator are classic examples — they ' re given to individual users based on need or access level.

Compensation Partner and Managers are role-based security groups , which are tied to a worker ' s role within an organization, not directly to a user.

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

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

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

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

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

In Workday HCM, access to worklets , including delivered worklets such as the Pay App , is governed by domain security , not business process security. Worklets display data and provide navigation to reports, tasks, and applications, all of which rely on domain-level permissions to control visibility and access.

To prevent Contingent Workers from seeing or accessing the Pay App on their Home landing page, you must remove their associated security group from the domain security policy that grants access to pay-related data. Once domain access is removed, the Pay App will no longer appear for those users because Workday dynamically displays worklets based on the user’s domain permissions.

Business process security policies control who can participate in transactional processes —such as initiating or approving a Hire, Change Job, or Termination—and do not influence whether a worklet appears on the Home page. Therefore, options B and D are incorrect because modifying business process security would not affect worklet visibility.

Option C is also incorrect because adding a security group to a domain security policy would grant access, not restrict it.

From a Workday Pro HCM best-practice perspective, restricting access to delivered worklets is always achieved through domain security policy configuration . This ensures consistent behavior across dashboards, reports, and applications tied to sensitive data such as compensation and payroll.

Therefore, the correct and Workday-verified way to prevent Contingent Workers from accessing the Pay App is to remove the security group from the domain security policy .

The correct answer is B – View Security for Securable Item.

In Workday, every task , report , domain , and business process is considered a securable item . To analyze how access to a specific task (like Change My Legal Name ) is controlled, the system administrator uses the View Security for Securable Item report.

This report allows users to:

Identify which domain security policy governs the securable item,

See what security groups currently have access,

Determine the type of access granted (View, Modify, Initiate, etc.), and

Understand the security policy inheritance associated with the item.

For example, when you run this report and enter “Change My Legal Name” as the securable item, Workday returns the domain policy controlling it—typically within the Worker Data: Personal Information domain. From there, security administrators can update access via the Maintain Domain Security Policy for Functional Area task if necessary.

This is the standard and recommended Workday method for determining how any specific action, report, or task is secured.

A consolidated approval task combines multiple approval actions into a single approval experience, but the user who receives that consolidated task still needs the correct business process security permissions for each underlying process being approved. In this scenario, the HR Administrator must approve the termination details, retiree status, and service date changes. Therefore, the HR Administrator must be added to the Approve section for each relevant business process security policy: Termination, Add Retiree Status, and Service Dates Change. Ad Hoc Approve is not correct because the requirement is not to allow ad hoc approval routing; it is to permit the HR Administrator to perform the standard approval actions included in the consolidated approval. Initiating Action is also incorrect because initiating a process and approving a process are separate security actions. Granting initiate access would not authorize the user to approve the consolidated approval step. The security must match the action presented in the consolidated task. Therefore, adding the HR Administrator to the Approve section on all three processes is correct. Reference topics: Security, Business Process Security Policies, Consolidated Approval, Approve Permissions, and Termination subprocess security.

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

The correct answer is B – Contract Contingent Worker.

In Workday, Contingent Workers are individuals who perform services for the organization but are not on the organization’s payroll (they are paid by a third party). To bring a contingent worker into the system, the appropriate business process is Contract Contingent Worker .

This business process mirrors the Hire Employee process but is designed for contingent workforce management. It captures key details such as vendor, contract dates, location, job profile, and supervisory organization . The process is typically initiated when the organization wants to assign contingent workers under a supervisory org for project or temporary work.

The Hire Employee process (option A) is used for direct employees only, while options C and D are termination or ending processes, not staffing ones.

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 .

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

The Compensation Spreadsheet is a powerful Workday reporting and analysis tool that allows managers and HR partners to view detailed compensation information for employees across one or more organizations they manage or support. It supports side-by-side viewing of key metrics, including:

Total base pay

Compensation package

Compa-ratio

Position in range

Allowances and bonuses

The spreadsheet format is specifically designed for managerial review, planning, and analysis , with optional inclusion of subordinate organizations. It is widely used during compensation review cycles and off-cycle analysis.

Other reports have more limited scope:

Employee Compensation Audit focuses on eligibility mismatches

Job Profile reports focus on structure, not worker-level pay

Total Rewards is employee-facing and not manager-analytic

Therefore, the correct answer is Compensation Spreadsheet , making option D correct.

The correct answer is B – Create Position.

In Workday, when a supervisory organization uses the Position Management staffing model, each hire must be associated with a specific position . Before initiating a hire, an administrator or HR partner must execute the Create Position business process to establish that position record.

This process defines critical attributes such as:

Job Profile (e.g., HR Analyst, Accountant),

Location ,

Time Type (Full-time/Part-time),

Worker Type (Employee or Contingent Worker),

Availability Date and Earliest Hire Date , and

Position Restrictions that control who and how hiring can occur.

Once the position is created and approved through the configured workflow, it becomes available for hiring via the Hire Employee business process. Without an open, approved position, the system will not allow a hire in Position Management organizations.

After a business process completes in Workday, the valid corrective action that can be taken is to Rescind the process. The Rescind action allows an authorized user (typically with HR Partner or BP Administrator access) to reverse the completed business process, effectively undoing the transaction and restoring the system to its prior state.

This is often used when incorrect data was entered, or when the transaction was completed prematurely. Rescinding a process automatically generates related rescind events and notifications, ensuring system integrity.

Option A ( Cancel ) applies to in-progress business processes only — it stops a process before completion.

Option B ( Reassign ) allows task ownership changes while a process is active but not after completion.

Option D ( Delegate ) is a security feature for work delegation, not a post-completion action.

Thus, Rescind is the only valid corrective action once a BP is finalized.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework and Transaction Correction Guide (2023R2), Section: “Rescind and Cancel Business Processes.”

In Workday HCM, To Do steps are commonly used within business process definitions to prompt users to complete follow-up actions, such as entering additional information or reviewing details. By default, a To Do step is required , meaning the business process cannot move forward until the user completes it. However, there are scenarios where the action should be optional, allowing the process to continue even if the user does not complete the task.

To allow a user to skip a To Do step , the correct configuration is to make the step optional . When a step is marked as optional, Workday presents the To Do task to the user but does not require completion for the business process to proceed. The user can choose to complete the task or bypass it without blocking the transaction.

The other options do not achieve this outcome. Editing the step notification only changes messaging and does not affect whether the step is required. Assigning the completion step controls when the transaction is finalized but does not alter step requirements. Adding a step condition determines whether the step runs at all based on defined criteria, but it does not give the user the ability to skip the step once it is initiated.

From a Workday Pro HCM configuration standpoint, marking a To Do step as optional is the correct and recommended approach when the action is helpful but not mandatory. This ensures flexibility for users while maintaining the integrity and flow of the business process.

Therefore, the correct and Workday-verified answer is Make the step optional .

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 answer is C – Compensation Grade.

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

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

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

In Workday HCM, compensation grades are a foundational component of the compensation framework and are primarily used to define pay ranges (minimum, midpoint, and maximum) for roles within the organization. These grades are typically associated with job profiles, positions, or job families to ensure internal equity and market competitiveness.

From a transactional perspective, compensation grades guide users with appropriate security access —such as HR Partners or Compensation Partners—when entering or proposing compensation amounts during staffing and compensation events. When a worker is hired, promoted, transferred, or receives a compensation change, the assigned compensation grade determines the acceptable pay range that can be entered in the transaction. This ensures consistency, compliance with company policy, and alignment with compensation strategy.

Compensation grades do not calculate compensation basis, connect compensation to payroll earnings, or determine overtime eligibility. Those functions are handled by compensation basis rules, payroll mappings, and time tracking or FLSA status configurations, respectively. Instead, compensation grades act as reference structures that inform and constrain compensation entry, often working in conjunction with compensation plans and guidelines.

Additionally, compensation grades can be used in reporting and analytics to compare compensation across roles and to identify exceptions where pay falls outside the defined range. Overall, their primary purpose is to provide guidance and controls for entering specific pay rates , making option D the correct answer according to Workday Pro HCM best practices.

In Workday organization configuration, multiple organizations can be grouped into a hierarchy or rollup structure for reporting, analysis, and transaction visibility. The task used to group existing organizations together for reporting purposes is Assign Included Organizations. This task allows administrators to specify which organizations are included beneath a higher-level organization or hierarchy node, enabling consolidated reporting across revenue, expense, and other organization-related transactions. Assign Superior changes the parent or superior relationship of an organization, but it does not directly answer the requirement to group multiple organizations for reporting. Inactivate Organization removes an organization from active use and is unrelated to reporting rollups. Create Custom Organization creates a new organization object, but creation alone does not group existing organizations under a reporting structure. The scenario explicitly asks for the task that groups multiple organizations, not the task that creates the organization itself. Therefore, Assign Included Organizations is the correct answer. Reference topics: Organizations, Organization Hierarchies, Included Organizations, Cost Center Hierarchies, and organization reporting structures.

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

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

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

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

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

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

When creating a new supervisory organization , Workday allows the subordinate organization to inherit key structural and configuration attributes from its superior organization. These inherited elements include:

Visibility (A): Determines who can view the organization and its members, inherited to maintain consistent access control.

Organization Assignments (B): Such as company, cost center, region, and custom organizations, ensuring hierarchical alignment.

Staffing Model (D): The staffing model (Position Management or Job Management) is inherited to ensure consistency in hiring and staffing control.

Subtype (C) and Name (E) are not inherited; they must be defined at the time of creation. Subtype determines the organization’s classification, while the name uniquely identifies it.

Reference (Paraphrased Source):

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

" Subordinate supervisory organizations inherit configuration from their superior supervisory organization, including attributes such as the staffing model, organization assignments, and visibility settings. This ensures consistency and reduces administrative overhead. "

– Workday Module 2 Binder, Supervisory Organizations Section

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

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

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

What hiring restriction do you set to meet this need?

A. Job Family Group

B. Job Profile

C. Job Description

D. Job Category

Answer: A

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

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

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

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

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

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

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

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

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

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.

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, compensation plans remain active through the Actual End Date entered on the plan. The system removes the plan the day after the Actual End Date, ensuring the employee receives compensation through the final eligible day.

This behavior supports accurate payroll calculation and avoids prematurely ending compensation. Workday does not delay removal to the end of the pay period or month unless explicitly configured elsewhere.

Therefore, the plan is removed on the actual end date plus one day , making option A correct.