C_THR81 Employee Central Core Practice Question
An administrator needs to create a new MDF object to track employee visas. The object must store the visa type, issue date, expiry date, and a link to the employee. The administrator wants to ensure that the visa expiry date is always after the issue date. Which feature should the administrator use to enforce this validation?
⚠ Common exam trap
The trap here is thinking that field criteria can compare two date fields, when they can only control field properties based on simple conditions.
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 MDF object that triggers on save and validates that the expiry date is after the issue date.
Business rules on MDF objects can perform cross-field validations on save. By creating a rule that compares the issue date and expiry date and raises an error when the expiry date is not after the issue date, the administrator enforces the required validation. This is the standard method for ensuring data consistency in custom MDF objects.
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 workflow that routes the visa record to a manager for approval if the expiry date is before the issue date.
Why it's wrong here
A workflow can route records for approval, but it does not prevent the invalid data from being saved. The requirement is to enforce that the expiry date is always after the issue date, which means the system should reject the save if the condition is not met. A workflow would only add a manual check, which is not automatic and does not guarantee data integrity.
- ✓
Create a business rule on the MDF object that triggers on save and validates that the expiry date is after the issue date.
Why this is correct
Business rules on MDF objects can be configured to trigger on save and perform validations. By creating a rule that checks if the expiry date is after the issue date and raises an error if not, the administrator ensures data integrity. This is a standard approach for cross-field validation within MDF objects and is fully supported in Employee Central.
- ✗
Configure a field criteria on the expiry date field to make it required only when the issue date is populated.
Why it's wrong here
Field criteria can control whether a field is required, visible, or editable based on other fields, but they cannot compare two date fields to enforce that one is after the other. This approach would only ensure that expiry date is filled when issue date is present, but it would not validate the chronological order, so it does not meet the requirement.
- ✗
Use a picklist for the expiry date that only allows dates after the issue date.
Why it's wrong here
Picklists are used for predefined value sets and cannot dynamically restrict date selections based on another date field. Date fields in MDF objects are typically free-text or date pickers, not picklists. This approach is not feasible and would not enforce the validation.
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.