Free and Premium Workday Workday-Pro-HCM-Core Dumps Questions Answers

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.

The correct answer is C – All Employees.

Workday delivers the All Employees security group as a predefined (delivered) user-based security group that automatically includes every active worker within the tenant. This group grants broad access to non-sensitive information that all workers should be able to view—such as organizational structure, reporting relationships, job profiles, and public worker details (like name, title, and location).

The All Employees group is fundamental for system usability and transparency, ensuring employees can navigate the org chart, identify colleagues, and understand reporting hierarchies without compromising confidential data.

Workday recommends maintaining this group’s configuration in its default state to avoid restricting essential information visibility. Security administrators may, however, further refine domain policies to exclude sensitive data while preserving general organization structure access.

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.

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.

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

To have the Company Organization automatically default when hiring workers into a supervisory organization, you must update the organization settings through the Edit Supervisory Organization task.

This task allows you to define default organization assignments , including Company , Cost Center , Region , and Custom Organizations . Once these defaults are set, Workday automatically populates these values during staffing events such as Hire or Add Job , reducing manual entry and ensuring consistent data alignment across the hierarchy.

Option B ( Create Position ) is used to define positions within the supervisory org, not defaults.

Option C ( Edit Name/Code ) modifies identifiers only.

Option D ( Assign Roles ) relates to security role assignments.

Therefore, Edit Supervisory Organization is the correct task to establish the default Company for new hires.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Defining Default Organization Assignments.”

In Workday, field-level visibility during business processes—especially for self-service events—is controlled through Optional Fields configuration, not security domains. The Request One-Time Payment for Self process has its own optional field settings that allow administrators to show or hide specific fields for employees.

To prevent employees from modifying sensitive options such as Gross Up and Send to Payroll, administrators must configure Optional Fields specifically for the Request One-Time Payment for Self process and hide those checkboxes. This preserves the self-service capability while enforcing governance and preventing unintended financial impact.

Removing security domain access would block employees from initiating the process entirely, which does not meet the requirement. Configuring optional fields on the administrator-driven Request One-Time Payment process would not affect self-service behavior.

Therefore, the correct and precise solution is to configure Optional Fields for Request One-Time Payment for Self and hide the fields, making option D correct.

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

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

In Workday, every worker must belong to exactly one Supervisory Organization . The Supervisory Organization defines the management hierarchy and reporting structure for workers and positions. It serves as the foundation for staffing, business process routing, security role assignment, and approval workflows.

When hiring or transferring a worker, assigning them to a supervisory organization ensures that the worker’s manager , HR partner , and other role-based participants are correctly identified. Without this relationship, the worker cannot be successfully staffed or managed within the tenant.

Options B ( Matrix ), C ( Cost Center ), and D ( Company ) may also be required for organizational reporting or accounting, but only Supervisory Organizations are mandatory for all workers because they define managerial oversight and operational hierarchy.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Supervisory Organizations as the Basis of Staffing Structure.”

In Workday staffing, position restrictions define which values are allowed when a worker is hired into a position. In this scenario, Worker Type is restricted to Employee, but Worker Subtype is blank. A blank optional restriction does not mean the manager cannot select a value; it means the value is not restricted by that specific field. Because Worker Type is restricted to Employee, the available subtypes must be valid subtypes under the Employee worker type. The manager can therefore select any Worker Subtype that belongs to Employee, such as Regular or another configured employee subtype. The answer is not Employee because Employee is a worker type, not a worker subtype. Contingent Worker is incorrect because it is a different worker type and is excluded by the Employee restriction. Any subtype of the Contingent Worker worker type is also incorrect because contingent worker subtypes are not valid when the position is restricted to Employee. The restriction framework narrows subtype choices through the selected worker type. Therefore, any subtype of the Employee Worker Type is correct. Reference topics: Staffing, Position Restrictions, Worker Type, Worker Subtype, and position-based hiring controls.

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

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

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

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

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

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.

In Workday, when you need to trigger system events or sub-actions , such as initiating compensation eligibility rules for a newly hired worker , you use the Action Step type. The Action step executes a system-defined function or event automatically, without requiring manual user intervention.

In this case, adding an Action Step to the Hire Business Process (BP) can initiate the “Request Compensation Change” or run the “Determine Eligibility” process to assess compensation plans and eligibility rules for the new employee. This ensures that the worker’s pay components are properly configured based on eligibility criteria immediately upon hire completion.

Option A (Complete Questionnaire) is used to collect additional data; Option B (Service) is for integration or automated system services; and Option C (To Do) is used for manual informational or procedural tasks. Only Action Steps directly invoke system logic or secondary processes.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Action Step Configuration and Functional Usage.”

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, participation in business processes—such as Hire, Termination, or Job Change—is controlled by Business Process Security Policies , not by domain security. Business process security determines who can initiate, approve, review, or take action on specific steps within a business process definition.

To remove an HR Partner from participating in the Hire process, you must update the Business Process Security Policy associated with the Hire business process. This policy defines which security groups are authorized to perform specific actions (for example, initiate, approve, or complete steps) within that process. By removing the HR Partner role-based security group from the relevant steps or permissions in the Hire business process security policy, Workday will no longer route Hire-related tasks or approvals to HR Partners.

Option D, Domain Security Policy , is incorrect because domain security controls data access , such as viewing or editing worker or organization data, not participation in business process steps. Even if an HR Partner has domain access, they cannot participate in a business process unless explicitly granted permissions through business process security.

Option A, Maintain Assignable Roles , is used to determine which roles can be assigned to organizations, not to control business process participation. Option C, Maintain Functional Areas , is used for organizing security policies and reports, not for granting or removing process access.

From a Workday Pro HCM best-practice perspective, any change related to who participates in a business process must be made in the Business Process Security Policy . This ensures precise control, proper approval routing, and compliance with organizational governance.

Therefore, the correct and Workday-verified answer is Business Process Security Policy .

In Position Management, a position can be made temporarily unavailable for staffing without permanently closing or deleting the position. The task designed for this purpose is Manage Position Freeze. A position freeze prevents the position from being filled while preserving the position record, restrictions, and future availability for planning purposes. This is useful when hiring is paused for budget, approval, or timing reasons but the organization does not want to remove the position from the structure. Edit Position Restrictions is used to change allowed staffing values such as job profile, location, worker type, time type, or worker subtype; it does not freeze staffing availability. Edit Position changes position details, but it is not the specific task for temporarily blocking hiring. Close Position is a stronger and more permanent action that removes the position from availability because the position is no longer needed. The scenario clearly says temporarily unavailable to fill, which matches a freeze, not a close. Therefore, Manage Position Freeze is correct. Reference topics: Staffing, Position Management, Position Restrictions, Position Status, and Manage Position Freeze.

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

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

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

Therefore, option A is the correct answer.

Compensation steps in Workday are designed to support structured, automatic pay progression based on time, service, or measurable criteria . To meet the requirement in this scenario, the configuration must enforce two separate conditions before the employee progresses to the next step: completion of 12 months of duration and accumulation of 400 worked hours .

In Workday, duration defines the minimum amount of time an employee must remain on a compensation step before becoming eligible for progression. Setting the duration to 12 months ensures the employee cannot advance earlier than one year of service. However, duration alone is insufficient when additional criteria—such as hours worked—must also be met.

This is where step progression rules are used. A step progression rule allows administrators to define measurable thresholds, such as hours worked, that must be satisfied before progression occurs. By configuring a rule that counts 400 hours worked , Workday ensures that employees who do not meet the hours requirement will not advance, even if they have completed 12 months.

Options A and B only configure one condition and do not satisfy the full requirement. Option C applies to initial step assignment, not progression eligibility.

Therefore, combining a 12-month duration with a step progression rule based on hours worked is the correct and Workday-supported configuration, making option D the correct answer.

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.

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

The values available in the Subtype field when creating a new Cost Center are determined by the subtypes configured for that specific organization type . Each organization type (e.g., Company, Cost Center, Region, or Supervisory) can have one or more associated subtypes that define additional categorization or behavior.

During configuration, administrators define which subtypes are valid for each organization type. Hence, when an end user creates a Cost Center, only the subtypes associated with the “Cost Center” organization type will appear in the selection list.

Options A, C, and D are incorrect because subtypes are not influenced by location, user role, or system recommendations — they are strictly defined in the configuration setup.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Defining Organization Types and Subtypes.”

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.

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

Workday delivers Overdue Notifications automatically to remind users that a step or task within a business process has not been completed within the expected time frame. These notifications are part of Workday’s built-in process monitoring and are generated by the system based on defined due dates or completion delays.

Overdue notifications ensure accountability by alerting users when a step is pending beyond its due date, helping maintain compliance with HR and operational timelines.

Options A ( Custom ) and C ( Alert ) refer to user-configurable messages and rule-based triggers that administrators create, but they are not delivered automatically by Workday unless specifically configured. Option D ( System ) refers to general system messages, not process-driven notifications.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework Configuration Guide (2023R2), Section: “Workday-Delivered Notifications and Overdue Task Alerts.”

The correct answer is B – Have an open, approved position.

In Workday’s Position Management staffing model, each hire is tied to a specific position . Before a worker can be hired, a position must exist, be opened, and be approved through the appropriate business process.

Once a position is approved, it becomes available for the Hire or Add Job process. Without an approved position, no worker can be assigned under that supervisory organization. The position serves as the structural foundation for tracking headcount, job details, and time-to-fill metrics.

Options A and C refer to configuration prerequisites, but the question specifically focuses on the operational readiness to hire. Option D is incorrect because a hire cannot occur until after a position exists.

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.

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 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 HCM, standard reports are delivered in several formats, each designed for different reporting needs and levels of complexity. Common Workday-delivered report types include Advanced , Report Writer , Matrix , and XpressO . While most standard reports allow users to create a copy and modify it to meet business-specific requirements, XpressO reports are the exception .

XpressO reports do not allow copy access. These reports are system-delivered, predefined reports designed for quick access to commonly needed information. They are optimized for perfor mance and usability and are typically used as-is without customization. Because of their underlying structure and system dependencies, Workday restricts users from copying XpressO reports into custom reports.

In contrast, Advanced , Report Writer , and Matrix reports all allow copy access, provided the user has the appropriate security permissions. This capability enables report writers to duplicate delivered reports, adjust fields, filters, prompts, and layouts, and create tenant-specific reporting solutions while preserving the original delivered report.

From a Workday Pro HCM best-practice perspective, understanding which report types can be copied is important for efficient reporting design. When customization is required, report developers should start with a copyable report type rather than attempting to modify or replicate XpressO functionality. If similar data is needed, report writers can build a new Advanced or Report Writer report using the same data sources.

Therefore, the correct and Workday-verified answer is XpressO , as it is the only Workday-delivered standard report type that does not allow copy access.

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 HCM, compensation grades are a core component of the job and grade framework , which belongs to organizational configuration rather than transactional staffing activities. The primary purpose of assigning a compensation grade to a job profile is to define and default the appropriate pay range —minimum, midpoint, and maximum—for employees performing that job.

When a compensation grade is attached to a job profile, Workday uses the associated grade profiles (which may vary by location, currency, or frequency) to automatically determine the salary or hourly range during hire, job change, and compensation change events. This ensures consistency, internal equity, and alignment with market data across the organization.

Compensation grades do not control compensation frequency, bonus eligibility, or target compensation amounts. Frequency is defined at the compensation plan level, bonus eligibility is governed by eligibility rules, and target compensation is typically managed through compensation plans and guidelines.

By separating job architecture (grades) from transactional compensation plans , Workday enables scalable global compensation structures that are easy to maintain and audit. Therefore, the correct and primary purpose of assigning a compensation grade to a job profile is to default the appropriate pay range , making option C correct.

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

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

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

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

Therefore, option A is the correct answer.

In Workday, 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, step-based grades use progression logic to control movement from one step to the next . Conditional logic is applied only to steps that an employee progresses through , not to the final step in the sequence.

In this scenario, the business requirement is to allow progression only if the employee does not have a poor performance rating (value 1) . This condition must be evaluated when the employee attempts to move from:

Step 1 → Step 2

Step 2 → Step 3

There is no progression after Step 3 , so conditional logic is not required for that step.

Conditional logic for step progression is configured at the step level , not at the grade profile level. The logic must explicitly evaluate that the performance review rating is not equal to selection list value 1 .

Options B and D are incorrect because grade profiles do not control step-level progression logic. Option C incorrectly allows progression only when performance is poor, which is the opposite of the requirement.

Therefore, conditional logic should be applied to Step 1 and Step 2 , evaluating that the rating is not in selection list value 1 , making Option A the correct answer.

The report used to view organization activities grouped by effective date is Reorganizations. In Workday, organization changes are effective-dated so that structural changes, hierarchy updates, included organization changes, and related organization activities can be tracked over time. Reorganization events provide a controlled way to group and review organization changes that share an effective date. This is especially important when organization structures are used for financial or workforce reporting because historical and future-dated changes must be auditable. Find Events can locate business process events, but it is not the best report for reviewing organization activities grouped by effective date. Org Chart provides a visual view of reporting or organization structure, not a grouped list of organization activities by effective date. Navigate Hierarchy supports browsing through hierarchy relationships but does not serve as the effective-dated organization activity report. Because the scenario asks specifically for viewing organization activities grouped by effective date, Reorganizations is the correct answer. Reference topics: Organizations, Reorganization Events, Effective Dating, Organization Activities, and hierarchy maintenance.

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

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

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

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

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

In Workday, 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 HCM, advanced custom reports offer powerful filtering capabilities, but certain configuration options intentionally limit available fields to ensure optimal system performance. One such option is the Optimized for Performance checkbox. When this option is selected, Workday restricts filters to indexed fields only .

Indexed fields are pre-optimized by Workday to support faster query execution and efficient data retrieval, especially in large tenants with significant data volumes. By limiting filters to indexed fields, Workday ensures that reports run quickly and reliably without placing excessive load on the system. This design aligns with Workday’s performance and scalability standards.

When Optimized for Performance is enabled, non-indexed fields are excluded from filter selection because filtering on those fields could result in long-running queries or degraded system performance. This is expected and intended behavior, not a limitation of the report writer or data source.

The other options are incorrect. Using an indexed data source does not, by itself, restrict filters to indexed fields. The Temporary Report checkbox controls report persistence and availability, not filter behavior. A standard data source can still allow non-indexed fields unless performance optimization is explicitly enabled.

From a Workday Pro HCM best-practice perspective, the Optimized for Performance option should be used when reports are expected to run frequently, support dashboards, or be shared widely. While it reduces filter flexibility, it significantly improves execution efficiency and reliability.

Therefore, the correct and Workday-verified reason you can only select indexed fields is that the Optimized for Performance checkbox is selected .

The correct answer is C – Maintain Staffing Models.

In Workday, the Maintain Staffing Models task enables administrators to update or modify the staffing model assignments for multiple supervisory organizations simultaneously. This task provides a consolidated interface to review which organizations use Position Management or Job Management , and allows bulk updates where necessary.

While the Edit Staffing Model task is used to change the staffing model for a single supervisory organization, Maintain Staffing Models is the correct and efficient method for multi-org updates—especially during tenant configuration or large-scale reorganizations.

The correct answer is A – Role-Based (Constrained) can approve compensation of workers they are assigned to support. User-Based can approve compensation of all workers.

In Workday, Role-Based (Constrained) security groups restrict access based on an assigned organization or supervisory hierarchy. Members of a constrained role (such as Compensation Partner ) can perform actions—like approving compensation changes—only for workers within their assigned supervisory organizations.

Conversely, User-Based security groups are not tied to an organization unless specifically constrained, and typically have unconstrained, tenant-wide access . When both security groups have access to the same domain or business process (e.g., “Approve Compensation Change”), the User-Based group can approve changes for all workers, while the Role-Based (Constrained) group’s access is limited by their assigned scope.

In Workday HCM, organizations such as cost centers are assigned to workers during hire and job change events. To ensure data accuracy and governance, Workday provides two key configuration controls for organizations: default organizations and allowed organizations . While default organizations prepopulate values, only allowed organizations control which values are selectable .

To limit the list of cost centers that managers can select during the hiring process, you must configure the allowed organization on the supervisory organization . This configuration defines the specific cost centers that are valid for workers hired into that supervisory organization. By restricting the allowed cost centers, Workday ensures managers can select only from an approved list, preventing incorrect or unauthorized cost center assignments.

Configuring a default organization —whether on the supervisory organization or from the position—only sets an initial value. It does not prevent the manager from changing the cost center to another valid option. Therefore, options B and C do not meet the requirement to limit selection. Option D is incorrect because job profiles are not used to control organizational assignments such as cost centers; they define job architecture, not financial or organizational governance.

From a Workday Pro HCM best-practice perspective, allowed organizations are the primary mechanism for enforcing organizational assignment rules at the time of hire. Applying this configuration at the supervisory organization level ensures consistent cost center usage for all workers hired into that organization while still allowing flexibility across different parts of the enterprise.

Therefore, the correct and fully Workday-verified answer is Configure the allowed organization on the supervisory organization .

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

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

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

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

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

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

This report is especially useful for:

Impact analysis before modifying eligibility rules

Auditing which compensation components rely on shared rules

Understanding eligibility dependencies across compensation configuration

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

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

The correct answer is Filter .

In Workday reporting, filters are used to narrow down report results based on specific data criteria, such as location, supervisory organization, or worker type. By applying a filter condition to include only workers whose location equals Toronto or Montreal , the report output dynamically restricts data to meet those parameters.

Filters can be added to both custom and advanced reports and can include multiple conditions combined with logical operators (AND/OR). Unlike Sort (which arranges results in a specific order) or Share (which defines who can view or edit the report), a Filter directly controls which data rows appear in the report output, ensuring that only relevant workers are displayed.

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.

In Workday, the Review Step within a business process is specifically designed to enable a user to review, edit, and approve information that was submitted by the initiator. This step allows designated participants to view the transaction details, make permissible edits, and approve or send it back for correction. It serves as an intermediate checkpoint before final approval or completion, ensuring data accuracy and compliance with policy.

By contrast, the Approval Step (Option C) only permits approval or denial — it does not allow data modification. The Consolidated Approval Step (Option B) groups multiple approval steps for simplification but also lacks edit functionality. The Integration Step (Option D) is used for system integrations and automated data transfers, not for user data review.

Thus, the Review Step uniquely provides both review and edit capabilities, which makes it ideal for validating and refining information early in the process lifecycle.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2) – Section: “Step Types and Participant Actions” and “Review Step Configuration.”