C_THR81 Employee Central Core Practice Question
An administrator is configuring the 'Job Information' portlet and needs to ensure that the 'Employee Class' field is required for all employees except those with the 'Employment Type' of 'Intern'. Which configuration should the administrator use to achieve this?
⚠ Common exam trap
The trap here is assuming that portlet-level required settings can be conditionally overridden by business rules, when in fact conditional requiredness must be implemented entirely through business rules.
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
✓
Use a business rule on the 'Job Information' object that triggers on save and validates that Employee Class is populated unless Employment Type is 'Intern'.
To conditionally require Employee Class, a business rule on Job Information is needed. The rule can check if Employee Class is empty and Employment Type is not 'Intern', then throw an error. This enforces the requirement only for non-interns, allowing interns to save without the field. It is a standard use of business rules for dynamic validation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the 'Employee Class' field as required in the Job Information portlet configuration, and then create a business rule to make it optional when Employment Type is 'Intern'.
Why it's wrong here
Making a field required at the portlet level applies universally and cannot be overridden by a business rule to make it optional. Business rules can set field properties, but required fields are enforced at the UI level and cannot be conditionally relaxed by rules. This approach would prevent saving for interns.
- ✗
Configure a picklist for Employee Class that excludes 'Intern' and set the field as required.
Why it's wrong here
Excluding 'Intern' from the picklist would prevent selecting that employment type, not conditionally require Employee Class. This does not meet the requirement and would cause data issues for interns. The field requiredness must be conditional based on Employment Type.
- ✗
Create a workflow rule that checks if Employee Class is populated for non-interns and routes the record for correction if not.
Why it's wrong here
Workflow rules cannot enforce field requiredness at save; they operate after the record is saved. This would allow incomplete records to be saved and then require manual correction, which is inefficient and error-prone. A business rule provides immediate validation.
- ✓
Use a business rule on the 'Job Information' object that triggers on save and validates that Employee Class is populated unless Employment Type is 'Intern'.
Why this is correct
A business rule can enforce conditional requiredness by checking if Employee Class is empty and Employment Type is not 'Intern'. If the condition is met, the rule raises an error, preventing save. This allows interns to bypass the requirement while enforcing it for others.
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.