Permission Sets and Profiles in Salesforce control a user's ability to Create, Read, Update, and Delete object records by defining permissions and access levels for different objects.
Why the other options are incorrect:
C. Public Group: This is used for sharing purposes and to simplify the sharing of records but does not directly control CRUD (Create, Read, Update, Delete) permissions on objects.
D. Roles: This is used to control the level of visibility users have to data across the organization, typically for reporting and record-level access, but it does not directly define CRUD permissions on objects.
Example:
Profiles: A user with a "Sales Profile" might have Create, Read, and Update permissions on the Account object but not Delete permissions.
Permission Sets: If a user needs additional permissions beyond what their profile provides, such as the ability to delete records, a Permission Set can be assigned to grant that specific permission without changing the profile.