C_THR81 Employee Central Core Practice Question
A company needs to track employee assignments to different projects. Each employee can be assigned to multiple projects simultaneously, and each assignment has a start date, end date, and role. The company wants to maintain a history of all assignments. Which MDF object configuration is most appropriate?
⚠ Common exam trap
The trap here is trying to use existing objects like Job Information or simple picklists, which cannot handle multiple detailed assignments with history.
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 MDF object 'Project Assignment' with a field 'Employee' as an association to the Employee object, and enable 'Effective Dating' on the object.
The requirement is to track multiple project assignments per employee with details and history. A separate MDF object with an association to Employee and effective dating supports multiple records, stores assignment-specific data, and maintains history. The other options either limit the number of assignments, lack detail fields, or do not provide historical tracking.
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 the existing 'Job Information' object and add fields for project details.
Why it's wrong here
Job Information is designed for employment details and typically holds one record per employee at a time. Adding project fields there would not support multiple simultaneous assignments or historical tracking. It would also clutter the Job Information object. A separate object is the correct approach.
- ✗
Add multiple fields to the Employee object for Project 1, Project 2, etc., with start and end dates.
Why it's wrong here
This approach limits the number of projects an employee can be assigned to and does not scale well. It also does not easily maintain history because you would need to track changes over time. A separate object is more flexible and maintainable. This configuration is not suitable for multiple simultaneous assignments with history.
- ✗
Create a MDF object 'Project' and use a multi-select picklist in Employee to assign projects.
Why it's wrong here
A multi-select picklist in Employee would allow selecting multiple projects, but it cannot store additional attributes like start date, end date, and role for each assignment. It also does not maintain history. Therefore, this does not meet the requirement for detailed assignment data and history.
- ✓
Create a MDF object 'Project Assignment' with a field 'Employee' as an association to the Employee object, and enable 'Effective Dating' on the object.
Why this is correct
A separate MDF object for Project Assignment with an association to Employee allows multiple records per employee. Enabling effective dating maintains a history of assignments with start and end dates. This configuration supports multiple simultaneous assignments and historical tracking, meeting all requirements. The association links each assignment to an employee.
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.