Workday Updated Workday-Pro-HCM-Core Exam Questions and Answers by jannah

The correct answers are B, D, and E.

User-based security groups are groups in which membership is manually assigned to individual users. They are highly flexible and used primarily for administrative or elevated-access purposes.

(B) These groups can be either constrained or unconstrained. Constrained groups limit data access (for example, access only to workers in a particular supervisory org), while unconstrained groups provide broad system-wide visibility.

(D) These groups are commonly used for system administrators, payroll admins, or HR system owners, who require full access across tenants.

(E) Once a user is assigned to a user-based group, they automatically inherit access to all domains and business processes that the security group has permissions for.

Option A is incorrect because user-based groups are not always unconstrained; and C is incorrect because assigning users does not initiate a business process—it’s a configuration action managed through the Maintain Security Group Members task.

In Workday HCM, access to reports—whether standard or custom—is controlled by domain security permissions. Domain security governs what data a user can see or interact with, and different permission levels determine whether the user can only view data or also create, update, or retrieve it through integrations.

The Location Directory is a Workday-delivered standard report that displays location-related data, such as business sites, addresses, and associated attributes. Because this report is read-only and does not involve creating or updating data, the HR Auditor security group only needs View permission on the relevant Location domain to run the report successfully.

The View permission allows users to see data and run reports that reference that domain. It is the minimum permission required for reporting access and aligns with the typical responsibilities of an HR Auditor, whose role is to review and validate data rather than modify it.

The other permissions are not appropriate in this context. Modify and Put permissions would allow changes to location data, which exceeds auditor responsibilities and violates the principle of least privilege. Get permission is typically used for web services and integrations and does not apply to interactive report execution in the Workday user interface.

From a Workday Pro HCM security best-practice standpoint, assigning only View access ensures auditors can perform their oversight duties without risking unintended data changes. This approach supports compliance, audit integrity, and strong internal controls.

Therefore, the correct and Workday-verified domain permission required for an HR Auditor to run the Location Directory report is View.

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

A Consolidated Approval Chain Step allows multiple approval actions within a business process to be combined into a single, streamlined approval task. However, this step must be the final step before the completion step in a business process.

If the Consolidated Approval Chain appears after the completion step, Workday will trigger a critical error because the step order violates the BP framework rules. The system expects the consolidated approval to act as the last step to ensure that all approvals are received before the event finalizes.

Therefore, Option C is correct — a critical error occurs because the Consolidated Approval Chain Step must immediately precede the completion step, not follow it.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Consolidated Approval Chains and Step Sequence Rules.”

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.