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 onChange rule on the Event Reason field that sends a notification whenever the field changes.

  Why it's wrong here

  An onChange rule on Event Reason would fire whenever the field changes, regardless of the new value. It would not limit the notification to promotions only unless a condition is added. However, the scenario requires triggering on Job Information update, not just on the field change, so this rule type is not the best fit.

• ✗

  Create an onInit rule on the Job Information portlet that checks the Event Reason and sends a notification when the portlet loads.

  Why it's wrong here

  onInit rules run when the portlet is initialized, which is typically when the page loads, not when the record is saved. They are used for defaulting values and cannot reliably detect an update. Therefore, this rule type does not meet the requirement of triggering on update.

• ✓

  Create an onSave rule on the Job Information object with a condition that checks if Event Reason equals 'Promotion' and then triggers a notification.

  Why this is correct

  An onSave rule on Job Information executes when the record is saved. By adding a condition that evaluates the Event Reason field, the rule only proceeds when the event reason is Promotion. This satisfies the requirement to trigger only for promotions and to send the notification.

• ✗

  Create a scheduled job that runs daily to check for Job Information records with Event Reason 'Promotion' and sends notifications.

  Why it's wrong here

  A scheduled job introduces a delay and does not trigger immediately upon update. It also may send duplicate notifications if not carefully designed. The requirement is for a rule that triggers when Job Information is updated, so a real-time onSave rule is appropriate, not a batch job.