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.

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.

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

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 staffing, position restrictions define which values are allowed when a worker is hired into a position. In this scenario, Worker Type is restricted to Employee, but Worker Subtype is blank. A blank optional restriction does not mean the manager cannot select a value; it means the value is not restricted by that specific field. Because Worker Type is restricted to Employee, the available subtypes must be valid subtypes under the Employee worker type. The manager can therefore select any Worker Subtype that belongs to Employee, such as Regular or another configured employee subtype. The answer is not Employee because Employee is a worker type, not a worker subtype. Contingent Worker is incorrect because it is a different worker type and is excluded by the Employee restriction. Any subtype of the Contingent Worker worker type is also incorrect because contingent worker subtypes are not valid when the position is restricted to Employee. The restriction framework narrows subtype choices through the selected worker type. Therefore, any subtype of the Employee Worker Type is correct. Reference topics: Staffing, Position Restrictions, Worker Type, Worker Subtype, and position-based hiring controls.

In Workday, field-level visibility during business processes—especially for self-service events—is controlled through Optional Fields configuration, not security domains. The Request One-Time Payment for Self process has its own optional field settings that allow administrators to show or hide specific fields for employees.

To prevent employees from modifying sensitive options such as Gross Up and Send to Payroll, administrators must configure Optional Fields specifically for the Request One-Time Payment for Self process and hide those checkboxes. This preserves the self-service capability while enforcing governance and preventing unintended financial impact.

Removing security domain access would block employees from initiating the process entirely, which does not meet the requirement. Configuring optional fields on the administrator-driven Request One-Time Payment process would not affect self-service behavior.

Therefore, the correct and precise solution is to configure Optional Fields for Request One-Time Payment for Self and hide the fields, making option D correct.

In Workday HCM, organizations such as Company are used extensively during hiring, job changes, and other staffing events. To control how an organization is presented and selected during these processes, Workday provides two important configuration concepts: default organizations and allowed organizations . Understanding the distinction between these two is essential to achieving the desired behavior.

If Company 1000 needs to be both automatically selected and the only selectable option during the hiring process, it must be configured as both the default and allowed organization . Setting Company 1000 as the default organization ensures that it is pre-populated on the hire event, reducing data entry and minimizing user error. However, default alone does not restrict users from changing the value.

To ensure that Company 1000 is the only company that can be selected , it must also be configured as an allowed organization . Allowed organizations define which values are valid and selectable for a given organization type. By limiting the allowed organization list to Company 1000, Workday prevents users from selecting any other company during the hiring process.

Option A is incomplete because configuring an organization as default does not prevent other companies from being selected. Option D is also insufficient because allowed organization alone does not ensure the value defaults automatically. Option C is unrelated, as superior and subordinate relationships define hierarchy, not selection behavior.

From a Workday Pro HCM best-practice standpoint, combining default and allowed organization configuration provides both efficiency and control. Therefore, the correct and fully verified answer is Configure it as the default and allowed 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 .