C_THR81 Employee Central Core Practice Question
An administrator needs to create a new MDF object in Employee Central to store employee visa records. The object must reference the existing Employee object so that each visa record is linked to a specific employee. Which configuration step is required to establish this link?
⚠ Common exam trap
Watch out — candidates often confuse a field that stores an identifier with a field that creates a relationship; only an Association field type builds the object-to-object link.
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
✓
Add a field of type 'Association' on the visa object that references the Employee object.
Linking a custom MDF object to the Employee object requires an Association field that references Employee. Associations create the underlying relationship used by the system to display related records, enforce integrity, and support reporting. Picklists, string fields, and business rules cannot create that structural link, so they do not satisfy the requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a business rule that copies the employee ID into the visa object on save.
Why it's wrong here
A business rule can populate a field, but it does not establish a structural relationship between two MDF objects. The requirement is to link records, which is a data model concern solved by an association field. A rule would also depend on a field existing to hold the value, and it would not enable navigation or integrity checks between the objects.
- ✓
Add a field of type 'Association' on the visa object that references the Employee object.
Why this is correct
An Association field type in MDF is specifically designed to create a relationship between a custom object and another object, such as Employee. By defining an association to the Employee object, each visa record can be linked to the correct employee, enabling the object to appear on the employee's profile and supporting reporting. This is the standard mechanism for object-to-object relationships in MDF.
- ✗
Create a picklist with all employee IDs and use it as a field on the visa object.
Why it's wrong here
A picklist is a static list of values and is not suited to referencing dynamic employee records. Employee IDs change frequently as people join and leave, so a picklist would quickly become stale and would not create a true relationship. Picklists are used for enumerated values such as visa type or status, not for linking to another object.
- ✗
Add a field of type 'String' and manually enter the employee's user ID.
Why it's wrong here
A string field can store an employee identifier, but it does not create a relationship in the data model. Without an association, the system cannot navigate from the visa record to the employee, cannot enforce referential integrity, and cannot display the record in the employee's portlet. Manual entry also introduces data quality risks such as typos.
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.