Workday Workday-Pro-HCM-Core Workday Pro HCM Core Certification Exam Exam Practice Test

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.

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.

Default compensation on a job requisition allows organizations to predefine compensation plans and values that automatically flow into the Offer event. The primary advantage is consistency—every candidate hired from the same requisition starts with the same baseline compensation configuration.

This ensures fairness, reduces recruiter error, and accelerates the offer process by minimizing manual data entry. Default compensation on requisitions is especially valuable when hiring multiple candidates for the same role, location, and level.

Position-based compensation is configured separately and applies regardless of requisition. Viewing eligible plans is unrelated to default compensation. While employees hired into a position may share compensation, requisition defaulting specifically governs applicant and offer behavior.

Therefore, option B is the correct answer.

In Workday HCM, it is critical to understand the distinction between job management and position management, as worker movement and vacancy behavior differ significantly between the two staffing models. In a job management organization, workers are hired into jobs, not into discrete position objects. Jobs in this model do not represent fixed headcount slots; instead, they are simply descriptive attributes assigned to workers.

When a worker in a job management organization retires, the worker’s job assignment ends with the worker. Because job management does not maintain a separate position record, there is no concept of a job remaining open, being frozen, or awaiting backfill. Once the worker exits the organization, the job itself effectively no longer exists unless another worker is hired into the same job profile through a separate hiring event.

Option A is incorrect because leaving a role open for backfill applies only to position management, where positions are persistent objects that can remain vacant and be refilled. Option B is invalid, as Workday does not support overlapping jobs in this manner. Option D is also incorrect because freezing applies to positions, not jobs.

From a Workday Pro HCM best-practice perspective, this behavior reinforces why job management is often used for organizations that require greater flexibility, such as high-volume or seasonal hiring. There is no headcount lock tied to individual jobs, and staffing levels are managed through hiring rules and organizational limits rather than position vacancies.

Therefore, the correct and Workday-verified outcome is that the job no longer exists once the worker retires in a job management organization.

In Workday HCM, business process definitions control how transactions such as hires, job changes, terminations, and approvals flow through the system. Each business process consists of multiple steps, including initiation, approvals, notifications, and system actions. Among these, the completion step plays a critical and often misunderstood role.

The primary purpose of the completion step is to indicate when Workday saves, finalizes, and commits the transaction data to the system. Until the completion step is reached, information entered during the business process remains in a pending state and is not fully written to the database. Once the completion step executes, the transaction becomes effective, and all related changes—such as worker status updates, organization assignments, compensation changes, or security updates—are officially applied.

Option A is incorrect because automatic completion of steps is controlled by step type and routing rules, not by the completion step itself. Option B is incorrect because exit condition rules are evaluated at various points during the process to determine whether steps should be skipped, not specifically at completion. Option D is unrelated, as the completion step does not control when specific roles receive approvals.

From a Workday Pro HCM perspective, the completion step is essential for ensuring data integrity and transactional accuracy. It marks the point at which the business process is considered finished and all downstream effects—such as reporting, payroll, benefits eligibility, and security changes—can occur reliably.

Therefore, the correct and Workday-verified purpose of the completion step is to indicate when Workday saves or commits information.

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

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

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

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

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

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

Workday’s Business Process Notification functionality enables administrators to configure custom notifications that are automatically sent to users when specific BP events occur. The correct statement is that you can use text and fields in the body of the notification message (Option B).

Notification templates support the insertion of business process fields, allowing dynamic content such as worker names, event types, or effective dates to be automatically populated in the message. This helps personalize communications and provide clear, actionable context.

Option A is incorrect because notifications can be sent to both internal users and external participants (such as vendors or contingent workers) if appropriately configured.

Option C is incorrect — you can configure multiple status triggers (e.g., In Progress, Denied, Completed).

Option D is incorrect since notification triggers are predefined by Workday, and while you can configure their messages and recipients, you cannot create entirely new trigger types.

Therefore, the main strength of this feature lies in its customizable content, dynamic field integration, and multi-status trigger support.

Reference (Paraphrased Source):

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

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

In Workday, the ability to assign compensation plans—regardless of employee eligibility—is controlled by security domains, not by business process steps or guidelines. The Worker Data: Compensation Plan Type security domain governs access to specific types of compensation plans, such as allowance plans, salary plans, or one-time payments.

When a user (such as a compensation partner) has broader access through this domain, they can assign compensation plans even when eligibility rules are not met. This is commonly granted to advanced compensation roles to allow exceptions, corrections, or special cases during approvals.

Manager roles are typically restricted by eligibility, which is why the manager can only assign the car allowance. The compensation partner’s elevated security allows them to override eligibility.

The “Select Any Compensation Package” option controls package selection, not plan-level overrides. Guidelines and manager domains do not grant override capability.

Therefore, the correct security domain is Worker Data: Compensation Plan Type, making option D correct.

In Workday HCM, job profiles are core configuration objects that define the general characteristics of work performed in the organization. Their primary function is to standardize and describe roles consistently across the enterprise, regardless of whether the organization uses job management, position management, or a hybrid staffing model. Job profiles capture high-level attributes such as job title, job family, job family group, management level, job category, worker type eligibility, and other structural elements that describe the nature of the work.

The correct statement is that job profiles include the general characteristics of position. In position management organizations, every position is associated with a job profile, which supplies these shared characteristics. This ensures that multiple positions performing the same type of work are aligned to the same job definition, supporting consistency in staffing, compensation, reporting, and organizational analysis.

Option A is incorrect because job profiles are not optional; they are foundational to staffing and compensation processes. Option B is inaccurate because job profiles are not assigned only to jobs—they are used across both job management and position management models. Option D is also incorrect because while job profiles are required for creating positions, that statement describes a dependency, not the function of job profiles.

From a Workday Pro HCM best-practice perspective, job profiles serve as the single source of truth for job architecture, enabling scalable workforce management, consistent reporting, and effective compensation governance. They allow organizations to evolve roles over time while maintaining structural alignment across workers and positions.

Therefore, the correct and Workday-verified function of job profiles is that they include the general characteristics of positions.

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

When creating a new supervisory organization that should inherit attributes such as staffing model, company, and cost center from an existing organization, you use the Create Subordinate task.

This task creates the new subordinate organization directly under a superior supervisory organization. It automatically copies inherited settings such as visibility, organization assignments, and staffing model, ensuring hierarchical alignment and simplifying setup.

Option B (Create Supervisory Organization) creates a brand-new top-level supervisory org without inheritance.

Option A (Assign Roles) only assigns role-based permissions after creation.

Option C (Assign Included Organizations) is used for related org relationships, not for hierarchical creation.

Thus, Create Subordinate is the correct task when the new org must inherit settings from a superior one.

Reference (Paraphrased Source):

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

When a Change Job event includes a compensation impact, Workday triggers the Propose Compensation Change subprocess. This subprocess allows users to review and update compensation plans, amounts, and guidelines as part of the job change.

Request Compensation Change is a standalone process used when compensation changes occur without a job change. Propose Compensation Offer and Propose Compensation Hire are tied to recruiting and hiring events, not internal transfers.

The Propose Compensation Change process ensures that compensation updates are evaluated with proper eligibility rules, guidelines, approvals, and audit tracking within the context of the job change.

Therefore, option D is the correct answer.

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

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

Options A, B, and C are incorrect:

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

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

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

Reference (Paraphrased Source):

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

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

The correct answer is A – Job families and job family groups are optional, but they can help organize and group job profiles.

Job Families and Job Family Groups are optional configuration elements in Workday, but they serve a key purpose in maintaining a structured, organized job framework. They enable the grouping of similar jobs for streamlined management in areas such as compensation, recruiting, reporting, and career development.

For instance, all technical roles (like Software Engineer, Systems Analyst, and Data Architect) might belong to the Information Technology Job Family, which in turn is part of the Technology Job Family Group.

While optional, using these structures provides consistency across departments, simplifies security and reporting filters, and supports analytics related to workforce planning and talent management.

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

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

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

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

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

The correct answer is D – Edit Hiring Restrictions.

In this scenario, the supervisory organization uses the Job Management staffing model (“no limit on the number of jobs”). Because there are no discrete positions, you control staffing limits through Hiring Restrictions rather than position-level restrictions.

The Edit Hiring Restrictions task allows administrators to specify criteria such as:

Worker Type (Employee, Contingent Worker)

Location

Job Family / Job Profile

Time Type (Full-time, Part-time)

This ensures that hiring aligns with organizational policy even when positions are not individually managed. For organizations using Position Management, the corresponding task would be Edit Position Restrictions instead.

From the Workday Module 2 Binder:

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

– Workday Module 2 Binder, Security Configuration Section

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

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

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

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

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.

A unit salary plan in Workday is specifically designed to support compensation that varies based on a measurable unit of output, such as miles driven, items produced, or— in this case—kilometers flown. This plan type allows compensation to scale proportionally with the quantity of units, making it ideal for roles where pay increases directly with activity or performance volume.

For airplane pilots, compensation based on kilometers flown is not a fixed allowance or a one-time payment. Instead, it represents variable earnings tied to ongoing work output, which aligns exactly with the purpose of a unit salary plan. Workday allows administrators to define a rate per unit, and the system can calculate estimated compensation by multiplying the rate by the expected number of units. This calculated amount can then be displayed in offer letters, providing transparency and clarity to candidates.

A period salary plan is used for fixed salaries distributed over defined pay periods and cannot model variable, unit-driven earnings. A one-time payment plan is intended for bonuses or ad-hoc payments and does not support ongoing estimation. A unit-based allowance plan is typically used for reimbursements or allowances, not base compensation tied to work output.

Therefore, the unit salary plan is the correct choice for modeling and presenting estimated wages based on kilometers flown, making option B the correct answer.

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

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

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

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

As per the Workday Module 2 Binder:

“Validation condition rules are used in approval steps to determine whether the step should occur or be skipped based on specific conditions.”

– Workday Module 2 Binder, Business Processes Section

Situation: In a business process in Workday, organizations want certain steps (like approvals) to occur only if specific conditions are met—for example, skipping approval if the amount is under a certain threshold.

Task: Implement logic that dynamically controls the flow of a business process based on conditions.

Action: You apply a validation condition rule within an approval step. This rule evaluates defined criteria and determines if the step should be executed or bypassed.

Result: This enhances automation, improves efficiency, and reduces manual intervention in workflow execution.

Hence, approval steps are the specific step type in which validation condition rules can be added.

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.

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.

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.

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

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

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

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

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

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

Reference (Paraphrased Source):

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

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

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 HCM, condition rules are used within business process definitions to control when steps start, continue, or stop executing. When working with consolidated approvals, it is common to define stopping points so that once a required level of approval is met—such as approval by a vice president—the approval chain does not continue unnecessarily.

To stop a consolidated approval chain after a vice president approves the task, you must use an Exit condition rule. Exit conditions are evaluated after a step completes and determine whether the business process should continue to subsequent steps or stop processing additional steps. When the exit condition evaluates to true, Workday exits the process flow at that point.

This behavior makes exit conditions ideal for scenarios where hierarchical or role-based approval chains should end once a certain authority level has approved. In this case, once the vice president approval is completed, the exit condition prevents additional approvers from receiving the task.

The other condition types do not meet this requirement. Entry conditions control whether a step starts at all but do not stop a process once it has begun. Validation conditions are used to enforce data accuracy and prevent submission if requirements are not met. While Running conditions are evaluated while a step is in progress and are typically used to cancel or reroute steps if circumstances change.

From a Workday Pro HCM best-practice perspective, exit condition rules are the correct and recommended method for ending approval chains early when business requirements are satisfied. Therefore, the correct and Workday-verified answer is Exit

In Workday, condition rules determine whether a step executes, routes, or triggers based on defined criteria such as job attributes, location, or organization. There are two primary ways to create or associate condition rules directly from a business process step:

Create Condition Rule (Option C) – allows a user to define a new condition rule directly from within the step configuration screen. This opens the condition rule editor where criteria can be defined using Workday attributes.

Maintain Step Conditions (Option D) – provides the option to assign existing condition rules or create new ones for the selected step. This is often used to ensure that certain steps run only when specific business conditions are met.

Options A and B are incorrect:

Maintain Advanced Routing Restrictions (A) is related to security routing and worktag-based participant logic, not condition rule creation.

Maintain Step Delay (B) controls timing (delaying execution by hours or days), unrelated to conditions.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Framework and Condition Rule Configuration Guide (2023R2) – Sections: “Creating and Maintaining Condition Rules” and “Step-Level Configuration.”

In Workday HCM, it is essential to distinguish between domain security and business process security, as each controls different aspects of system access. Domain security governs data visibility, such as whether a user can view compensation information or run reports. Business process security, on the other hand, controls transactional actions, such as initiating or completing tasks like Create Compensation Package.

In this scenario, the worker is able to run the Compensation Package report, which indicates they have permission to view compensation-related data. However, they cannot access the Create Compensation Package task, which is a transactional action within a business process. This clearly shows the worker has view-only access to the domain but does not have business process initiation permissions.

The correct permission type is View on a domain security policy. This level of access allows users to view data and run reports associated with that domain, but it does not allow them to modify data or initiate related business processes.

Option A is incorrect because Initiate permissions on a business process security policy would allow the worker to start the Create Compensation Package task. Option B is incorrect because View and Modify domain access would allow data changes, which is not supported by the scenario. Option C is incorrect because View All on a business process security policy would relate to visibility within business processes, not report execution.

From a Workday Pro HCM security design perspective, this scenario demonstrates the separation of duties principle: reporting access is granted through domain security, while transactional authority is tightly controlled through business process security. Therefore, the correct and Workday-verified answer is View on a domain security policy.

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

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

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, role-based (constrained) security groups control access to business processes and data based on an individual’s organizational assignments. The Access Rights to Organizations setting determines which organizations—and therefore which workers—fall within the scope of responsibility for users assigned to that security role.

When the Access Rights to Organizations setting is configured as Current Organization and All Subordinates, the HR Partner assigned to a supervisory organization gains security access to that organization and every subordinate organization beneath it in the hierarchy. This access applies regardless of whether subordinate organizations have their own HR Partners assigned.

In the context of employee terminations, this means HR Partners are responsible for approving termination events for employees who belong to the organization they directly support as well as employees in any subordinate supervisory organizations. Workday evaluates the worker’s organizational membership at the time of the transaction and routes the business process approval accordingly.

Options B and C are incorrect because Workday does not limit approvals based on whether subordinate organizations have HR Partners or restrict access to a single subordinate. Option D is also incorrect because it ignores subordinate organizations entirely, which contradicts the selected access rights configuration.

From a Workday Pro HCM security design perspective, this setting ensures appropriate oversight and continuity by allowing HR Partners to support broader organizational segments without creating security gaps. It is commonly used in shared-services or regional HR models where HR Partners support entire organizational branches.

Therefore, the correct and Workday-verified answer is that HR Partners must approve termination events for employees in their assigned organization and all subordinate organizations.

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

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

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

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

In Workday, guideline warnings are used to alert users during compensation events when proposed compensation falls outside defined ranges. These warnings are tied to compensation basis configurations, not to informational metrics such as compa-ratio or position in range.

A compensation package relies on a primary compensation basis to evaluate pay ranges, limits, and guidelines. The primary compensation basis pay range defines the acceptable boundaries for compensation proposals and is where guideline warnings are configured.

Compa-ratio and position in range are derived analytics used for reporting and decision support; they do not drive validation or warnings. Segment ranges are used for guideline calculations but do not independently generate warnings.

By configuring guideline warnings on the primary compensation basis pay range, Workday ensures that users are alerted when compensation proposals exceed or fall below acceptable thresholds during Hire, Change Job, or Compensation Change processes.

Therefore, option D is the correct answer.