C_THR81 Employee Central Core Practice Question
A SuccessFactors administrator is defining a new MDF object called 'CompanyVehicle' to track the vehicles assigned to employees. Each vehicle must be linked to exactly one employee, and an employee may be assigned several vehicles over time. The administrator wants the association field on the CompanyVehicle object to reference the Employee object. Which association type must be configured on the CompanyVehicle object to meet this requirement?
⚠ Common exam trap
Watch out — candidates often confuse the direction of the association and assuming that a one-to-many association should be created on the object that has many records, when the many-to-one association belongs on the child object that references the single parent.
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
✓
Many-to-One association from CompanyVehicle to Employee
The requirement is that each vehicle record points to exactly one employee, while an employee can be referenced by many vehicle records. In MDF, that cardinality is modelled with a many-to-one association placed on the child object (CompanyVehicle) and pointing to the parent object (Employee). The other association types either reverse the ownership, filter values without storing a link, or impose the wrong cardinality.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Many-to-One association from CompanyVehicle to Employee
Why this is correct
A many-to-one association defined on CompanyVehicle pointing to Employee allows many vehicle records to reference the same employee while each vehicle record references only one employee, exactly matching the stated cardinality. This is the standard way in MDF to model a lookup to a parent object such as Employee from a child object like CompanyVehicle.
- ✗
Composite association
Why it's wrong here
A composite association creates a parent-child relationship where the child record cannot exist independently of the parent, and the parent is the owning object. Here the owning object would be the vehicle, not the employee, so a composite association would make the vehicle the parent of the employee, which is the reverse of the requirement and would also restrict an employee from owning multiple vehicles.
- ✗
Valid When association
Why it's wrong here
A Valid When association is used to filter the values available in a field based on the value of another field, such as restricting the picklist of positions by the selected department. It does not create a persistent link between two object records, so it cannot record which employee a vehicle is assigned to and would not store the relationship at all.
- ✗
One-to-Many association from CompanyVehicle to Employee
Why it's wrong here
A one-to-many association is defined on the parent object and points to many child records; placing it on CompanyVehicle would imply one vehicle links to many employees, which contradicts the requirement that each vehicle belongs to exactly one employee. The direction and cardinality are both wrong for this scenario, so it cannot be the correct configuration.
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.