The correct answer is D because requiring supporting documentation during a life event submission is controlled through the business process framework , specifically within the Change Benefits business process . Workday allows administrators to enforce rules such as mandatory attachments by configuring a validation rule on the business process step. This ensures that when an employee submits a life event, the system checks for the presence of an attachment and prevents submission if the requirement is not met.

Option A is incorrect because the Route to Benefits Partner checkbox only determines whether the event is routed for review by a benefits administrator and does not enforce document attachment requirements. Option B is unrelated, as Do Not Reprocess controls event reprocessing behavior. Option C is also incorrect because Worker Selectable determines whether employees can initiate the event, not whether attachments are required. To enforce compliance and ensure documentation is provided at submission, the requirement must be configured using a validation rule within the Change Benefits business process.

The correct answer is A because Health Savings Accounts (HSA) and Flexible Spending Accounts (FSA) typically require active re-enrollment each plan year , meaning they do not automatically carry forward prior elections. In Workday, this behavior is controlled through the Defaulting Rules on the Coverage Rules tab of the Enrollment Event Rule. By selecting Default to Waive , the system ensures that if an employee does not take action during Open Enrollment, their election for these plans will default to waived status, effectively ending their participation for the new plan year.

Option B is incorrect because Default to Current Elections or Waive would retain prior elections if no changes are made, which contradicts the requirement that HSA and FSA should not remain active without explicit enrollment. Option C is also incorrect because reinstating previous elections would automatically continue participation. Option D is not relevant because provider or classification defaulting does not control whether coverage continues or is waived. Therefore, to enforce active enrollment and prevent automatic carryover, the correct configuration is Default to Waive .

The correct answer is D because in Workday, employer match contributions for retirement plans are typically configured using a separate match plan rather than being embedded directly within the employee contribution plan. This design allows for greater flexibility and control over eligibility, contribution rules, and plan dependencies. By creating a distinct 401(k) match plan, administrators can define specific employer contribution logic, such as dollar-for-dollar matching up to a defined percentage, and then link it to the primary 401(k) savings plan.

A cross plan dependency rule ensures that when an employee elects the base 401(k) plan, the corresponding employer match plan is also triggered or made available. This approach supports accurate enrollment behavior and maintains clear separation between employee and employer contributions for reporting and processing purposes. Option A and B incorrectly shift responsibility outside Workday configuration, while Option C oversimplifies the setup and does not reflect how employer matching logic is structured within the system. Therefore, using a separate match plan with dependency rules is the correct and standard approach.

The correct answer is A because the requirement is to give all employees a unified open enrollment experience while restricting only two specific plans to the acquired population. In Workday, when the broader enrollment structure should remain the same for everyone, the preferred design is to keep workers in a single benefit group and use benefit plan eligibility rules to control access to individual plans. This preserves a consistent enrollment flow, rate frequency presentation, and general benefits framework while still limiting the two acquired-population plans to the correct employees.

Option B is incorrect because leaving the plan eligibility rule blank would make those plans available to everyone in the benefit group. Option C is not the best design because creating separate benefit groups introduces a broader split in the benefits framework, which can lead to a less unified enrollment experience and additional administrative complexity when only two plans need to differ. Option D is also incorrect because manual assignment is not the standard scalable configuration approach in Workday Benefits. Plan-level eligibility is the correct method when only selected plans must be restricted within a shared enrollment structure.

The correct answer is B because Workday coordinates overlapping benefits events primarily based on the benefit event date , not simply on the date the events were submitted. In this scenario, both the birth event and the administrative correction relate to the same employee, but the administrative correction has a benefit event date of June 20 , which is earlier than the birth event submission date of July 1. When Workday encounters multiple events that may affect the same benefits records, it gives priority to the event with the earlier effective event date and places the later event on hold until the earlier-dated event is resolved.

This sequencing protects the integrity of coverage elections, effective dates, and deductions by ensuring changes are processed in the correct chronological order. Option A is incorrect because Workday does not place the earlier event on hold when it should drive the foundational coverage timeline. Option C is incorrect because submission order is not the governing factor here. Option D is also incorrect because Workday does not combine these into a hybrid event. The later event is held until the earlier-dated event is processed.

The correct answer is C because Workday controls how long an employee has to report a self-service life event through the Days to Enroll value combined with the Employee Cannot Report After Days to Enroll setting on the Enrollment Event Type. When Days to Enroll is set to 30 , the system establishes a 30-day reporting window from the event date. Selecting Employee Cannot Report After Days to Enroll enforces that limit by preventing employees from initiating or submitting the event after the allowed timeframe has passed.

Option A is incorrect because Do Not Reprocess relates to event reprocessing behavior and does not limit how long an employee has to report the event. Option B is also incorrect because Do Not Reprocess Future Events manages future event handling rather than self-service submission timing. Option D is unrelated because the Reinstatement Event configuration is used for rehired workers or reinstatement scenarios, not for setting the reporting window for standard employee-initiated life events. To restrict employee self-service benefit event initiation to within 30 days, the correct setup is Days to Enroll plus the Employee Cannot Report After Days to Enroll control.

The correct answer is A because Enrollment Instructions in Workday are used to present employees with guidance, explanatory text, and helpful links during the benefits enrollment experience. This is the appropriate configuration area when an organization wants to provide additional benefit information, direct workers to carrier or vendor websites, or include messaging that supports enrollment decision-making. These instructions enhance the employee experience by making relevant information available at the point where workers review and elect their benefits.

Option B is incorrect because Enrollment Event Types define the type of benefits event, such as open enrollment or a life event, but they are not primarily used to store employee-facing informational content and links. Option C is unrelated because Health Care Coverage Targets are used for plan design and contribution strategies, not communication content. Option D is also incorrect because Benefit Coverage Types classify benefit offerings and do not control enrollment messaging. When the goal is to display helpful descriptions, external site references, or decision-support text during benefits enrollment, the correct configuration task is Maintain Enrollment Instructions .