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.
Reference: Workday Pro HCM - Security Configuration and Administration, "User-Based Security Group Behavior and Permissions" section.

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

In Workday HCM, proration based on an employee's scheduled hours (such as part-time versus full-time workers) is controlled through theApply FTE%configuration within a salary plan. FTE (Full-Time Equivalent) represents the ratio of an employee's scheduled hours to the standard full-time schedule, and Workday uses this value to proportionally calculate compensation.
When theApply FTE%box is checked on a salary plan, Workday automatically prorates the compensation amount based on the employee's FTE. For example, if a salary plan amount is defined as $100,000 annually and the employee is working at 50% FTE, Workday will calculate and pay $50,000. This ensures fair and consistent compensation aligned with scheduled working hours.
Eligibility rules determinewhocan receive a plan, nothow muchthey receive. TheExclude from Meritoption only controls whether a plan is included in merit processes and has no impact on proration. Compensation elements connect compensation to payroll earnings but do not control proration logic.
Therefore, checking theApply FTE%box is the correct and Workday-recommended method for configuring proration based on scheduled hours, making option D the correct answer.

In Workday, eligibility rules are evaluatedsequentially, andperformance optimizationis achieved by placing themost restrictive condition first. This minimizes the number of records evaluated in subsequent conditions.
In this scenario:
* Only5 employeesmeet the job family criterion
* 50 employeesmeet the organization criterion
To optimize performance, the rule should first evaluatejob family, which immediately narrows the population to a smaller subset. The organization criterion is then evaluated against this reduced population.
Placing organizational membership first would cause unnecessary evaluation of a much larger group, negatively impacting performance. Workday does not automatically sequence eligibility conditions, and removing criteria would violate the business requirement.
Therefore,job family should precede organizational membership, making optionDcorrect.

In Workday HCM, consolidated approvals are used within business process definitions to reduce approval fatigue by grouping multiple related approval steps into a single task for the approver. This is especially useful for senior leaders, such as HR executives, who otherwise might receive several separate approval tasks for the same transaction-such as hire details, compensation, and organization assignments.
When you add a Consolidated Approval step to a business process, that step alone does not define what information is presented to the approver. To complete the configuration and make the consolidated approval functional, you must also complete the Configure Consolidated Template task. This task defines the approval layout and content, specifying which sections, fields, and business process steps are grouped and displayed together in the single approval task.
Without configuring the consolidated template, Workday does not know how to combine the approval content, and the consolidation will not behave as intended. The template controls the user experience for the approver and ensures all required information is reviewed in one place.
The other options do not meet this requirement. Maintain Step Conditions controls when a step runs but does not define consolidation behavior. Configure Consolidated Approval is not a delivered standalone task; consolidation is driven by the step and its template. Maintain Step Delay controls timing, not task grouping.
From a Workday Pro HCM best-practice perspective, adding a consolidated approval step must always be paired with Configure Consolidated Template to complete the setup. Therefore, the correct and Workday- verified answer is Configure Consolidated Template.