C_THR81 Employee Central Core Practice Question

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 an OnSave rule on Job Information that evaluates Location and Legal Entity

  Why it's wrong here

  An OnSave rule would only run when the Job Information record is saved. It does not provide immediate update when either field changes. The requirement specifies that the rule must run when either field changes, implying real-time responsiveness. Thus, OnSave is not the best fit.

• ✗

  Create a business rule on the Location object that updates the Works Council on Job Information

  Why it's wrong here

  A business rule on the Location object cannot directly update fields on Job Information because it operates in a different context. Cross-object updates require a rule on the target object or a save rule with association. This approach would not work as described.

• ✗

  Create two separate OnChange rules: one on Location and one on Legal Entity

  Why it's wrong here

  While two separate OnChange rules could work, they would both need to set the Works Council field. This could lead to conflicts or redundant execution. A single OnChange rule with both trigger fields is more efficient and avoids potential race conditions or duplicate logic.

• ✓

  Create an OnChange rule on Job Information with trigger fields Location and Legal Entity

  Why this is correct

  An OnChange rule on Job Information can have multiple trigger fields. When either Location or Legal Entity changes, the rule fires and sets the Works Council field. This provides immediate update and meets the requirement of reacting to changes in both fields.