An app builder at Cloud Kicks created a custom object and related fields in the schema builder. Which next steps should the app builder take to ensure users can access the new object and fields?
Correct Answer:
A, C
The correct next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields.
This is a two-part access problem in Salesforce: users need both security access and user-interface exposure. Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.
C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.
A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.
B is incorrect because ''Allow Reports'' only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.
