Pass Workday-Pro-HCM-Core Exam Guide

The correct answer is B – Have an open, approved position.

In Workday’s Position Management staffing model, each hire is tied to a specific position. Before a worker can be hired, a position must exist, be opened, and be approved through the appropriate business process.

Once a position is approved, it becomes available for the Hire or Add Job process. Without an approved position, no worker can be assigned under that supervisory organization. The position serves as the structural foundation for tracking headcount, job details, and time-to-fill metrics.

Options A and C refer to configuration prerequisites, but the question specifically focuses on the operational readiness to hire. Option D is incorrect because a hire cannot occur until after a position exists.

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

The correct answer is D – User-based.

User-based security groups are manually assigned to specific users and are typically used for administrative or audit-level access. They can be configured as unconstrained, granting full visibility across all organizations and data in the tenant.

For users responsible for security oversight or auditing, a user-based group (such as Security Administrator or Security Auditor) is appropriate. This group can be assigned to the necessary domain and business process security policies that control access to security reports and configuration data.

Other group types (e.g., role-based or segment-based) depend on organizational context and cannot provide unrestricted system-wide visibility, making a user-based group the correct option for full security monitoring.

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