C_THR81 Employee Central Core Practice Question
An Employee Central consultant is configuring the MDF object 'Benefits Enrollment' for a client. HR requires that when an employee selects a 'Medical Plan' record, the 'Dependent Coverage' field must be populated before the record can be saved. The consultant needs to enforce this dependency. Which MDF object configuration should the consultant use?
⚠ Common exam trap
The trap here is assuming that making a field required or visible conditionally will enforce its population, but only a validation rule can prevent saving incomplete data.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a business rule on the 'Benefits Enrollment' object that triggers on save and validates the 'Dependent Coverage' field when 'Medical Plan' is not empty.
The requirement is to conditionally require Dependent Coverage when Medical Plan is selected. A business rule on save can check both fields and throw an error if the condition is unmet. This is the standard way to enforce conditional validation on MDF objects. Required fields and visibility dependencies do not provide conditional enforcement, and picklist dependencies only filter options.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a picklist dependency to ensure that 'Dependent Coverage' options are filtered based on the selected 'Medical Plan'.
Why it's wrong here
Picklist dependencies filter the available options in a picklist based on another field's value. They do not enforce that a value must be selected. Even with filtered options, the field could remain blank. This addresses the set of choices, not the requirement that a choice must be made. Therefore, it does not satisfy the mandatory condition.
- ✗
Set the 'Dependent Coverage' field as a required field on the 'Benefits Enrollment' object.
Why it's wrong here
Marking a field as required enforces that it is populated on every record, regardless of the selected Medical Plan. It cannot conditionally require the field only when a Medical Plan is chosen. This would force Dependent Coverage even for employees waiving coverage, creating unnecessary data entry and potential errors. The requirement is conditional, so a simple required flag is insufficient.
- ✗
Configure a field dependency in the 'Benefits Enrollment' object definition to make 'Dependent Coverage' visible only when 'Medical Plan' is selected.
Why it's wrong here
Field dependencies control visibility or filter values, not mandatory data entry. Making Dependent Coverage visible when Medical Plan is selected does not prevent saving the record with an empty value. The requirement is to enforce population, not just visibility. Visibility alone does not guarantee data completeness, so this approach fails to meet the validation need.
- ✓
Create a business rule on the 'Benefits Enrollment' object that triggers on save and validates the 'Dependent Coverage' field when 'Medical Plan' is not empty.
Why this is correct
A business rule on the MDF object can evaluate the Medical Plan value on save and raise an error if Dependent Coverage is empty. This enforces the conditional dependency exactly as required. MDF business rules support onSave validation, making this the appropriate configuration to ensure data integrity without over-constraining other scenarios.
About these practice questions
One of 108 original C_THR81 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official SAP exam blueprint
This C_THR81 practice question is part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C_THR81 exam.