In Workday business process terminology, the subject of a business process event is the Target. The target is the person, position, organization, or object that the business process is acting on. For example, in a Hire event, the target is the worker being hired; in a Change Job event, the target is the worker whose job is being changed; and in an organization event, the target may be the organization being updated. The Initiator is the user or process that starts the event, so it describes who launched the process rather than what the process is about. Instance is a general Workday object occurrence and does not specifically identify the subject of a business process event. Primary Business Object refers to the underlying object type associated with a business process definition or template, but it is not the transactional subject term used in routing and event context. Understanding target is important because business process routing, security, notifications, and condition rules often evaluate fields relative to the target. Therefore, Target is the correct answer. Reference topics: Business Processes, Business Process Event Context, Target Object, Initiator, and Primary Business Object.

The correct answer isA - Employee-as-Self.
Employee-as-Selfis adelivered Workday user-based security groupautomatically assigned to all active workers within the tenant. This group allows employees toview and update their own personal data, such as home address, phone number, emergency contacts, and other self-service information.
The permissions for this group are defined indomain security policiesrelated to personal data, such asWorker Data: Personal InformationandWorker Data: Home Contact Information. Employees only have access to modify their own records, not those of others.
This self-service model is central to Workday's HCM design, empowering employees to maintain accurate personal information without administrator intervention.
Reference:Workday Pro HCM -Security and Self-Service Fundamentals, "Employee-as-Self Delivered Security Group" section.

In Workday,plan profile eligibility rulescontrol which employees qualify for a compensation planduring evaluation events, such as Hire, Job Change, or Compensation Change. When eligibility rules are updated, Workday doesnot immediately retroactively remove compensation. Instead, the system evaluates eligibility at thenext compensation-related business process.
In this scenario, Sales employees were explicitly removed from theSales / Australiaplan profile eligibility. As a result, those employees no longer qualify for the allowance. During the next eligible event-such as a job change or compensation review-Workday will automaticallyremove the allowancefrom employees who no longer meet the eligibility criteria.
Workday does not generate system errors due to eligibility rule changes, nor does it automatically enroll unrelated populations. Additionally, allowances are not mass-added or removed immediately without a triggering event unless a mass operation is run.
Therefore, the correct outcome is thatSales employees will automatically be removed from the plan, making optionDcorrect.

During a Change Job event, Workday re-evaluates compensation plan eligibility based on the employee's updated attributes, such as location. Even if an allowance plan has no eligibility rules, it can still be removed during the Propose Compensation Change step if not explicitly retained.
The correct way to ensure that an intentionally assigned allowance plan remains on the employee's record is for the compensation partner to restore or re-add the plan during the Propose Compensation Change subprocess of the Change Job transaction. This keeps the correction within the same business process and ensures accurate audit tracking.
Request Compensation Change is a standalone process and should not be used mid-transaction. Plan adjustments and rollouts are bulk tools and are not appropriate for correcting a single employee during an in- flight job change.
Therefore, restoring the plan during Propose Compensation Change is the correct and Workday-supported approach, making option D correct.

The correct answer is C - All Employees.
Workday delivers the All Employees security group as a predefined (delivered) user-based security group that automatically includes every active worker within the tenant. This group grants broad access to non- sensitive information that all workers should be able to view-such as organizational structure, reporting relationships, job profiles, and public worker details (like name, title, and location).
The All Employees group is fundamental for system usability and transparency, ensuring employees can navigate the org chart, identify colleagues, and understand reporting hierarchies without compromising confidential data.
Workday recommends maintaining this group's configuration in its default state to avoid restricting essential information visibility. Security administrators may, however, further refine domain policies to exclude sensitive data while preserving general organization structure access.
Reference: Workday Pro HCM - Security Fundamentals, "Delivered Security Groups: All Employees, All Contingent Workers, and All Users" section.