C_THR81 Employee Central Core Practice Question
A company wants to track employee dependents for benefits purposes. Each employee can have multiple dependents, and each dependent must store name, date of birth, relationship, and a flag indicating whether they are covered under the employee's health plan. The data must be reportable and editable from the employee's profile. Which configuration approach should the administrator use?
⚠ Common exam trap
The trap here is choosing a foundation object or standard portlet for employee-specific one-to-many data, when a custom MDF object with a composite association is the correct pattern.
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 new MDF object 'Dependent' with a composite association to Employee, and add a 'Dependents' portlet or section to the employee profile.
The appropriate approach is a custom MDF object with a composite association to Employee, which naturally supports multiple records per employee and stores all required attributes. Surfacing it on the employee profile enables editing and reporting. The other options either cannot handle one-to-many data or misuse foundation objects and standard portlets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a new foundation object 'Dependent' and assign it as a picklist to the Personal Information portlet.
Why it's wrong here
Foundation objects are intended for shared reference data, not for employee-specific records with associations. Using a foundation object as a picklist cannot store per-employee dependent details such as date of birth or coverage flag, so it does not meet the requirement.
- ✗
Add multiple sets of dependent fields directly to the Personal Information portlet as repeating fields.
Why it's wrong here
Personal Information does not support repeating groups of dependent fields in a scalable way, and adding many fields would be inflexible. This approach cannot cleanly handle an arbitrary number of dependents per employee and complicates reporting and maintenance.
- ✗
Use the Employee Profile portlet's built-in Dependents section and enable the health plan coverage flag through a business rule.
Why it's wrong here
A built-in Dependents section may not exist or may not support the specific fields and reporting needs described. Relying on a business rule to add a coverage flag does not create the underlying data structure, so the requirement for persistent, reportable dependent records would not be met.
- ✓
Create a new MDF object 'Dependent' with a composite association to Employee, and add a 'Dependents' portlet or section to the employee profile.
Why this is correct
A custom MDF object with a composite association to Employee supports multiple dependent records per employee, stores the required fields, and can be surfaced on the profile for editing and reporting. This is the standard pattern for one-to-many custom data in Employee Central.
About these practice questions
This C_THR81 question is part of Courseiva's 108-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.