C_THR81 Employee Central Core Practice Question
An HR administrator needs to ensure that when an employee's date of birth is entered in Employee Central, it is automatically validated to be at least 18 years before the current date. Which feature should the administrator use?
⚠ Common exam trap
Test-takers frequently confuse validation with approval; workflows do not enforce data constraints, only business rules do.
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
✓
Business rule with a date validation on the Date of Birth field in the Personal Information portlet.
A business rule on the Date of Birth field is the correct way to enforce age validation. It can dynamically compare the entered date to the current date and block saving if the employee is under 18. This ensures data accuracy at the point of entry without additional workflows or 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.
- ✗
Workflow that requires manager approval if the employee is under 18.
Why it's wrong here
A workflow adds an approval step but does not automatically validate the age. The requirement is to ensure the date is at least 18 years before the current date, which is a data validation, not an approval process. Workflows are for approvals, not for enforcing data constraints. This approach would not prevent invalid data entry.
- ✓
Business rule with a date validation on the Date of Birth field in the Personal Information portlet.
Why this is correct
Business rules can be configured to validate the Date of Birth field against the current date, ensuring the employee is at least 18 years old. The rule can trigger on save and display an error if the condition is not met. This is the standard approach for field-level validation in Employee Central.
- ✗
Custom MDF object to store birth dates and a scheduled job to validate age daily.
Why it's wrong here
Creating a custom MDF object for birth dates duplicates data and does not integrate with the standard Personal Information portlet. A scheduled job would validate after the fact, not on entry. This approach is overly complex and does not prevent invalid data at the point of entry. Standard fields should be used with business rules.
- ✗
Field-level picklist restriction on the Date of Birth field to only allow dates before a certain year.
Why it's wrong here
Picklists are used for predefined lists of values, not for date fields. You cannot restrict a date field with a picklist. Date fields require validation rules to enforce dynamic conditions like age. This option is technically not feasible in Employee Central.
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.