An analytics user at Cloud Kicks needs Read, Create, and Edit access for objects and should be restricted from deleting any records. What should the administrator do to meet this requirement?

Profiles define the base object and field permissions for users; creating a custom profile and explicitly removing 'Delete' access for each relevant object will ensure the user has the required Read, Create, and Edit permissions while strictly prohibiting deletion.

Permission sets are used to *extend* permissions and grant additional access, but they cannot be used to *remove* or restrict permissions that are already granted by a user's assigned profile.

Assigning the standard System Administrator profile grants 'Modify All Data' and 'Delete' access for all objects, which directly contradicts the requirement to restrict delete permissions.

Giving 'View All' access impacts record visibility, and assigning a role in the role hierarchy primarily affects data access through sharing rules, neither of which controls object-level 'Delete' permissions.