Salesforce Sharing and Visibility Certification Practice Exam

How can the Architect prevent users in the Custom Sales Department Profile from deleting Opportunities?

1. Remove the Delete button from the Opportunity Page Layout.

2. Create a Validation Rule that checks the User's Profile before allowing the deletion.

3. Override the Standard button with a Visualforce Page warning of deletion restrictions.

4. Remove the "Opportunity Delete" Permission from the User Profile.

The correct answer is: Remove the "Opportunity Delete" Permission from the User Profile.

The correct approach to prevent users in the Custom Sales Department Profile from deleting Opportunities is to remove the "Opportunity Delete" permission from the User Profile. This method directly addresses the issue by modifying the profile settings, which govern what users can do with specific records. By taking away this permission, users associated with that profile will not have the ability to delete Opportunities, regardless of their access to the page layout or any other features. This technique is preferred because permissions at the profile level establish the foundational access control for users. It is a straightforward and effective way to manage record-level access rather than relying on indirect methods that may still allow the action to occur. The other methods involve either modifying the user interface or creating custom logic that may not be as reliable or straightforward. For example, simply removing the Delete button from the Opportunity Page Layout does not prevent users from deleting records through other interfaces or APIs. A validation rule could theoretically prevent deletions based on profile checking, but it is not an absolute safeguard since it relies on execution context and can be bypassed in certain scenarios. Overriding the standard button with a Visualforce page is also a more complex solution that adds extra steps and could lead to confusion for users if not implemented cohesively. Therefore, managing permissions