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 a composite unique key on the combination of 'EmployeeID' and 'ProjectName'.

  Why this is correct

  A composite unique key ensures that the combination of EmployeeID and ProjectName values is unique across all records of the object. This directly prevents duplicate assignments of the same employee to the same project. In MDF, you can configure a unique key by selecting multiple fields as part of a single unique constraint. This is the correct approach to enforce the business rule at the data level, ensuring data integrity without relying on user vigilance or complex validation rules.

• ✗

  Use a 'Picklist' for ProjectName and restrict values to a predefined list.

  Why it's wrong here

  Using a picklist for ProjectName restricts the values to a predefined list, which can help standardize data entry, but it does not enforce uniqueness of the employee-project combination. An employee could still be assigned to the same project multiple times if the picklist value is selected repeatedly. Picklists are for value validation, not for preventing duplicate records. This approach fails to address the core requirement of preventing duplicate assignments.

• ✗

  Set the 'ProjectName' field as a required field and enable 'Unique' on it.

  Why it's wrong here

  Setting the ProjectName field as unique would prevent any two records from having the same project name, regardless of the employee. This would incorrectly disallow multiple employees from being assigned to the same project. The requirement is to prevent the same employee from being assigned to the same project multiple times, not to prevent multiple employees from sharing a project. Therefore, a unique constraint on ProjectName alone is too restrictive and does not meet the requirement.

• ✗

  Create a business rule that checks for existing records before saving a new assignment.

  Why it's wrong here

  A business rule can validate data and prevent saving if a duplicate is found, but it requires custom logic to query existing records, which can be complex and may impact performance. Business rules are not the most efficient or reliable method for enforcing uniqueness, as they depend on proper configuration and may not trigger in all scenarios (e.g., data imports). A unique key constraint is a more robust, declarative solution that is enforced by the system automatically.