What situation would require your company to create a second benefit group?
Correct Answer: D
Explanation:
The correct answer is D because a second benefit group is typically required when a distinct worker population must follow a different overall benefits structure or administration cycle. In an acquisition scenario, newly acquired employees may need separate eligibility handling, separate plan year alignment, and a different open enrollment schedule from the existing workforce. Since benefit groups are used to organize broad populations that share common benefit administration rules, creating a separate group is the appropriate way to manage that difference.
Option A is not the best answer because workers who are not benefits-eligible can generally be excluded through eligibility rules rather than requiring an entirely separate benefit group. Option B describes a plan-specific eligibility condition, which is normally handled through plan eligibility rules, not by creating a new benefit group. Option C may also be addressed through location based eligibility at the plan level when only one specific medical plan differs. A second benefit group is most appropriate when the difference affects the broader benefits framework, such as enrollment timing, plan administration, or population-wide setup. That is why a separate open enrollment period for an acquired workforce justifies creating another benefit group.
Question 2
When the Finalize Open Benefit Events action closes an overdue benefit event, Workday defaults employees into their current elections or to waive. Where do you configure this defaulting logic?
Correct Answer: A
Explanation:
The correct answer is A because the Coverage Rules tab within the Enrollment Event Rule is where Workday defines how elections are defaulted when an employee does not take action during a benefit event. This includes scenarios such as overdue events that are finalized using the Finalize Open Benefit Events process. The system uses the defaulting logic configured in this tab such as “Default to Current Elections or Waive” to determine whether existing elections are carried forward or coverage is waived.
Option B is incorrect because the Enrollment Event Type defines the nature of the event and triggering conditions, but it does not control election defaulting behavior. Option C is also incorrect because the Loss of Coverage tab is used to manage coverage termination scenarios, not default election outcomes. Option D is incorrect because benefit plan configuration defines plan-specific details but does not control how elections default when no action is taken during an event. Therefore, to manage how Workday assigns elections when events are closed without employee input, the configuration must be set on the Coverage Rules tab of the Enrollment Event Rule .
Demo Practice Mode
You are viewing only the questions marked as Demo.