Workday provides a wide range of standard delivered reports to support workforce analysis, job architecture review, and organizational planning. When the requirement is to view job profile details , the correct Workday-delivered standard report is the Job Catalog . The Job Catalog report is specifically designed to display detailed information about job profiles that exist in the tenant.

The Job Catalog report presents comprehensive job profile attributes such as job title, job family, job family group, job category, management level, worker type eligibility, and other job architecture–related fields. This report is commonly used by HR administrators, compensation teams, and organizational design partners to review and validate job structures across the enterprise. Because job profiles are foundational objects in Workday HCM, the Job Catalog serves as the primary reporting tool to analyze and audit these profiles.

Other options do not meet this requirement. Find Workers focuses on worker data and employment details, not job profile configuration. Job History reports historical job changes for workers and does not display standalone job profile definitions. All Jobs typically reflects jobs held by workers or staffing data rather than the underlying job profile setup.

From a Workday Pro HCM perspective, understanding the distinction between job profiles and worker job assignments is critical. The Job Catalog report aligns directly with job architecture governance and supports reporting needs related to job design, standardization, and compliance. Therefore, the correct and fully Workday-verified answer is Job Catalog , as it is the standard report that displays detailed job profile information.

In Workday HCM, business process templates define the foundational structure of a business process, including the types of steps that are available to be configured. When administrators need to determine which action steps —such as approvals, To Do steps, notifications, integrations, or subprocesses—can be added to a specific business process, the correct Workday-delivered report to use is View Business Process Template .

The View Business Process Template report displays the delivered template for a given business process and outlines all supported step types and actions that Workday allows for that process. Because templates are system-delivered and cannot be modified, this report serves as the authoritative reference for understanding what configuration options are available before adding or modifying steps in a business process definition.

The other options do not fulfill this purpose. Business Process Security Policy for Functional Area and Domain Security Policies for Functional Area focus on security access and permissions, not step availability. Business Process Configuration Options is used to identify which business process definition applies to specific organizations, not which step types can be added.

From a Workday Pro HCM best-practice perspective, administrators should always consult the View Business Process Template report before designing or troubleshooting business process configurations. This ensures that changes align with Workday’s delivered framework and prevents configuration errors caused by attempting to add unsupported step types.

Therefore, the correct and Workday-verified answer is View Business Process Template , as it identifies which action steps can be added to a business process.

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

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.

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 HCM, compensation grades are a foundational component of the compensation framework and are primarily used to define pay ranges (minimum, midpoint, and maximum) for roles within the organization. These grades are typically associated with job profiles, positions, or job families to ensure internal equity and market competitiveness.

From a transactional perspective, compensation grades guide users with appropriate security access —such as HR Partners or Compensation Partners—when entering or proposing compensation amounts during staffing and compensation events. When a worker is hired, promoted, transferred, or receives a compensation change, the assigned compensation grade determines the acceptable pay range that can be entered in the transaction. This ensures consistency, compliance with company policy, and alignment with compensation strategy.

Compensation grades do not calculate compensation basis, connect compensation to payroll earnings, or determine overtime eligibility. Those functions are handled by compensation basis rules, payroll mappings, and time tracking or FLSA status configurations, respectively. Instead, compensation grades act as reference structures that inform and constrain compensation entry, often working in conjunction with compensation plans and guidelines.

Additionally, compensation grades can be used in reporting and analytics to compare compensation across roles and to identify exceptions where pay falls outside the defined range. Overall, their primary purpose is to provide guidance and controls for entering specific pay rates , making option D the correct answer according to Workday Pro HCM best practices.

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

In Workday, the ability to share a report depends on a user or group’s security access to the report’s data source and data source filters . This ensures that only authorized individuals can view the report’s content, even if they have the link or the report is shared with them directly.

Data sources define what underlying information a report can pull (e.g., Worker, Position, Organization). Security policies tied to those data sources control who can access or view specific data fields. Therefore, even if a report is shared broadly, users can only see results their security permissions allow.

Options A, B, and D are incorrect because Workday security doesn’t evaluate “business reasons” or “tags” for access — it enforces data-source–based controls. Field-level access is governed by the domain security policy within the data source.

Reference (Paraphrased Source):

Workday Pro HCM Core – Reporting Configuration Guide (2023R2), Section: “Report Sharing and Security Dependencies.”

In Workday, when an organization needs to change only compensation details —such as base salary—without affecting job, position, organization, or other worker attributes, the correct task is Request Compensation Change . This task is specifically designed for standalone compensation updates .

The Transfer, Promote or Change Job task is used when job-related attributes change and should not be used for compensation-only updates. Request Grade Change modifies the employee’s compensation grade but does not directly update salary amounts. Request One-Time Payment is limited to non-recurring payments and does not affect base pay.

Request Compensation Change ensures:

No job or organizational data is altered

Proper compensation validations and guidelines apply

Accurate audit tracking and approvals are enforced

Therefore, Request Compensation Change is the correct and Workday-recommended task for ad hoc salary changes.

In Workday, allowance plan profiles are designed to localize plan targets based on eligibility criteria. However, a key rule is that each employee can match only one profile . When an employee meets the eligibility criteria for multiple plan profiles , Workday cannot determine which profile amount to apply and therefore defaults to the plan’s base default value , which in this case is zero.

In this scenario, the plan uses both management level and location as eligibility criteria across multiple profiles. If these criteria overlap and are not mutually exclusive, employees may qualify for more than one profile simultaneously.

Workday does not throw an error in this situation; instead, it applies the plan’s default value to avoid ambiguity. In-progress compensation events do not affect defaulting logic, and having multiple compensation packages does not cause zero defaulting. A missing eligibility rule would apply the default to everyone, not just some employees.

To resolve this issue, administrators must ensure that plan profile eligibility rules are mutually exclusive so that each employee qualifies for exactly one profile.

Therefore, option B is the correct answer.

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.