Salesforce App Builder Practice Exam

The selection of Profiles as the method that does not control record-level access is accurate because Profiles primarily define the permissions and access settings for users, including what they can do with records, but are not specifically designed for record-level access control.

Profiles control object permissions, field-level security, and various user settings, allowing administrators to specify what actions users can perform across records of an object. However, record-level access—determining which records a user can view or edit—is managed instead through mechanisms like Organization-Wide Defaults, Role Hierarchy, and Sharing Rules.

Organization-Wide Defaults set the baseline level of access for all records in an object, Role Hierarchy determines access based on the user's position within the organization structure, and Sharing Rules further specify access for groups of users based on criteria. Therefore, while Profiles are essential for defining user capabilities, they do not directly control which specific records users can access or manipulate, putting them outside the realm of record-level access methods.