Free Practice Questions for Workday Workday-Pro-HCM-Core Exam

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

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.

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.

By default, Workday allows only one one-time payment per event when the Enable Multiple One-Time Payments tenant setting is not enabled. This behavior ensures strict control over one-time payment submissions and prevents multiple payments from being entered within the same transaction.

The Enable Multiple One-Time Payments setting in Edit Tenant Setup – HCM > Compensation explicitly removes this restriction and allows users to submit multiple one-time payments with the same reason and effective date. Since the business requirement is to limit submissions to a single payment, this setting must remain disabled.

Security configuration and business process rules do not control the number of one-time payment rows allowed in an event. They only manage access and approval flow.

Therefore, to enforce a single one-time payment per event, administrators must not enable the Multiple One-Time Payments setting, making option B correct.