Salesforce Certified Data Architecture Practice Test

How can UC ensure only the owner of a contact can delete that contact record?

1. Create a "before delete" trigger to check ownership.

2. Set Sharing settings as Public Read Only for the Contact object.

3. Remove delete permissions from the contact profile.

4. Create a validation rule based on ownership.

The correct answer is: Create a "before delete" trigger to check ownership.

Creating a "before delete" trigger to check ownership is an effective way for UC to ensure that only the owner of a contact can delete that contact record. This type of trigger allows for custom logic to be executed before the deletion process occurs. By implementing this trigger, you can programmatically enforce that the delete action is only permitted if the current user matches the owner of the contact record. This control mechanism provides a robust solution, as it directly addresses the delete event and checks the ownership explicitly. If the user attempting to delete the record is not the owner, the trigger can throw an error, thus preventing the deletion. Other options focus on different aspects of permissions and record access but do not provide the same level of specificity. For example, setting sharing settings as Public Read Only would allow everyone to view the records but wouldn't prevent users from attempting to delete records if they had the permission. Removing delete permissions from the contact profile would disable the ability to delete for all users within that profile, not just for non-owners. Lastly, a validation rule is used to validate data input rather than controlling record deletion and would not be executed during the delete operation.