Workday Workday-Pro-HCM-Core Dumps

The correct answer is C – Domain Security Policy.

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

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

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.

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.

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 .

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

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, a configurable compensation basis is used when an organization needs to group multiple compensation plans—such as salary, commission, and bonus—for purposes of calculation, validation, guidelines, and reporting. This type of basis allows administrators to explicitly select which compensation plans are included and define how they interact.

For a sales team, compensation commonly consists of base salary, variable commission earnings, and incentive or bonus plans. A configurable compensation basis is the only option that supports combining these different plan types into a single, controlled compensation framework. It also allows ranking, eligibility rules, and advanced controls such as Manage Basis Total.

Compensation grades define pay ranges and are not used to aggregate compensation components. Calculated compensation bases derive values from formulas and are not appropriate when simply grouping plans. The delivered Total Salary and Allowances basis does not include commission plans and cannot be extended to meet this requirement.

Therefore, creating a configurable compensation basis that includes salary, commission, and bonus plans is the correct and Workday-recommended solution, making option A correct.

The Set Up Allowance Plan Adjustment task is specifically designed to update allowance plan amounts for existing employee assignments when plan targets change. Simply editing the allowance plan amount ensures new employees receive the updated value, but it does not automatically update existing employees already assigned to the plan.

By running the Allowance Plan Adjustment task and selecting Adjust to New Defaults , Workday evaluates all employees assigned to the plan and updates their allowance amounts to match the new default value of $3,500.

Manually updating employees through Request Compensation Change is inefficient and error-prone. Creating a new plan introduces unnecessary complexity and disrupts reporting continuity.

Therefore, the correct and Workday-recommended approach is to run Set Up Allowance Plan Adjustment and adjust to new defaults, making option D correct.

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

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

Options A, B, and D are incorrect:

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

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

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

Reference (Paraphrased Source):

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

The correct answers are B and C.

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

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

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

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

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.

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

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.

Advanced routing restrictions are used when a normal role-based routing rule would create an inappropriate assignment, such as routing a review step back to the person who initiated the transaction. In this scenario, the review step is assigned to the HR Partner, but if the HR Partner starts the Termination event, that same HR Partner should not complete the review. The requirement is to route the step to the terminated worker’s manager, which means the alternate assignee must be determined from the transaction target, not from the initiator’s own supervisory relationship. Therefore, the correct configuration is to exclude the initiator and specify the manager relative to the transaction as the alternate security group. Excluding the initiator without an alternate would leave the step without a valid participant in some cases. Specifying the manager of the excluded user could route to the HR Partner’s manager, which is not the business requirement. Excluding the prior approver addresses a different segregation-of-duties scenario. Reference topics: Business Processes, Advanced Routing Restrictions, Exclude Initiator, Alternate Security Group, and transaction-relative routing.

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 .

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

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

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

In Workday, compa-ratio is a calculated metric that compares an employee’s pay to the midpoint of their compensation grade range. While the calculation depends on grades and pay, its visibility is controlled through compensation package analytics settings .

If the compa-ratio is not visible when viewing worker compensation, the most likely cause is that the metric has not been enabled for display within the compensation package analytics configuration . Administrators must explicitly select which analytics—such as compa-ratio, position in range, or range penetration—are displayed to users.

Security policies control access to data but do not toggle metric visibility. Eligibility rules and job profile assignments affect calculation accuracy but not whether the metric is shown.

By enabling the compa-ratio option in compensation package analytics , Workday displays the metric consistently during compensation events.

Therefore, option B is the correct answer.

The correct task to assign someone as a leader of a new organization is " Assign Roles. " In Workday, each organization (e.g., Cost Center, Company, Supervisory Organization) can have one or more roles assigned to manage that organization’s transactions and activities. These roles might include Manager, HR Partner, Finance Partner, etc.

When creating a new organization or modifying an existing one, the “Assign Roles” task is used to designate the individuals who will hold specific responsibilities over that organization. This action ensures proper workflow routing, approvals, and visibility across business processes like Staffing, Compensation, and Financials. This is essential for cross-functional reporting and financial oversight.

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

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

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

Therefore, option D is the correct answer.

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

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

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

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

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

The correct answer is A – Employee-as-Self.

Employee-as-Self is a delivered Workday user-based security group automatically assigned to all active workers within the tenant. This group allows employees to view and update their own personal data , such as home address, phone number, emergency contacts, and other self-service information .

The permissions for this group are defined in domain security policies related to personal data, such as Worker Data: Personal Information and Worker Data: Home Contact Information . Employees only have access to modify their own records, not those of others.

This self-service model is central to Workday’s HCM design, empowering employees to maintain accurate personal information without administrator intervention.

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

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

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

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

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

The correct report is View Security for Securable Item .

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

This report provides detailed insight into:

The domain or business process associated with the securable item,

The related security policies ,

Which security groups currently have access, and

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

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

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.

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

The correct answer is C – Hiring Restrictions.

When a supervisory organization uses the Job Management staffing model (which has no limit on the number of jobs that can be filled), hiring is controlled through Hiring Restrictions rather than position management.

The Edit Hiring Restrictions business process must be configured before initiating hires to define:

Worker Type (Employee or Contingent Worker)

Location

Job Family and Job Profile

Time Type (Full-time or Part-time)

These restrictions determine what roles and worker types can be staffed in that supervisory organization. Unlike Position Management , there is no need to create or approve individual positions beforehand.

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

In Workday, compensation entered during the Offer event only carries forward to the Hire event if it is part of the compensation package associated with the job or position. Compensation packages define which plans—such as salary plans, allowance plans, and one-time payment plans —are eligible to flow through staffing events.

If a signing bonus is entered during Offer but not included in the compensation package, Workday treats it as an isolated entry that does not persist into Hire. This behavior is by design to ensure consistency and control over compensation structures.

Security policies, approval steps, and subprocess configuration do not control whether compensation carries forward between Offer and Hire. The determining factor is inclusion in the compensation package.

Therefore, to ensure the signing bonus carries forward, the Signing Bonus one-time payment plan must be included in the compensation package , making option A correct.

The correct answer is C – Position Management.

In Workday, Position Management is the staffing model used when an organization needs to track headcount, vacancies, and time-to-fill for each position individually. Each position represents a distinct job slot that must be filled by a worker, providing clear visibility into when a position is open, filled, or closed.

This model is ideal for organizations that require detailed tracking of resource allocation, workforce planning, and recruiting metrics such as “time to fill” . Because each position must exist before a hire can occur, Workday automatically records the date the position is opened and the date it is filled , allowing accurate reporting on recruitment cycle times.

In contrast, Job Management groups workers under jobs rather than individual positions and does not provide vacancy-level tracking, making it unsuitable for time-to-fill analysis.

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.

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.

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

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.

In Workday, configurable compensation bases allow organizations to control how compensation plans relate to one another and to enforce limits or proportions within a total compensation structure. The Manage Basis Total option is specifically designed to impose constraints on how much certain plan types can contribute relative to the overall compensation basis.

In this scenario, the business requirement is to ensure that salary plans do not exceed 50% of the total compensation for Indian employees. This requirement is achieved by enabling Manage Basis Total on the Total Cost (India) compensation basis and setting a maximum percentage of 50 for salary plans . This configuration enforces the rule automatically during compensation proposals and validations.

Changing the ranking of the compensation basis has no impact on percentage enforcement; rankings only determine precedence when multiple bases apply. Fixed compensation bases do not support proportional controls and would remove flexibility. Removing retirement plans would alter the total compensation calculation but would not guarantee the 50% salary cap.

Therefore, configuring Manage Basis Total with a salary plan maximum of 50% is the correct and Workday-recommended solution to enforce this business rule, making option B the correct answer.

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.

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

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.

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.

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.

Revenue and expense-related financial transactions in Workday are normally tracked through financial organization structures such as cost centers. When a business needs to group members of multiple organizations for reporting on revenue and expense activity, a Cost Center Hierarchy is the correct organization type. Cost centers identify where costs, expenses, and financial accountability are assigned. A hierarchy allows multiple cost centers to be rolled up for consolidated reporting, financial analysis, budgeting, and management review. A Region Hierarchy can group geographic regions, but geography is not the primary driver for revenue and expense reporting in this scenario. A Supervisory Organization Hierarchy is used for worker reporting relationships and staffing, not financial transaction grouping. A Location Hierarchy groups physical locations and may support workforce or facilities reporting, but it is not the appropriate structure for tracking financial transactions by revenue and expense. Therefore, the correct organization type is Cost Center Hierarchy. Reference topics: Organizations, Cost Centers, Cost Center Hierarchies, Organization Assignments, and financial transaction reporting.

In Workday, the Effective Date controls when the compensation change is legally and payroll-effective , while the Employee Visibility Date determines when employees can see the change in Workday.

In this scenario:

The increase must be effective March 1 for equity and payroll accuracy.

Employees should not see the change until after March 20 , when managers communicate it.

By setting:

Effective Date = March 1

Employee Visibility Date = March 21

Workday ensures the increase is included in payroll and historical records while remaining hidden from employees until the specified visibility date.

Using the transaction date or delaying the effective date would create payroll inaccuracies. Setting both dates to March 21 would make the increase effective too late.

Therefore, option D is the correct and compliant solution.

In Workday, compensation packages are used to group compensation plans that are presented and assigned during staffing events , such as Hire or Change Job. These packages are designed to include plans that are transactionally assigned and visible during compensation proposals.

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

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

Therefore, the only valid option is One-time payment plan , making option D correct.