CRT-101 practice question 4 of 30

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?

Full set: 248 questions
Answer options
A: Assign the standard System Administrator profile to the analytical user.
B: Give the user View all access and assign them to the highest role in the role hierarchy.
C: Create and assign a custom profile with Delete access removed for each object. Correct answer
D: Create and assign a permission set that includes Read, Create, and Edit access
Correct Answer:
C. Create and assign a custom profile with Delete access removed for each object.
Explanation

The most direct and appropriate method to meet this requirement is by using a custom profile. Profiles are the primary mechanism for defining a user's baseline object-level permissions (Create, Read, Edit, Delete). By creating a custom profile, an administrator can explicitly grant Read, Create, and Edit permissions for the necessary objects while ensuring the Delete permission is disabled. This enforces the principle of least privilege by providing the user with exactly the access they need to perform their job, without granting excessive permissions like deletion rights.

Why Incorrect

A. Assign the standard System Administrator profile to the analytical user. This profile grants "Modify All Data," which includes delete permissions for all objects, directly violating the core requirement.
B. Give the user View all access and assign them to the highest role in the role hierarchy. The role hierarchy and "View All" access control record-level visibility, not the object-level permissions (like Create, Edit, or Delete) required by the user.
D. Create and assign a permission set that includes Read, Create, and Edit access. Permission sets only grant additional access; they cannot restrict permissions granted by the user's base profile. If the profile allows deletion, the permission set cannot remove it.

References

1. Salesforce Help - Profiles: "Profiles define how users access objects and data, and what they can do within the application. When you create a user, you assign a profile to them... A profile contains user permissions, object permissions, field permissions..."

Source: Salesforce Help Documentation, "What Are Profiles?"

2. Salesforce Help - Object Permissions: "Object permissions specify the base-level access users have to create, read, edit, and delete records for each object... You can manage object permissions in profiles and permission sets."

Source: Salesforce Help Documentation, "Object Permissions." This page details how profiles are the foundation for setting these specific CRUD permissions.

3. Salesforce Help - Permission Sets: "A permission set is a collection of settings and permissions that gives users access to various tools and functions... Use permission sets to grant additional permissions and access settings to users."

Source: Salesforce Help Documentation, "Permission Sets." This confirms that permission sets are for adding permissions, not for establishing a restrictive baseline.

Scroll to Top