Workday Pro HCM Core Exam Questions

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

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, pay rate type (Salaried or Hourly) is a foundational attribute used across staffing, compensation, and eligibility logic. When a salary plan's eligibility rule evaluates pay rate type, that value must be consistently defined at the job profile level to avoid mismatches or incorrect eligibility results.

Assigning pay rate types directly to job profiles ensures that employees hired into those roles inherit the correct classification automatically. This reduces reliance on manual data entry and prevents discrepancies during hire, job change, or compensation events.

Assigning salary plans to job profiles does not guarantee accurate eligibility if the pay rate type itself is not consistently defined. Modifying the eligibility rule weakens the control logic. Job requisitions may temporarily hold pay rate types, but job profiles are the source of truth for long-term configuration.

Therefore, assigning pay rate types to job profiles is the correct and Workday-recommended next step, making option D correct.

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.

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.