Workday Pro Benefits Certification exam Workday Pro Benefits Exam Questions

Answer : A

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.

Answer : D

The correct answer is D because in Workday, when an employee initiates a life event such as the birth of a child through the Benefits and Pay Hub, the system launches the Change Benefits business process. This process is the central workflow used to capture and process benefit election changes resulting from qualifying life events. The birth event acts as the trigger, but the actual business process used to manage elections, review options, and submit changes is Change Benefits.

Option A is incorrect because Change Benefit Job is not a standard Workday process related to life event benefit changes. Option B is also incorrect because while the birth of a child is a dependent-related event, ''Dependent Event'' is not the name of the business process used to process benefit elections. Option C is incorrect because Change Beneficiary is used specifically for updating beneficiary designations, not for enrolling dependents or modifying benefit elections. The correct process that handles employee-initiated benefit changes from life events is Change Benefits, making it the correct answer.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : B

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.

Answer : C

The correct answer is C because reinstatement of benefits for rehired employees is configured through an Enrollment Event Type, not at the individual benefit plan level. Workday uses the enrollment event type to define whether a rehire should trigger reinstatement behavior, how long the reinstatement window remains valid, and which business processes and reasons should launch that event. By selecting Reinstatement Event and setting the Reinstatement Period to six months, the system can determine whether a rehired employee falls within the allowed timeframe to restore prior benefit elections.

Associating the event with the Hire Employee business process and the correct rehire reason ensures the event is triggered automatically when the rehire occurs. Option A is incorrect because reinstatement is not configured on a benefit plan itself. Option B is not appropriate because manual reinstatement introduces inconsistency and bypasses standard event automation. Option D is also incorrect because a step delay in the business process does not define reinstatement logic or prior-election restoration rules. The correct design is to configure a reinstatement-enabled enrollment event type tied to the rehire process.

Answer : A

The correct answer is A because the Start or Waive Coverage section of the Enrollment Event Rule is where Workday determines when benefit coverage becomes effective after an employee becomes eligible. In this scenario, the organization needs two pieces of timing logic applied in sequence: first, a 60-day waiting period from the hire date, and second, a rule that moves the actual coverage start date to the first day of the following month. This type of effective-date calculation belongs in the coverage start configuration tied to the enrollment event.

Option B is incorrect because a Benefit Plan Eligibility Rule determines whether the employee qualifies for the plan, but it does not control the detailed coverage effective-date calculation sequence. Option C identifies the event itself, such as hire or newly eligible, but does not hold the specific start-date logic needed here. Option D is also incorrect because Benefit Groups are used to organize populations for benefits eligibility and plan assignment, not to calculate waiting periods and coverage effective dates. For waiting period and start-date timing logic, the correct configuration point is Start or Waive Coverage.

Answer : C

The correct answer is C because Workday allows insurance rates and calculated healthcare rates to incorporate demographic factors such as age and length of service when determining employee contributions or employer costs. These types of rates are designed to be dynamic and flexible, enabling organizations to apply tiered or variable pricing structures based on worker-specific attributes. For example, insurance plans often vary premiums based on age bands, while calculated healthcare rates can use formulas that consider service duration or other demographic criteria.

Option A is incorrect because flat healthcare rates apply a fixed cost regardless of employee characteristics, meaning demographic factors are not considered. Option B is incorrect because Benefits Annualized Rates (BAR) primarily standardize cost calculations over time and do not inherently support demographic-based variations. Option D is also incorrect because additional benefits rates are typically used for supplemental offerings and do not provide the same level of demographic-driven calculation capability. Therefore, insurance and calculated healthcare rates are the appropriate rate types for incorporating demographic factors in Workday Benefits configuration.

Answer : D

The correct answer is D because the Review Benefit Changes action step gives the benefit partner an opportunity to review and correct event details, including the event date, before the employee's elections are finalized. In Workday, the timing of that review step is critical. If the event date needs to be adjusted, it must be done before the Change Benefit Election steps so the system can correctly evaluate eligibility, effective dates, enrollment windows, and the plans available for selection based on the corrected event date.

Option A is incorrect because the configuration belongs in the standard Change Benefits business process rather than a differently named business process. Option B is not correct because event dates are not simply editable at any time without process design to support the review. Option C is also incorrect because placing the review step after elections would allow employees to make elections using potentially incorrect eligibility timing, which can produce inaccurate enrollment results. The proper design is to position the review step before elections so the business process uses the corrected event data throughout the remainder of the benefits event.

Answer : C

The correct answer is C because when a new employee is hired after Open Enrollment has already been initiated, Workday typically prioritizes the employee's new hire benefits event first. The system does this to ensure the worker completes their initial eligibility-based elections before any broader enrollment event is coordinated for them. Once the new hire event is completed, Workday can then reprocess the Open Enrollment event so the employee is brought into the same enrollment cycle as others in the benefit group, if applicable.

This behavior is part of Workday's event coordination logic, which prevents overlapping benefits tasks from creating conflicting elections or duplicate enrollment opportunities. Option A is incorrect because marking an event as Worker Selectable affects self-service visibility, not whether a new hire initially receives an OE inbox task. Option B is unrelated because a Reinstatement Event applies to rehire scenarios, not newly hired workers entering an open enrollment cycle. Option D is also incorrect because No Changes Allowed would restrict election changes within an event, but it would not explain why the OE task is not initially present. The missing task is due to reprocessing after completion of the new hire event.

Answer : B

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.

Answer : D

The correct answer is D because benefit groups in Workday are driven by benefit group eligibility rules, and the Benefit Group Audit is specifically used to identify workers who qualify for more than one group at the same time. When a worker appears in multiple benefit groups, the root cause is almost always overlapping or conflicting eligibility logic within those group definitions. The appropriate corrective action is to review the criteria assigned to each benefit group and determine exactly why the worker satisfies both sets of rules.

Option A is not appropriate because creating an additional broad benefit group does not resolve the overlap; it would likely add more complexity and increase the risk of duplicate eligibility. Option B focuses on plan-level eligibility, which is downstream from the benefit group assignment and does not address why the worker entered multiple groups in the first place. Option C relates to event processing and enrollment timing, not foundational eligibility setup. To ensure a worker is only eligible for one benefit group, the administrator must refine or correct the group eligibility rules so the criteria are mutually exclusive and aligned with the intended benefits population.

Answer : A

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.

Answer : D

The correct answer is D because benefit events in Workday are highly configurable and designed to align with an organization's specific business processes and policy requirements. Administrators define event types such as life events, open enrollment, or administrative events based on company needs, including eligibility rules, timing, coverage start and end logic, and routing behavior. This flexibility allows organizations to tailor benefit administration to their workforce and regulatory environment.

Option A is incorrect because while Workday provides a framework and some sample configurations, benefit events themselves are not strictly system-delivered and must be configured by the organization. Option B is also incorrect because benefit events typically cannot be freely deleted once in use; instead, they are inactivated to preserve historical data integrity. Option C is incorrect because event closure timing is configurable and depends on settings like Days to Enroll or administrative processes, not an automatic 30-day rule. Therefore, benefit events are best understood as configurable components built to meet company-specific requirements.

Answer : C

The correct answer is C because a Passive event in Workday is used when benefit changes must occur automatically without requiring employee action. In this scenario, the new plan is triggered when employees reach a 12-month service milestone, and the requirement is to automatically transition them to the new plan on their anniversary date. Passive events are designed for exactly this type of situation, where the system enforces enrollment changes based on predefined eligibility conditions or milestones.

Option A is incorrect because Open Enrollment applies to all eligible employees during a scheduled enrollment window and requires employee participation. Option B is incorrect because New Hire events only apply at the time of hire, not for service anniversaries. Option D is also incorrect because Worker Selectable events require the employee to actively make a choice, which contradicts the requirement for automatic enrollment. A Passive event ensures the system evaluates eligibility at the 12-month mark and applies the new plan without requiring any employee interaction, making it the correct configuration approach.

Answer : A

The correct answer is A because Workday insurance plan setup depends on several foundational insurance-specific components being in place before the plan itself can be configured. These prerequisites include insurance coverage levels, insurance coverage, and the applicable insurance rate. Together, these elements define how the plan will structure enrollment options, what level of protection or election is available, and how the associated cost is calculated. Without these core building blocks, the insurance plan cannot be created correctly because the plan requires a predefined coverage framework and rate structure.

Option B is incorrect because Enrollment Event Rule configuration is related to how and when workers can make benefit changes, not to the foundational setup required before creating the plan. Option C is not correct because those items are not the standard prerequisite configuration components for insurance plan creation. Option D includes items that may be relevant later in overall benefits administration, but they are not the essential insurance setup components required prior to creating the plan itself. For insurance plan configuration in Workday, the primary prerequisite is the definition of coverage levels, coverage structure, and rates.

Answer : D

The correct answer is D because Workday provides cross plan insurance rules specifically to control relationships between elections across multiple insurance plans. When one plan's maximum coverage must be calculated as a percentage of another plan's election, the correct configuration is a cross plan insurance percentage maximum. In this case, the Spousal Life plan must be capped at 50% of the employee's Voluntary Supplemental Life election, so the system needs a rule that compares the two plans and enforces that percentage-based limit during enrollment.

Option A is incorrect because an eligibility rule determines whether a worker can enroll in a plan, not how one insurance election is mathematically limited by another. Option B is also incorrect because business process validations are not the standard configuration method for enforcing insurance coverage relationships during benefit elections. Option C does not solve the requirement either, since a prerequisite can require another election but does not impose a percentage-based maximum. To enforce dependent insurance coverage limits tied to an employee's elected amount, Workday uses a cross plan insurance percentage maximum, making D the correct configuration choice.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : D

The correct answer is D because the Benefit Corrections in Progress Audit report is specifically designed to identify benefit events that require administrative action, including those that must be reviewed, corrected, or submitted by a benefits partner or administrator. This report highlights events that are not yet finalized and may require intervention, making it especially useful for tracking administrative workload and ensuring no pending corrections are overlooked.

Option A is incorrect because Open Enrollment Status focuses on mass enrollment events and their progress, not specifically on events requiring administrative submission. Option B is also incorrect because Benefit Group Audit is used to review eligibility and group assignment issues, not event submission tracking. Option C is partially related, as Benefit Event Status shows the status of events, but it does not specifically isolate events that require action from a benefits partner. The Benefit Corrections in Progress Audit report provides targeted visibility into events needing administrative completion, making it the correct choice.

Answer : D

The correct answer is D because the Open Enrollment Status report is specifically designed to manage and monitor mass benefit events, such as Open Enrollment. This report provides administrators with visibility into the status of all enrollment events across the organization, including those that are in progress, submitted, or not yet started. Importantly, it also allows administrators to take action on these events, including closing and finalizing mass events once the enrollment period ends.

Option A is incorrect because the Benefit Census report provides a snapshot of current enrollments, not event processing actions. Option B is incorrect because Benefit Group Audit focuses on eligibility and group assignment issues. Option C is partially related, as Benefit Event Status shows event progress, but it is not the primary report used for managing and finalizing mass enrollment events. The Open Enrollment Status report is specifically built to support large-scale enrollment tracking and administrative actions, making it the correct choice for closing and finalizing mass benefit events.

Answer : A

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.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : D

The correct answer is D because Workday provides cross plan insurance rules specifically to control relationships between elections across multiple insurance plans. When one plan's maximum coverage must be calculated as a percentage of another plan's election, the correct configuration is a cross plan insurance percentage maximum. In this case, the Spousal Life plan must be capped at 50% of the employee's Voluntary Supplemental Life election, so the system needs a rule that compares the two plans and enforces that percentage-based limit during enrollment.

Option A is incorrect because an eligibility rule determines whether a worker can enroll in a plan, not how one insurance election is mathematically limited by another. Option B is also incorrect because business process validations are not the standard configuration method for enforcing insurance coverage relationships during benefit elections. Option C does not solve the requirement either, since a prerequisite can require another election but does not impose a percentage-based maximum. To enforce dependent insurance coverage limits tied to an employee's elected amount, Workday uses a cross plan insurance percentage maximum, making D the correct configuration choice.

Answer : C

The correct answer is C because Workday allows insurance rates and calculated healthcare rates to incorporate demographic factors such as age and length of service when determining employee contributions or employer costs. These types of rates are designed to be dynamic and flexible, enabling organizations to apply tiered or variable pricing structures based on worker-specific attributes. For example, insurance plans often vary premiums based on age bands, while calculated healthcare rates can use formulas that consider service duration or other demographic criteria.

Option A is incorrect because flat healthcare rates apply a fixed cost regardless of employee characteristics, meaning demographic factors are not considered. Option B is incorrect because Benefits Annualized Rates (BAR) primarily standardize cost calculations over time and do not inherently support demographic-based variations. Option D is also incorrect because additional benefits rates are typically used for supplemental offerings and do not provide the same level of demographic-driven calculation capability. Therefore, insurance and calculated healthcare rates are the appropriate rate types for incorporating demographic factors in Workday Benefits configuration.

Answer : C

The correct answer is C because for a benefit event to both trigger from a Leave of Absence business process and route to the benefits team, two key configurations must be present within the Enrollment Event Type. First, the event must be properly linked to the Leave of Absence business process in the Events and Reasons section so that Workday recognizes the staffing action as a trigger. Second, the Route to Benefits Partner checkbox must be selected so that once the event is initiated, it is automatically routed to the benefits team for review or processing.

Option A is incorrect because reinstatement configuration applies to rehire scenarios, not leave events. Option B is incorrect because Worker Selectable controls employee self-service visibility, not routing. Option D is partially correct regarding routing but incomplete, as without mapping the Leave event in Events and Reasons, the event will not trigger at all. Therefore, both mapping the Leave event and enabling routing are required to ensure proper event initiation and processing by the benefits team.

Answer : A

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.

Answer : B

The correct answer is B because the Benefit Events Status report is specifically designed to track and monitor benefit events across various stages, including in progress, submitted, completed, or cancelled. This report provides visibility into event activity at the individual worker level and is commonly used by benefits administrators to monitor ongoing events such as new hire benefit enrollments. It allows administrators to identify which employees still need to complete their elections and ensures timely follow-up.

Option A is incorrect because the Benefit Group Audit report focuses on validating worker assignment to benefit groups and identifying eligibility overlaps, not event progress. Option C is also incorrect because the Benefit Census report provides a snapshot of current benefit enrollments rather than tracking event status. Option D is incorrect because Open Enrollment Status is specific to open enrollment events and does not provide detailed tracking for other event types like new hire events. For monitoring active benefit events, especially new hire enrollments, the correct report is Benefit Events Status.

Answer : D

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.

Answer : A

The correct answer is A because in Workday, adding a newborn to benefits requires more than simply already being enrolled at the Employee+Family coverage target. Even when the employee's current election tier already allows family coverage, the new dependent must still be formally added through a qualifying life event, typically a birth event. The employee must initiate the appropriate benefits event, add the child as a dependent, review the existing medical plan election, and submit the event so the system can properly record the dependent, apply eligibility rules, and transmit the updated enrollment to downstream processes and carriers.

Option B is incorrect because carrier coverage does not update automatically unless the dependent is entered and the benefit event is completed in Workday. Option C is incorrect because a birth is a qualifying life event and should not wait until the next open enrollment period. Option D is also incorrect because adding the dependent record alone is not enough; the employee must also complete and submit the related benefits event so the child is attached to the medical election and coverage is processed correctly.

Answer : D

The correct answer is D because Change Benefits (Default Definition) is the standard business process in Workday that enables benefit elections to be triggered and processed in conjunction with core HCM events such as Hire, Change Job, or other staffing actions. This business process is designed to integrate with HCM workflows and ensures that benefit eligibility and enrollment opportunities are automatically initiated when relevant changes occur in a worker's employment status.

Option A is incorrect because Open Enrollment is a specific, scheduled event that applies to all eligible workers during a defined period, not to individual HCM transactions. Option B is also incorrect because Life Event processes are triggered by employee-reported changes such as marriage or birth, rather than system-driven HCM events. Option C is not a standard Workday benefits business process used for enrollment. The Default Definition provides the foundational configuration that links benefits processing with HCM business processes, allowing seamless and automated benefit election updates during key employment events.

Answer : A

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.

Answer : A

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.

Answer : A

The correct answer is A because this scenario describes a benefit that employees may elect during the year as a new enrollment opportunity, which means the event belongs on the Start/Waive tab of the Enrollment Event Rule. The requirement also states that only the gym membership plan should be available and that both coverage and payroll deductions should begin on the first of the following month. The Start/Waive configuration is where Workday controls which coverage type is opened for election and how coverage and deduction effective dates are calculated for that event.

Option B is incorrect because the Loss of Coverage tab is used when coverage is ending, not when a worker is newly electing a plan. Option C is also incorrect because it would start coverage and deductions on the event date, which does not meet the stated timing requirement. Option D is incorrect because enrollment event rules are driven by event types, not by adding a coverage type in place of the event itself. Therefore, the administrator should add the gym membership event type to Start/Waive and configure the start logic for the first of the following month.

Answer : A

The correct answer is A because in Workday, a benefit plan must be included in the Benefit Plan Year Definition to be available for enrollment during a specific plan year. Even if the plan is fully configured with eligibility rules, rates, and coverage targets, it will not appear to employees unless it is explicitly associated with the active plan year. This configuration determines whether the plan is ''active'' and available for enrollment events such as Open Enrollment or life events.

Option B is incorrect because Health Care Rates define cost calculations but do not control whether a plan is available or visible. Option C is also incorrect because Benefit Coverage Types classify the type of benefit (such as medical or dental) but do not determine plan availability. Option D is incorrect because Health Care Coverage Targets define employer and employee cost-sharing, not whether the plan is active for enrollment. Therefore, if a benefit plan is not appearing during enrollment, the first place to verify is whether it has been properly added to the Benefit Plan Year Definition for the relevant plan year.

Answer : A

The correct answer is A because the employee's birth life event occurred after open enrollment had already been closed, but before the new plan year effective date of January 1. In Workday, the birth event can update the employee's future-dated benefit elections so the child is added with coverage effective for the new plan year, but if open enrollment was already closed and finalized, the updated enrollment results must be re-closed and re-finalized so downstream integrations and provider files reflect the revised coverage.

This action is an administrative responsibility handled by the benefit administrator, not simply by the benefit partner. Option B is incorrect because the question asks about the step needed to ensure final integrated coverage handling, which is typically managed at the administrative mass-event level. Option C is unnecessary because rescinding and recreating open enrollment adds avoidable complexity and is not the standard approach. Option D is also incorrect because Workday does not require creation of a hybrid event in this scenario. Re-finalizing the open enrollment results ensures the newborn is included in the January 1 coverage transmission.

Answer : A

The correct answer is A because the Start or Waive Coverage section of the Enrollment Event Rule is where Workday determines when benefit coverage becomes effective after an employee becomes eligible. In this scenario, the organization needs two pieces of timing logic applied in sequence: first, a 60-day waiting period from the hire date, and second, a rule that moves the actual coverage start date to the first day of the following month. This type of effective-date calculation belongs in the coverage start configuration tied to the enrollment event.

Option B is incorrect because a Benefit Plan Eligibility Rule determines whether the employee qualifies for the plan, but it does not control the detailed coverage effective-date calculation sequence. Option C identifies the event itself, such as hire or newly eligible, but does not hold the specific start-date logic needed here. Option D is also incorrect because Benefit Groups are used to organize populations for benefits eligibility and plan assignment, not to calculate waiting periods and coverage effective dates. For waiting period and start-date timing logic, the correct configuration point is Start or Waive Coverage.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : C

The correct answer is C because a Health Care Classification is typically required in Workday when configuring U.S. medical plans. This classification supports plan identification and compliance-related processing within the United States benefits framework. It is used to distinguish the type of medical coverage being offered and helps align the plan with U.S.-specific benefits administration requirements, reporting needs, and downstream processing. Since U.S. medical plans are subject to particular health coverage categorizations, including this value during plan setup is an essential part of proper configuration.

Option B is not correct because Canadian medical plans do not use the same U.S.-specific health care classification requirement. Option A and Option D are also incorrect because Health Savings Accounts are different benefit types from medical plans. Although an HSA may be linked to a medical election in the U.S., the question asks specifically about including a Health Care Classification in the plan setup, which is associated with the medical plan configuration itself rather than the savings account plan. Therefore, the scenario that requires this setup element is a Medical plan for USA.

Answer : B

The correct answer is B because Workday controls whether dependents such as spouses and children can be enrolled in a health care plan through the Coverage Dependent Eligibility configuration on the plan. This is the field used to apply eligibility logic specifically to covered dependents. When a consultant needs to prevent children over a certain age from enrolling, the age-based rule should be attached at this plan-level dependent coverage eligibility point so the system evaluates the child's eligibility at the time of enrollment.

Option A is too general and does not identify the specific field used for dependent coverage evaluation in the health care plan setup. Option C is incorrect because the Maintain Related Persons Relationship task defines relationship types, such as child or spouse, but it does not enforce benefit plan age-based eligibility rules. Option D is also incorrect because coverage targets determine cost-sharing or coverage structure, not whether a dependent satisfies enrollment eligibility conditions. To ensure only eligible children can be covered, the consultant must configure the rule in the Coverage Dependent Eligibility field of the health care plan.

Answer : B

The correct answer is B because the Benefit Events Status report is specifically designed to track and monitor benefit events across various stages, including in progress, submitted, completed, or cancelled. This report provides visibility into event activity at the individual worker level and is commonly used by benefits administrators to monitor ongoing events such as new hire benefit enrollments. It allows administrators to identify which employees still need to complete their elections and ensures timely follow-up.

Option A is incorrect because the Benefit Group Audit report focuses on validating worker assignment to benefit groups and identifying eligibility overlaps, not event progress. Option C is also incorrect because the Benefit Census report provides a snapshot of current benefit enrollments rather than tracking event status. Option D is incorrect because Open Enrollment Status is specific to open enrollment events and does not provide detailed tracking for other event types like new hire events. For monitoring active benefit events, especially new hire enrollments, the correct report is Benefit Events Status.

Answer : D

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.

Answer : B

The correct answer is B because in Workday, Related Person Relationships are configurable and can be used across multiple contexts such as dependents, beneficiaries, and emergency contacts. The Restricted to Relationships field allows administrators to limit where a relationship type can be used. However, if this field is left blank, the relationship type becomes broadly available across all applicable areas, enabling it to be used flexibly for different purposes within the system.

Option A is incorrect because although Workday delivers some standard relationship types, they can be configured or extended as needed. Option C is incorrect because Workday does support tracking certain dependent-related data within benefits and eligibility contexts. Option D is also incorrect because Related Person Relationships are not restricted by benefit group; they are global configuration elements that apply across the tenant rather than being tied to specific benefit group eligibility structures. Therefore, leaving the restriction field blank allows maximum usability of a relationship type across different business processes.

Answer : C

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.

Answer : A

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.

Answer : D

The correct answer is D because in Workday, when an employee initiates a life event such as the birth of a child through the Benefits and Pay Hub, the system launches the Change Benefits business process. This process is the central workflow used to capture and process benefit election changes resulting from qualifying life events. The birth event acts as the trigger, but the actual business process used to manage elections, review options, and submit changes is Change Benefits.

Option A is incorrect because Change Benefit Job is not a standard Workday process related to life event benefit changes. Option B is also incorrect because while the birth of a child is a dependent-related event, ''Dependent Event'' is not the name of the business process used to process benefit elections. Option C is incorrect because Change Beneficiary is used specifically for updating beneficiary designations, not for enrolling dependents or modifying benefit elections. The correct process that handles employee-initiated benefit changes from life events is Change Benefits, making it the correct answer.

Answer : A

The correct answer is A because Workday insurance plan setup depends on several foundational insurance-specific components being in place before the plan itself can be configured. These prerequisites include insurance coverage levels, insurance coverage, and the applicable insurance rate. Together, these elements define how the plan will structure enrollment options, what level of protection or election is available, and how the associated cost is calculated. Without these core building blocks, the insurance plan cannot be created correctly because the plan requires a predefined coverage framework and rate structure.

Option B is incorrect because Enrollment Event Rule configuration is related to how and when workers can make benefit changes, not to the foundational setup required before creating the plan. Option C is not correct because those items are not the standard prerequisite configuration components for insurance plan creation. Option D includes items that may be relevant later in overall benefits administration, but they are not the essential insurance setup components required prior to creating the plan itself. For insurance plan configuration in Workday, the primary prerequisite is the definition of coverage levels, coverage structure, and rates.

Answer : D

The correct answer is D because the behavior described shows that benefit coverage is ending immediately on the employee's termination date rather than continuing through the end of the month. In Workday, this outcome is controlled by the Coverage End Date setting on the termination event within the Enrollment Event Rule. If that setting is configured as On the Event Date, coverage ends on the exact date of termination, which explains why benefits become inactive right away.

Option C is incorrect because if the Coverage End Date were set to Last Day of the Month, the employee's benefits would remain active until the month-end, which is the desired result. Option A is not the best answer because a half-month rule would produce a different timing result and would not directly explain coverage ending exactly on the termination date. Option B is also incorrect because an end date based on the next pay period begin date would not typically cause immediate termination-date inactivation. Since the system is ending benefits on the termination date itself, the termination event rule is clearly set to On the Event Date.

Answer : A

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.

Answer : C

The correct answer is C because Workday Benefits configuration starts with the foundational components that define how a benefit offering is structured. When introducing a completely new type of benefit such as a gym membership, the system must first recognize the benefit category through an appropriate coverage type. The coverage type serves as a core setup element that supports plan creation and determines how the plan is classified within the benefits framework.

Option A is not correct because rates are generally configured after the underlying plan structure exists. Rates define pricing or cost-sharing, but they do not establish the foundational setup needed to create a new benefit offering. Option B is also incorrect because benefit groups are used to organize worker eligibility and enrollment populations, not to establish the base benefit component required for a new plan type. Option D applies to dependent or related-person scenarios, such as spouse or child coverage, which is not relevant for a gym membership benefit. In this case, defining the proper coverage type is the necessary first step before the plan itself can be configured.

Answer : D

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.

Answer : A

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.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : B

The correct answer is B because in Workday, Related Person Relationships are configurable and can be used across multiple contexts such as dependents, beneficiaries, and emergency contacts. The Restricted to Relationships field allows administrators to limit where a relationship type can be used. However, if this field is left blank, the relationship type becomes broadly available across all applicable areas, enabling it to be used flexibly for different purposes within the system.

Option A is incorrect because although Workday delivers some standard relationship types, they can be configured or extended as needed. Option C is incorrect because Workday does support tracking certain dependent-related data within benefits and eligibility contexts. Option D is also incorrect because Related Person Relationships are not restricted by benefit group; they are global configuration elements that apply across the tenant rather than being tied to specific benefit group eligibility structures. Therefore, leaving the restriction field blank allows maximum usability of a relationship type across different business processes.

Answer : B

The correct answer is B because the Benefit Events Status report is specifically designed to track and monitor benefit events across various stages, including in progress, submitted, completed, or cancelled. This report provides visibility into event activity at the individual worker level and is commonly used by benefits administrators to monitor ongoing events such as new hire benefit enrollments. It allows administrators to identify which employees still need to complete their elections and ensures timely follow-up.

Option A is incorrect because the Benefit Group Audit report focuses on validating worker assignment to benefit groups and identifying eligibility overlaps, not event progress. Option C is also incorrect because the Benefit Census report provides a snapshot of current benefit enrollments rather than tracking event status. Option D is incorrect because Open Enrollment Status is specific to open enrollment events and does not provide detailed tracking for other event types like new hire events. For monitoring active benefit events, especially new hire enrollments, the correct report is Benefit Events Status.

Answer : C

The correct answer is C because reinstatement of benefits for rehired employees is configured through an Enrollment Event Type, not at the individual benefit plan level. Workday uses the enrollment event type to define whether a rehire should trigger reinstatement behavior, how long the reinstatement window remains valid, and which business processes and reasons should launch that event. By selecting Reinstatement Event and setting the Reinstatement Period to six months, the system can determine whether a rehired employee falls within the allowed timeframe to restore prior benefit elections.

Associating the event with the Hire Employee business process and the correct rehire reason ensures the event is triggered automatically when the rehire occurs. Option A is incorrect because reinstatement is not configured on a benefit plan itself. Option B is not appropriate because manual reinstatement introduces inconsistency and bypasses standard event automation. Option D is also incorrect because a step delay in the business process does not define reinstatement logic or prior-election restoration rules. The correct design is to configure a reinstatement-enabled enrollment event type tied to the rehire process.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : B

The correct answer is B because a Calculated Health Care Rate is designed for medical plan pricing that depends on multiple worker-specific and election-specific factors. In this scenario, the rate must vary based on the employee's age, tobacco usage, and the coverage target selected during enrollment. That combination requires a configurable rate structure capable of evaluating demographic factors and enrollment choices together, which is exactly what a calculated health care rate supports in Workday.

Option A is incorrect because a flat health care rate applies a fixed amount and does not dynamically adjust based on employee attributes or selected coverage targets. Option C is not the best fit because a Benefit Annualized Rate is intended to standardize cost presentation or annualization logic rather than drive complex medical pricing based on multiple eligibility and rating factors. Option D is also incorrect because a benefit surcharge is generally used to add an extra charge for a specific condition, such as tobacco use, but it does not by itself represent the full rate structure for the medical plan. A calculated health care rate is the appropriate configuration when several variables determine the employee's cost.

Answer : B

The correct answer is B because when a dependent reaches an age limit and loses eligibility for coverage, Workday treats this as a loss of coverage event. In this scenario, the child turning 25 triggers the termination of dependent eligibility, meaning their coverage must end. The Loss of Coverage tab within the Enrollment Event Rule is specifically designed to handle situations where an individual or dependent is no longer eligible for a benefit and coverage needs to be removed or ended.

Option A is incorrect because the Currently Covered tab is used to manage existing enrollments that remain valid, not those that must terminate due to eligibility changes. Option C applies to scenarios where coverage is being initiated or waived, not removed due to age limits. Option D is also incorrect because the Newly Eligible tab is used when a worker or dependent becomes eligible for new coverage, which is the opposite of this situation. Since the event results in the dependent losing eligibility and coverage, configuring it under the Loss of Coverage tab ensures proper termination processing within the enrollment event.

Answer : C

The correct answer is C because a Passive event in Workday is used when benefit changes must occur automatically without requiring employee action. In this scenario, the new plan is triggered when employees reach a 12-month service milestone, and the requirement is to automatically transition them to the new plan on their anniversary date. Passive events are designed for exactly this type of situation, where the system enforces enrollment changes based on predefined eligibility conditions or milestones.

Option A is incorrect because Open Enrollment applies to all eligible employees during a scheduled enrollment window and requires employee participation. Option B is incorrect because New Hire events only apply at the time of hire, not for service anniversaries. Option D is also incorrect because Worker Selectable events require the employee to actively make a choice, which contradicts the requirement for automatic enrollment. A Passive event ensures the system evaluates eligibility at the 12-month mark and applies the new plan without requiring any employee interaction, making it the correct configuration approach.

Answer : C

The correct answer is C because benefit groups in Workday are typically created when distinct populations of workers need different overall benefits structures, often due to major organizational differences such as country, legal entity, or currency. When employees are located in different countries like the United States and the United Kingdom, they commonly have different benefit programs, regulatory requirements, providers, and plan pricing currencies. In that situation, separate benefit groups help organize eligibility and ensure each population is tied to the correct set of plans and configuration rules.

Option A is not the best reason because holding multiple positions does not by itself require separate benefit groups; eligibility is usually managed through worker and job-based rules. Option B is more appropriately handled through plan-level eligibility rules rather than creating an entirely separate benefit group for one age-based condition. Option D concerns differences within medical plan design, such as coverage targets, which can be handled at the plan configuration level rather than by creating separate groups. Benefit groups should be used when broad populations require distinct benefits frameworks, and different countries with different currencies are a strong example of that need.

Answer : D

The correct answer is D because the Open Enrollment Status report in Workday provides a comprehensive view of benefit event activity across different statuses, including in progress, submitted, cancelled, closed, and finalized events. It is specifically designed to track enrollment progress and completion at a summarized level, often grouped by benefit group, allowing administrators to monitor participation and identify outstanding actions during enrollment cycles.

Option A is incorrect because Enrollment Count focuses on numerical summaries of enrollments rather than detailed status tracking across event stages. Option B is also incorrect because the Benefit Group Audit report is used to validate eligibility and identify workers assigned to multiple benefit groups, not to track event processing statuses. Option C is incorrect because Benefit Census provides a snapshot of current enrollments and participant data but does not track event lifecycle statuses. The Open Enrollment Status report is the appropriate tool for monitoring event progress and status breakdowns across benefit groups.

Answer : C

The correct answer is C because a Health Care Classification is typically required in Workday when configuring U.S. medical plans. This classification supports plan identification and compliance-related processing within the United States benefits framework. It is used to distinguish the type of medical coverage being offered and helps align the plan with U.S.-specific benefits administration requirements, reporting needs, and downstream processing. Since U.S. medical plans are subject to particular health coverage categorizations, including this value during plan setup is an essential part of proper configuration.

Option B is not correct because Canadian medical plans do not use the same U.S.-specific health care classification requirement. Option A and Option D are also incorrect because Health Savings Accounts are different benefit types from medical plans. Although an HSA may be linked to a medical election in the U.S., the question asks specifically about including a Health Care Classification in the plan setup, which is associated with the medical plan configuration itself rather than the savings account plan. Therefore, the scenario that requires this setup element is a Medical plan for USA.

Answer : D

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.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : D

The correct answer is D because Workday allows multiple benefit events to be open at the same time only when they do not impact the same coverage types. Coverage types define categories of benefits such as medical, dental, or life insurance. When two events affect different coverage types, the system can process them independently without conflict, allowing both events to remain open simultaneously.

If two events impact the same coverage type, Workday typically enforces sequencing rules to prevent overlapping or conflicting elections. In such cases, one event must usually be completed or closed before another can proceed, ensuring data integrity and consistent benefit elections. Option A is incorrect because event dates alone do not determine whether events can coexist. Option B and C are also incorrect because the timing of when events are entered does not control simultaneous processing. The key determining factor is whether the events overlap in the coverage types they affect. When they do not share coverage types, Workday permits both events to remain open concurrently.

Answer : A

The correct answer is A because in Workday, adding a newborn to benefits requires more than simply already being enrolled at the Employee+Family coverage target. Even when the employee's current election tier already allows family coverage, the new dependent must still be formally added through a qualifying life event, typically a birth event. The employee must initiate the appropriate benefits event, add the child as a dependent, review the existing medical plan election, and submit the event so the system can properly record the dependent, apply eligibility rules, and transmit the updated enrollment to downstream processes and carriers.

Option B is incorrect because carrier coverage does not update automatically unless the dependent is entered and the benefit event is completed in Workday. Option C is incorrect because a birth is a qualifying life event and should not wait until the next open enrollment period. Option D is also incorrect because adding the dependent record alone is not enough; the employee must also complete and submit the related benefits event so the child is attached to the medical election and coverage is processed correctly.

Answer : C

The correct answer is C because Workday Benefits configuration starts with the foundational components that define how a benefit offering is structured. When introducing a completely new type of benefit such as a gym membership, the system must first recognize the benefit category through an appropriate coverage type. The coverage type serves as a core setup element that supports plan creation and determines how the plan is classified within the benefits framework.

Option A is not correct because rates are generally configured after the underlying plan structure exists. Rates define pricing or cost-sharing, but they do not establish the foundational setup needed to create a new benefit offering. Option B is also incorrect because benefit groups are used to organize worker eligibility and enrollment populations, not to establish the base benefit component required for a new plan type. Option D applies to dependent or related-person scenarios, such as spouse or child coverage, which is not relevant for a gym membership benefit. In this case, defining the proper coverage type is the necessary first step before the plan itself can be configured.

Answer : C

The correct answer is C because when a new employee is hired after Open Enrollment has already been initiated, Workday typically prioritizes the employee's new hire benefits event first. The system does this to ensure the worker completes their initial eligibility-based elections before any broader enrollment event is coordinated for them. Once the new hire event is completed, Workday can then reprocess the Open Enrollment event so the employee is brought into the same enrollment cycle as others in the benefit group, if applicable.

This behavior is part of Workday's event coordination logic, which prevents overlapping benefits tasks from creating conflicting elections or duplicate enrollment opportunities. Option A is incorrect because marking an event as Worker Selectable affects self-service visibility, not whether a new hire initially receives an OE inbox task. Option B is unrelated because a Reinstatement Event applies to rehire scenarios, not newly hired workers entering an open enrollment cycle. Option D is also incorrect because No Changes Allowed would restrict election changes within an event, but it would not explain why the OE task is not initially present. The missing task is due to reprocessing after completion of the new hire event.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : A

The correct answer is A because Workday insurance plan setup depends on several foundational insurance-specific components being in place before the plan itself can be configured. These prerequisites include insurance coverage levels, insurance coverage, and the applicable insurance rate. Together, these elements define how the plan will structure enrollment options, what level of protection or election is available, and how the associated cost is calculated. Without these core building blocks, the insurance plan cannot be created correctly because the plan requires a predefined coverage framework and rate structure.

Option B is incorrect because Enrollment Event Rule configuration is related to how and when workers can make benefit changes, not to the foundational setup required before creating the plan. Option C is not correct because those items are not the standard prerequisite configuration components for insurance plan creation. Option D includes items that may be relevant later in overall benefits administration, but they are not the essential insurance setup components required prior to creating the plan itself. For insurance plan configuration in Workday, the primary prerequisite is the definition of coverage levels, coverage structure, and rates.

Answer : D

The correct answer is D because the Enrollment Event Rule is the configuration area in Workday that controls how benefit elections behave during events such as Open Enrollment. This is where administrators define which coverage types are available, when coverage and deductions begin, what defaulting logic applies if employees take no action, and how plans such as HSA and FSA should be treated when active re-enrollment is required. The scenario specifically references requirements that involve start dates, election behavior, and default outcomes, all of which are managed through the rule tied to the enrollment event.

Option A is incorrect because the Enrollment Event Type identifies and classifies the event, but it does not hold the detailed coverage behavior rules described in the question. Option B is also incorrect because Benefit Coverage Types classify plan groupings rather than define event processing logic. Option C is not correct because Initiate Open Enrollment is the process used to launch the event, not the place where these functional requirements are configured. Since the requirement is about controlling enrollment behavior and coverage processing during the event, the correct setup location is the Enrollment Event Rule.

Answer : B

The correct answer is B because Workday uses effective dating to manage changes to benefit plans over time, including contribution limits for plans such as Health Savings Accounts (HSAs). To ensure that new contribution limits apply for the upcoming open enrollment period, administrators must update the HSA plan with an effective date aligned to the start of the new benefit plan year. This allows the system to maintain historical accuracy while applying updated limits prospectively for future enrollments.

By entering the new limits with the correct future effective date, Workday ensures that employees enrolling during open enrollment will see and be governed by the updated contribution thresholds. Option A is incorrect because HSA contribution limits are configured within the benefit plan, not solely in payroll. Option C is incorrect because Workday does not prompt administrators automatically to update limits during enrollment events. Option D is also incorrect because Workday does not automatically adjust HSA limits; administrators must manually update them to reflect regulatory changes. Proper use of effective dating ensures accurate and compliant benefit plan configuration across plan years.

Answer : A

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.

Answer : C

The correct answer is C because when a new employee is hired after Open Enrollment has already been initiated, Workday typically prioritizes the employee's new hire benefits event first. The system does this to ensure the worker completes their initial eligibility-based elections before any broader enrollment event is coordinated for them. Once the new hire event is completed, Workday can then reprocess the Open Enrollment event so the employee is brought into the same enrollment cycle as others in the benefit group, if applicable.

This behavior is part of Workday's event coordination logic, which prevents overlapping benefits tasks from creating conflicting elections or duplicate enrollment opportunities. Option A is incorrect because marking an event as Worker Selectable affects self-service visibility, not whether a new hire initially receives an OE inbox task. Option B is unrelated because a Reinstatement Event applies to rehire scenarios, not newly hired workers entering an open enrollment cycle. Option D is also incorrect because No Changes Allowed would restrict election changes within an event, but it would not explain why the OE task is not initially present. The missing task is due to reprocessing after completion of the new hire event.

Answer : A

The correct answer is A because Workday allows administrators to keep a broad worker population in a single benefit group while restricting access to a specific plan through a Benefit Plan Eligibility Rule. In this case, all full-time employees belong to one benefit group, but only those with more than twenty years of service should be allowed to enroll in the medical plan. The correct design is to assign the plan to the existing benefit group and then attach a worker-based eligibility rule on the plan itself using the Worker Plan Eligibility field.

This approach avoids unnecessary creation of another benefit group and keeps the overall benefits structure simpler and easier to maintain. Option B is incorrect because manual communication and intervention are not proper configuration controls for eligibility. Option C is also incorrect because Provider ID is not intended to manage service-based plan eligibility. Option D is not appropriate because launching a separate enrollment just for one eligibility condition creates administrative complexity and does not solve the configuration requirement cleanly. Plan-level eligibility rules are the standard Workday method for handling this scenario.

Answer : D

The correct answer is D because in Workday, when an employee initiates a life event such as the birth of a child through the Benefits and Pay Hub, the system launches the Change Benefits business process. This process is the central workflow used to capture and process benefit election changes resulting from qualifying life events. The birth event acts as the trigger, but the actual business process used to manage elections, review options, and submit changes is Change Benefits.

Option A is incorrect because Change Benefit Job is not a standard Workday process related to life event benefit changes. Option B is also incorrect because while the birth of a child is a dependent-related event, ''Dependent Event'' is not the name of the business process used to process benefit elections. Option C is incorrect because Change Beneficiary is used specifically for updating beneficiary designations, not for enrolling dependents or modifying benefit elections. The correct process that handles employee-initiated benefit changes from life events is Change Benefits, making it the correct answer.

Answer : D

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.

Answer : D

The correct answer is D because Workday provides cross plan insurance rules specifically to control relationships between elections across multiple insurance plans. When one plan's maximum coverage must be calculated as a percentage of another plan's election, the correct configuration is a cross plan insurance percentage maximum. In this case, the Spousal Life plan must be capped at 50% of the employee's Voluntary Supplemental Life election, so the system needs a rule that compares the two plans and enforces that percentage-based limit during enrollment.

Option A is incorrect because an eligibility rule determines whether a worker can enroll in a plan, not how one insurance election is mathematically limited by another. Option B is also incorrect because business process validations are not the standard configuration method for enforcing insurance coverage relationships during benefit elections. Option C does not solve the requirement either, since a prerequisite can require another election but does not impose a percentage-based maximum. To enforce dependent insurance coverage limits tied to an employee's elected amount, Workday uses a cross plan insurance percentage maximum, making D the correct configuration choice.

Answer : B

The correct answer is B because medical and dental plans typically follow a passive enrollment approach during Open Enrollment, meaning employees who take no action should automatically retain their current elections. In Workday, this behavior is controlled through the Defaulting Rules on the Coverage Rules tab of the Enrollment Event Rule. Selecting Default to Current Elections or Waive ensures that if an employee does not actively make changes, the system carries forward their existing elections into the new plan year.

This aligns with the requirement that employees remain enrolled in their prior medical and dental coverage unless they explicitly choose otherwise. Option A is incorrect because Priority Coverage is used when selecting among multiple available options rather than maintaining existing elections. Option C is not appropriate because it introduces unnecessary complexity and is not the standard configuration for passive enrollment scenarios. Option D is incorrect because Default to Waive would terminate coverage for employees who do not take action, which contradicts the requirement. Therefore, using Default to Current Elections or Waive ensures consistent continuation of coverage for passive enrollment plans like medical and dental.

Answer : D

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.

Answer : B

The correct answer is B because Workday separates plan configuration dates from plan availability for enrollment through the use of benefit plan year definitions. Even though the system restricts entering a future effective date during plan creation, administrators can still control when a plan becomes available by associating it with a specific benefit plan year. The plan year defines the enrollment period, coverage dates, and availability of benefit plans for a given cycle, such as the upcoming year.

By adding the plan to the appropriate future benefit plan year definition, the administrator ensures that the plan is included in enrollment events like Open Enrollment for that year. Option A is incorrect because the effective date alone does not determine enrollment availability. Option C is not appropriate, as marking a plan inactive prevents usage rather than scheduling future availability. Option D is incorrect because assigning the plan to the current plan year does not make it available for the next year's enrollment. Proper configuration of the benefit plan year is the correct approach to control timing and availability.

Answer : C

The correct answer is C because a Health Care Classification is typically required in Workday when configuring U.S. medical plans. This classification supports plan identification and compliance-related processing within the United States benefits framework. It is used to distinguish the type of medical coverage being offered and helps align the plan with U.S.-specific benefits administration requirements, reporting needs, and downstream processing. Since U.S. medical plans are subject to particular health coverage categorizations, including this value during plan setup is an essential part of proper configuration.

Option B is not correct because Canadian medical plans do not use the same U.S.-specific health care classification requirement. Option A and Option D are also incorrect because Health Savings Accounts are different benefit types from medical plans. Although an HSA may be linked to a medical election in the U.S., the question asks specifically about including a Health Care Classification in the plan setup, which is associated with the medical plan configuration itself rather than the savings account plan. Therefore, the scenario that requires this setup element is a Medical plan for USA.

Answer : B

The correct answer is B because Workday uses effective dating to manage changes to benefit plans over time, including contribution limits for plans such as Health Savings Accounts (HSAs). To ensure that new contribution limits apply for the upcoming open enrollment period, administrators must update the HSA plan with an effective date aligned to the start of the new benefit plan year. This allows the system to maintain historical accuracy while applying updated limits prospectively for future enrollments.

By entering the new limits with the correct future effective date, Workday ensures that employees enrolling during open enrollment will see and be governed by the updated contribution thresholds. Option A is incorrect because HSA contribution limits are configured within the benefit plan, not solely in payroll. Option C is incorrect because Workday does not prompt administrators automatically to update limits during enrollment events. Option D is also incorrect because Workday does not automatically adjust HSA limits; administrators must manually update them to reflect regulatory changes. Proper use of effective dating ensures accurate and compliant benefit plan configuration across plan years.

Answer : D

The correct answer is D because the Open Enrollment Status report in Workday provides a comprehensive view of benefit event activity across different statuses, including in progress, submitted, cancelled, closed, and finalized events. It is specifically designed to track enrollment progress and completion at a summarized level, often grouped by benefit group, allowing administrators to monitor participation and identify outstanding actions during enrollment cycles.

Option A is incorrect because Enrollment Count focuses on numerical summaries of enrollments rather than detailed status tracking across event stages. Option B is also incorrect because the Benefit Group Audit report is used to validate eligibility and identify workers assigned to multiple benefit groups, not to track event processing statuses. Option C is incorrect because Benefit Census provides a snapshot of current enrollments and participant data but does not track event lifecycle statuses. The Open Enrollment Status report is the appropriate tool for monitoring event progress and status breakdowns across benefit groups.

Answer : B

The correct answer is B because for an enrollment event type to appear to employees in self-service, the event must be configured as Worker Selectable. This setting controls whether employees can initiate that life event themselves from the Benefits and Pay Hub or other employee self-service entry points. If the Marriage event is not marked as worker selectable, it will not display as an available option when employees attempt to start a change benefits event.

Option A is incorrect because Route to Benefit Partner determines whether the event is routed for administrative review or handling, not whether the event appears to the employee as a selectable option. Option C is also incorrect because the Employee Cannot Report After Days to Enroll setting governs submission timing after the event date, not visibility in self-service. Option D is unrelated because Do Not Reprocess controls event reprocessing behavior and does not determine whether employees can initiate the event. To make a marriage life event visible and available in employee self-service, the event type must have the Worker Selectable checkbox enabled.

Answer : C

The correct answer is C because Workday allows insurance rates and calculated healthcare rates to incorporate demographic factors such as age and length of service when determining employee contributions or employer costs. These types of rates are designed to be dynamic and flexible, enabling organizations to apply tiered or variable pricing structures based on worker-specific attributes. For example, insurance plans often vary premiums based on age bands, while calculated healthcare rates can use formulas that consider service duration or other demographic criteria.

Option A is incorrect because flat healthcare rates apply a fixed cost regardless of employee characteristics, meaning demographic factors are not considered. Option B is incorrect because Benefits Annualized Rates (BAR) primarily standardize cost calculations over time and do not inherently support demographic-based variations. Option D is also incorrect because additional benefits rates are typically used for supplemental offerings and do not provide the same level of demographic-driven calculation capability. Therefore, insurance and calculated healthcare rates are the appropriate rate types for incorporating demographic factors in Workday Benefits configuration.

Answer : B

The correct answer is B because medical and dental plans typically follow a passive enrollment approach during Open Enrollment, meaning employees who take no action should automatically retain their current elections. In Workday, this behavior is controlled through the Defaulting Rules on the Coverage Rules tab of the Enrollment Event Rule. Selecting Default to Current Elections or Waive ensures that if an employee does not actively make changes, the system carries forward their existing elections into the new plan year.

This aligns with the requirement that employees remain enrolled in their prior medical and dental coverage unless they explicitly choose otherwise. Option A is incorrect because Priority Coverage is used when selecting among multiple available options rather than maintaining existing elections. Option C is not appropriate because it introduces unnecessary complexity and is not the standard configuration for passive enrollment scenarios. Option D is incorrect because Default to Waive would terminate coverage for employees who do not take action, which contradicts the requirement. Therefore, using Default to Current Elections or Waive ensures consistent continuation of coverage for passive enrollment plans like medical and dental.

Answer : A

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.

Answer : B

The correct answer is B because in Workday, Related Person Relationships are configurable and can be used across multiple contexts such as dependents, beneficiaries, and emergency contacts. The Restricted to Relationships field allows administrators to limit where a relationship type can be used. However, if this field is left blank, the relationship type becomes broadly available across all applicable areas, enabling it to be used flexibly for different purposes within the system.

Option A is incorrect because although Workday delivers some standard relationship types, they can be configured or extended as needed. Option C is incorrect because Workday does support tracking certain dependent-related data within benefits and eligibility contexts. Option D is also incorrect because Related Person Relationships are not restricted by benefit group; they are global configuration elements that apply across the tenant rather than being tied to specific benefit group eligibility structures. Therefore, leaving the restriction field blank allows maximum usability of a relationship type across different business processes.

Answer : C

The correct answer is C because for a benefit event to both trigger from a Leave of Absence business process and route to the benefits team, two key configurations must be present within the Enrollment Event Type. First, the event must be properly linked to the Leave of Absence business process in the Events and Reasons section so that Workday recognizes the staffing action as a trigger. Second, the Route to Benefits Partner checkbox must be selected so that once the event is initiated, it is automatically routed to the benefits team for review or processing.

Option A is incorrect because reinstatement configuration applies to rehire scenarios, not leave events. Option B is incorrect because Worker Selectable controls employee self-service visibility, not routing. Option D is partially correct regarding routing but incomplete, as without mapping the Leave event in Events and Reasons, the event will not trigger at all. Therefore, both mapping the Leave event and enabling routing are required to ensure proper event initiation and processing by the benefits team.

Answer : A

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.

Answer : B

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.

Answer : B

The correct answer is B because adding the Change Benefits for Life Event subprocess into the Change Job business process only enables the process flow. Workday still needs to know which specific HCM transaction should trigger the benefit event. That linkage is configured on Maintain Enrollment Event Types, where the administrator associates the enrollment event with the relevant business process and reason in the Events and Reasons section. By adding the Change Job business process there, Workday can recognize that a job change meeting the configured criteria should launch the related benefits event.

Option A is incorrect because a condition rule on the Change Benefits business process alone does not establish the event trigger source. Option C is not correct because a passive event is used for automatic plan changes based on eligibility or timing, not for linking a staffing transaction to a benefits event trigger. Option D is also incorrect because Enrollment Event Rules govern coverage timing and election behavior after the event is triggered; they do not define the originating HCM business process. The trigger source must be configured on the enrollment event type itself.

Answer : D

The correct answer is D because benefit events in Workday are highly configurable and designed to align with an organization's specific business processes and policy requirements. Administrators define event types such as life events, open enrollment, or administrative events based on company needs, including eligibility rules, timing, coverage start and end logic, and routing behavior. This flexibility allows organizations to tailor benefit administration to their workforce and regulatory environment.

Option A is incorrect because while Workday provides a framework and some sample configurations, benefit events themselves are not strictly system-delivered and must be configured by the organization. Option B is also incorrect because benefit events typically cannot be freely deleted once in use; instead, they are inactivated to preserve historical data integrity. Option C is incorrect because event closure timing is configurable and depends on settings like Days to Enroll or administrative processes, not an automatic 30-day rule. Therefore, benefit events are best understood as configurable components built to meet company-specific requirements.

Answer : B

The correct answer is B because medical and dental plans typically follow a passive enrollment approach during Open Enrollment, meaning employees who take no action should automatically retain their current elections. In Workday, this behavior is controlled through the Defaulting Rules on the Coverage Rules tab of the Enrollment Event Rule. Selecting Default to Current Elections or Waive ensures that if an employee does not actively make changes, the system carries forward their existing elections into the new plan year.

This aligns with the requirement that employees remain enrolled in their prior medical and dental coverage unless they explicitly choose otherwise. Option A is incorrect because Priority Coverage is used when selecting among multiple available options rather than maintaining existing elections. Option C is not appropriate because it introduces unnecessary complexity and is not the standard configuration for passive enrollment scenarios. Option D is incorrect because Default to Waive would terminate coverage for employees who do not take action, which contradicts the requirement. Therefore, using Default to Current Elections or Waive ensures consistent continuation of coverage for passive enrollment plans like medical and dental.

Answer : D

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.

Answer : A

The correct answer is A because the Start or Waive Coverage section of the Enrollment Event Rule is where Workday determines when benefit coverage becomes effective after an employee becomes eligible. In this scenario, the organization needs two pieces of timing logic applied in sequence: first, a 60-day waiting period from the hire date, and second, a rule that moves the actual coverage start date to the first day of the following month. This type of effective-date calculation belongs in the coverage start configuration tied to the enrollment event.

Option B is incorrect because a Benefit Plan Eligibility Rule determines whether the employee qualifies for the plan, but it does not control the detailed coverage effective-date calculation sequence. Option C identifies the event itself, such as hire or newly eligible, but does not hold the specific start-date logic needed here. Option D is also incorrect because Benefit Groups are used to organize populations for benefits eligibility and plan assignment, not to calculate waiting periods and coverage effective dates. For waiting period and start-date timing logic, the correct configuration point is Start or Waive Coverage.

Answer : C

The correct answer is C because reinstatement of benefits for rehired employees is configured through an Enrollment Event Type, not at the individual benefit plan level. Workday uses the enrollment event type to define whether a rehire should trigger reinstatement behavior, how long the reinstatement window remains valid, and which business processes and reasons should launch that event. By selecting Reinstatement Event and setting the Reinstatement Period to six months, the system can determine whether a rehired employee falls within the allowed timeframe to restore prior benefit elections.

Associating the event with the Hire Employee business process and the correct rehire reason ensures the event is triggered automatically when the rehire occurs. Option A is incorrect because reinstatement is not configured on a benefit plan itself. Option B is not appropriate because manual reinstatement introduces inconsistency and bypasses standard event automation. Option D is also incorrect because a step delay in the business process does not define reinstatement logic or prior-election restoration rules. The correct design is to configure a reinstatement-enabled enrollment event type tied to the rehire process.

Answer : D

The correct answer is D because the Benefit Corrections in Progress Audit report is specifically designed to identify benefit events that require administrative action, including those that must be reviewed, corrected, or submitted by a benefits partner or administrator. This report highlights events that are not yet finalized and may require intervention, making it especially useful for tracking administrative workload and ensuring no pending corrections are overlooked.

Option A is incorrect because Open Enrollment Status focuses on mass enrollment events and their progress, not specifically on events requiring administrative submission. Option B is also incorrect because Benefit Group Audit is used to review eligibility and group assignment issues, not event submission tracking. Option C is partially related, as Benefit Event Status shows the status of events, but it does not specifically isolate events that require action from a benefits partner. The Benefit Corrections in Progress Audit report provides targeted visibility into events needing administrative completion, making it the correct choice.

Answer : A

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.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : A

The correct answer is A because the Start or Waive Coverage section of the Enrollment Event Rule is where Workday determines when benefit coverage becomes effective after an employee becomes eligible. In this scenario, the organization needs two pieces of timing logic applied in sequence: first, a 60-day waiting period from the hire date, and second, a rule that moves the actual coverage start date to the first day of the following month. This type of effective-date calculation belongs in the coverage start configuration tied to the enrollment event.

Option B is incorrect because a Benefit Plan Eligibility Rule determines whether the employee qualifies for the plan, but it does not control the detailed coverage effective-date calculation sequence. Option C identifies the event itself, such as hire or newly eligible, but does not hold the specific start-date logic needed here. Option D is also incorrect because Benefit Groups are used to organize populations for benefits eligibility and plan assignment, not to calculate waiting periods and coverage effective dates. For waiting period and start-date timing logic, the correct configuration point is Start or Waive Coverage.

Answer : C

The correct answer is C because Workday Benefits configuration starts with the foundational components that define how a benefit offering is structured. When introducing a completely new type of benefit such as a gym membership, the system must first recognize the benefit category through an appropriate coverage type. The coverage type serves as a core setup element that supports plan creation and determines how the plan is classified within the benefits framework.

Option A is not correct because rates are generally configured after the underlying plan structure exists. Rates define pricing or cost-sharing, but they do not establish the foundational setup needed to create a new benefit offering. Option B is also incorrect because benefit groups are used to organize worker eligibility and enrollment populations, not to establish the base benefit component required for a new plan type. Option D applies to dependent or related-person scenarios, such as spouse or child coverage, which is not relevant for a gym membership benefit. In this case, defining the proper coverage type is the necessary first step before the plan itself can be configured.

Answer : C

The correct answer is C because a Health Care Classification is typically required in Workday when configuring U.S. medical plans. This classification supports plan identification and compliance-related processing within the United States benefits framework. It is used to distinguish the type of medical coverage being offered and helps align the plan with U.S.-specific benefits administration requirements, reporting needs, and downstream processing. Since U.S. medical plans are subject to particular health coverage categorizations, including this value during plan setup is an essential part of proper configuration.

Option B is not correct because Canadian medical plans do not use the same U.S.-specific health care classification requirement. Option A and Option D are also incorrect because Health Savings Accounts are different benefit types from medical plans. Although an HSA may be linked to a medical election in the U.S., the question asks specifically about including a Health Care Classification in the plan setup, which is associated with the medical plan configuration itself rather than the savings account plan. Therefore, the scenario that requires this setup element is a Medical plan for USA.

Answer : C

The correct answer is C because a Passive event in Workday is used when benefit changes must occur automatically without requiring employee action. In this scenario, the new plan is triggered when employees reach a 12-month service milestone, and the requirement is to automatically transition them to the new plan on their anniversary date. Passive events are designed for exactly this type of situation, where the system enforces enrollment changes based on predefined eligibility conditions or milestones.

Option A is incorrect because Open Enrollment applies to all eligible employees during a scheduled enrollment window and requires employee participation. Option B is incorrect because New Hire events only apply at the time of hire, not for service anniversaries. Option D is also incorrect because Worker Selectable events require the employee to actively make a choice, which contradicts the requirement for automatic enrollment. A Passive event ensures the system evaluates eligibility at the 12-month mark and applies the new plan without requiring any employee interaction, making it the correct configuration approach.

Answer : B

The correct answer is B because Workday life event reporting can be restricted by enrollment timing rules tied to the event configuration. When an employee reports the birth of a child, the event must usually be submitted within a defined number of days from the event date. If the Employee Cannot Report After Days to Enroll setting is enabled, Workday prevents the worker from submitting the event once that reporting window has expired. In this scenario, the child's birth occurred on April 30 and the employee attempted to report it on June 30, which is typically outside the allowed time frame for that qualifying life event.

Option A is incorrect because missing coverage types would affect which benefits can be changed, but it would not specifically explain a timing-based submission error on the event itself. Option C is unrelated, since account activation does not determine whether a valid life event can be submitted after the deadline. Option D is also incorrect because benefit group overlap is an eligibility and configuration issue, not the reason for a late event reporting error. The error is caused by the event submission window having expired.

Answer : C

The correct answer is C because coordination of events in Workday Benefits is designed to manage how multiple benefit events interact with each other, especially when they overlap in timing or impact similar coverage types. While coordination is useful for handling standard life events and ensuring proper sequencing, it is generally recommended to turn off coordination for mass events, such as Open Enrollment or large-scale administrative events.

Mass events typically involve a large population of employees and are intended to process uniformly without being impacted by other concurrent or prior events. If coordination is left enabled, it can introduce unnecessary complexity, delays, or unintended dependencies between events, potentially preventing mass processing from completing efficiently. Disabling coordination ensures that mass events run independently and consistently across all eligible employees.

Option A is incorrect because HR-related events often benefit from coordination to ensure proper sequencing and data integrity. Option B is not correct because passive events may still require coordination depending on configuration. Option D is incorrect because coordination is an important feature and should not be universally disabled. Therefore, the best practice is to turn off coordination specifically for mass events.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : B

The correct answer is B because a Calculated Health Care Rate is designed for medical plan pricing that depends on multiple worker-specific and election-specific factors. In this scenario, the rate must vary based on the employee's age, tobacco usage, and the coverage target selected during enrollment. That combination requires a configurable rate structure capable of evaluating demographic factors and enrollment choices together, which is exactly what a calculated health care rate supports in Workday.

Option A is incorrect because a flat health care rate applies a fixed amount and does not dynamically adjust based on employee attributes or selected coverage targets. Option C is not the best fit because a Benefit Annualized Rate is intended to standardize cost presentation or annualization logic rather than drive complex medical pricing based on multiple eligibility and rating factors. Option D is also incorrect because a benefit surcharge is generally used to add an extra charge for a specific condition, such as tobacco use, but it does not by itself represent the full rate structure for the medical plan. A calculated health care rate is the appropriate configuration when several variables determine the employee's cost.

Answer : C

The correct answer is C because Workday Benefits configuration starts with the foundational components that define how a benefit offering is structured. When introducing a completely new type of benefit such as a gym membership, the system must first recognize the benefit category through an appropriate coverage type. The coverage type serves as a core setup element that supports plan creation and determines how the plan is classified within the benefits framework.

Option A is not correct because rates are generally configured after the underlying plan structure exists. Rates define pricing or cost-sharing, but they do not establish the foundational setup needed to create a new benefit offering. Option B is also incorrect because benefit groups are used to organize worker eligibility and enrollment populations, not to establish the base benefit component required for a new plan type. Option D applies to dependent or related-person scenarios, such as spouse or child coverage, which is not relevant for a gym membership benefit. In this case, defining the proper coverage type is the necessary first step before the plan itself can be configured.

Answer : C

The correct answer is C because when a new employee is hired after Open Enrollment has already been initiated, Workday typically prioritizes the employee's new hire benefits event first. The system does this to ensure the worker completes their initial eligibility-based elections before any broader enrollment event is coordinated for them. Once the new hire event is completed, Workday can then reprocess the Open Enrollment event so the employee is brought into the same enrollment cycle as others in the benefit group, if applicable.

This behavior is part of Workday's event coordination logic, which prevents overlapping benefits tasks from creating conflicting elections or duplicate enrollment opportunities. Option A is incorrect because marking an event as Worker Selectable affects self-service visibility, not whether a new hire initially receives an OE inbox task. Option B is unrelated because a Reinstatement Event applies to rehire scenarios, not newly hired workers entering an open enrollment cycle. Option D is also incorrect because No Changes Allowed would restrict election changes within an event, but it would not explain why the OE task is not initially present. The missing task is due to reprocessing after completion of the new hire event.

Answer : D

The correct answer is D because the Open Enrollment Status report is specifically designed to manage and monitor mass benefit events, such as Open Enrollment. This report provides administrators with visibility into the status of all enrollment events across the organization, including those that are in progress, submitted, or not yet started. Importantly, it also allows administrators to take action on these events, including closing and finalizing mass events once the enrollment period ends.

Option A is incorrect because the Benefit Census report provides a snapshot of current enrollments, not event processing actions. Option B is incorrect because Benefit Group Audit focuses on eligibility and group assignment issues. Option C is partially related, as Benefit Event Status shows event progress, but it is not the primary report used for managing and finalizing mass enrollment events. The Open Enrollment Status report is specifically built to support large-scale enrollment tracking and administrative actions, making it the correct choice for closing and finalizing mass benefit events.

Answer : A

The correct answer is A because Workday benefits administration requires the administrator to first address the benefit elections tied to the dependent before removing the related person from active use. When a domestic partnership or marriage ends, the correct process is to run the appropriate life event so the system can properly terminate the dependent's benefit coverage, update eligibility, and maintain an accurate audit trail of the enrollment changes. After the benefit event removes the dependent from all applicable elections, the administrator can then inactivate the dependent through related actions on the dependent record.

Option B is incorrect because deleting a dependent from the system is not the proper approach and would not preserve history appropriately. Option C is also incorrect because deleting the dependent profile does not represent the standard Workday process for handling dependent removal from benefits. Option D is incomplete because simply inactivating the dependent profile does not correctly process the benefits event or ensure elections are ended through the proper event-driven mechanism. Workday relies on the life event first, followed by dependent inactivation.

Answer : C

The correct answer is C because benefit groups in Workday are typically created when distinct populations of workers need different overall benefits structures, often due to major organizational differences such as country, legal entity, or currency. When employees are located in different countries like the United States and the United Kingdom, they commonly have different benefit programs, regulatory requirements, providers, and plan pricing currencies. In that situation, separate benefit groups help organize eligibility and ensure each population is tied to the correct set of plans and configuration rules.

Option A is not the best reason because holding multiple positions does not by itself require separate benefit groups; eligibility is usually managed through worker and job-based rules. Option B is more appropriately handled through plan-level eligibility rules rather than creating an entirely separate benefit group for one age-based condition. Option D concerns differences within medical plan design, such as coverage targets, which can be handled at the plan configuration level rather than by creating separate groups. Benefit groups should be used when broad populations require distinct benefits frameworks, and different countries with different currencies are a strong example of that need.

Answer : A

The correct answer is A because in Workday, when a benefits partner needs to assist an employee directly with their open enrollment event, they must access the employee's inbox tasks and event experience. This is accomplished by using the Start Proxy functionality, which allows the administrator to act on behalf of the employee and view exactly what the employee sees, including the Change Benefits task associated with open enrollment.

Option B (Open Enrollment Status Report) and D (Benefit Events Status Report) are reporting tools used to monitor event progress, status, and completion but do not provide direct access to perform or assist with the employee's enrollment elections. Option C (Initiate Open Enrollment task) is used to launch the event for a population, not to access or assist with an already initiated employee event.

Using proxy ensures that the benefits partner can guide or complete the enrollment accurately within the employee's context, maintaining consistency in elections, validations, and user experience while following Workday security and audit controls.

Answer : B

The correct answer is B because a Calculated Health Care Rate is designed for medical plan pricing that depends on multiple worker-specific and election-specific factors. In this scenario, the rate must vary based on the employee's age, tobacco usage, and the coverage target selected during enrollment. That combination requires a configurable rate structure capable of evaluating demographic factors and enrollment choices together, which is exactly what a calculated health care rate supports in Workday.

Option A is incorrect because a flat health care rate applies a fixed amount and does not dynamically adjust based on employee attributes or selected coverage targets. Option C is not the best fit because a Benefit Annualized Rate is intended to standardize cost presentation or annualization logic rather than drive complex medical pricing based on multiple eligibility and rating factors. Option D is also incorrect because a benefit surcharge is generally used to add an extra charge for a specific condition, such as tobacco use, but it does not by itself represent the full rate structure for the medical plan. A calculated health care rate is the appropriate configuration when several variables determine the employee's cost.

Answer : A

The correct answer is A because this scenario describes a benefit that employees may elect during the year as a new enrollment opportunity, which means the event belongs on the Start/Waive tab of the Enrollment Event Rule. The requirement also states that only the gym membership plan should be available and that both coverage and payroll deductions should begin on the first of the following month. The Start/Waive configuration is where Workday controls which coverage type is opened for election and how coverage and deduction effective dates are calculated for that event.

Option B is incorrect because the Loss of Coverage tab is used when coverage is ending, not when a worker is newly electing a plan. Option C is also incorrect because it would start coverage and deductions on the event date, which does not meet the stated timing requirement. Option D is incorrect because enrollment event rules are driven by event types, not by adding a coverage type in place of the event itself. Therefore, the administrator should add the gym membership event type to Start/Waive and configure the start logic for the first of the following month.

Answer : C

The correct answer is C because reinstatement of benefits for rehired employees is configured through an Enrollment Event Type, not at the individual benefit plan level. Workday uses the enrollment event type to define whether a rehire should trigger reinstatement behavior, how long the reinstatement window remains valid, and which business processes and reasons should launch that event. By selecting Reinstatement Event and setting the Reinstatement Period to six months, the system can determine whether a rehired employee falls within the allowed timeframe to restore prior benefit elections.

Associating the event with the Hire Employee business process and the correct rehire reason ensures the event is triggered automatically when the rehire occurs. Option A is incorrect because reinstatement is not configured on a benefit plan itself. Option B is not appropriate because manual reinstatement introduces inconsistency and bypasses standard event automation. Option D is also incorrect because a step delay in the business process does not define reinstatement logic or prior-election restoration rules. The correct design is to configure a reinstatement-enabled enrollment event type tied to the rehire process.

Answer : C

The correct answer is C because for a benefit event to both trigger from a Leave of Absence business process and route to the benefits team, two key configurations must be present within the Enrollment Event Type. First, the event must be properly linked to the Leave of Absence business process in the Events and Reasons section so that Workday recognizes the staffing action as a trigger. Second, the Route to Benefits Partner checkbox must be selected so that once the event is initiated, it is automatically routed to the benefits team for review or processing.

Option A is incorrect because reinstatement configuration applies to rehire scenarios, not leave events. Option B is incorrect because Worker Selectable controls employee self-service visibility, not routing. Option D is partially correct regarding routing but incomplete, as without mapping the Leave event in Events and Reasons, the event will not trigger at all. Therefore, both mapping the Leave event and enabling routing are required to ensure proper event initiation and processing by the benefits team.

Answer : A

The correct answer is A because the Start or Waive Coverage section of the Enrollment Event Rule is where Workday determines when benefit coverage becomes effective after an employee becomes eligible. In this scenario, the organization needs two pieces of timing logic applied in sequence: first, a 60-day waiting period from the hire date, and second, a rule that moves the actual coverage start date to the first day of the following month. This type of effective-date calculation belongs in the coverage start configuration tied to the enrollment event.

Option B is incorrect because a Benefit Plan Eligibility Rule determines whether the employee qualifies for the plan, but it does not control the detailed coverage effective-date calculation sequence. Option C identifies the event itself, such as hire or newly eligible, but does not hold the specific start-date logic needed here. Option D is also incorrect because Benefit Groups are used to organize populations for benefits eligibility and plan assignment, not to calculate waiting periods and coverage effective dates. For waiting period and start-date timing logic, the correct configuration point is Start or Waive Coverage.

Answer : B

The correct answer is B because in Workday, Related Person Relationships are configurable and can be used across multiple contexts such as dependents, beneficiaries, and emergency contacts. The Restricted to Relationships field allows administrators to limit where a relationship type can be used. However, if this field is left blank, the relationship type becomes broadly available across all applicable areas, enabling it to be used flexibly for different purposes within the system.

Option A is incorrect because although Workday delivers some standard relationship types, they can be configured or extended as needed. Option C is incorrect because Workday does support tracking certain dependent-related data within benefits and eligibility contexts. Option D is also incorrect because Related Person Relationships are not restricted by benefit group; they are global configuration elements that apply across the tenant rather than being tied to specific benefit group eligibility structures. Therefore, leaving the restriction field blank allows maximum usability of a relationship type across different business processes.

Answer : A

The correct answer is A because in Workday, when a benefits partner needs to assist an employee directly with their open enrollment event, they must access the employee's inbox tasks and event experience. This is accomplished by using the Start Proxy functionality, which allows the administrator to act on behalf of the employee and view exactly what the employee sees, including the Change Benefits task associated with open enrollment.

Option B (Open Enrollment Status Report) and D (Benefit Events Status Report) are reporting tools used to monitor event progress, status, and completion but do not provide direct access to perform or assist with the employee's enrollment elections. Option C (Initiate Open Enrollment task) is used to launch the event for a population, not to access or assist with an already initiated employee event.

Using proxy ensures that the benefits partner can guide or complete the enrollment accurately within the employee's context, maintaining consistency in elections, validations, and user experience while following Workday security and audit controls.

Answer : B

The correct answer is B because a Calculated Health Care Rate is designed for medical plan pricing that depends on multiple worker-specific and election-specific factors. In this scenario, the rate must vary based on the employee's age, tobacco usage, and the coverage target selected during enrollment. That combination requires a configurable rate structure capable of evaluating demographic factors and enrollment choices together, which is exactly what a calculated health care rate supports in Workday.

Option A is incorrect because a flat health care rate applies a fixed amount and does not dynamically adjust based on employee attributes or selected coverage targets. Option C is not the best fit because a Benefit Annualized Rate is intended to standardize cost presentation or annualization logic rather than drive complex medical pricing based on multiple eligibility and rating factors. Option D is also incorrect because a benefit surcharge is generally used to add an extra charge for a specific condition, such as tobacco use, but it does not by itself represent the full rate structure for the medical plan. A calculated health care rate is the appropriate configuration when several variables determine the employee's cost.

Answer : A

The correct answer is A because once Open Enrollment has been launched with incorrect benefit groups, the proper corrective action in Workday is to rescind the open enrollment event. Rescinding reverses the event for affected employees and removes the enrollment tasks that were incorrectly generated. This allows the administrator to correct the configuration and relaunch the event with the appropriate benefit groups.

Option B is incorrect because Open Enrollment cannot simply be ''corrected'' after it has been launched; the population tied to the event is already established and must be reset. Option C is not relevant because sending reminders does not fix incorrect group assignment. Option D is also incorrect because canceling and re-initiating without rescinding would leave prior events and data inconsistencies in place.

Rescinding ensures a clean reset of the enrollment process, allowing administrators to properly configure and relaunch Open Enrollment for the correct population without conflicts or duplicate events.

Answer : C

The correct answer is C because Workday supports automatic enrollment for plans that should be assigned to all eligible employees without requiring them to actively make an election. For an employee assistance plan offered at no cost, the standard configuration is to enable Auto Enroll on the benefit plan itself. This tells the system to automatically place eligible workers into the plan when a relevant benefits event occurs. To make that automation work correctly, the corresponding benefit events must reference the plan's benefit coverage type, ensuring the plan is included when the event is processed.

Option A is incorrect because a benefit default influences default election behavior during an event, but it is not the primary configuration for systematically auto-enrolling employees into the plan. Option B is also incorrect because Only One Election limits election behavior within a coverage type and does not cause automatic enrollment. Option D is unrelated because enrollment instructions provide guidance to employees, not automation. When the goal is to automatically enroll all eligible workers in a no-cost plan, the correct approach is to enable Auto Enroll on the plan and ensure relevant events include that coverage type.

Answer : A

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.