A company has a custom object 'Audit__c' that is referenced by a custom button on the Account page. The admin wants to delete the object. What is the most important consideration?

The object can be deleted only if the admin has the 'Modify All Data' permission.

The object can be deleted, and the button will continue to work.

The admin must first remove the custom button or its reference to the object.

The custom button will be automatically removed when the object is deleted.

An administrator is asked to delete a custom object that is no longer in use. What is a direct consequence of deleting a custom object?

The object is deactivated but its data remains accessible via API.

Only the object's metadata is removed, but records are archived.

The object is moved to the Recycle Bin and can be restored within 15 days.

All records and data associated with the object are permanently deleted.

An administrator wants to rearrange the order of fields on a record's detail page. Where should they go to make this change?

Object Manager > Validation Rules

Object Manager > Buttons, Links, and Actions

Object Manager > Fields & Relationships

A company has a custom field 'Legacy_Code__c' on the Account object that is referenced in a Flow. The admin wants to delete the field. What is the likely outcome?

The Flow will be automatically updated to remove the reference.

The field can be deleted, and the Flow will continue to work with null values.

The Flow will be deleted automatically when the field is deleted.

The admin must first remove the field from the Flow, then delete the field.

A company has multiple record types for the Opportunity object. The sales team wants different fields visible for each record type. The admin has created custom fields and wants to ensure each record type shows the appropriate fields. What is the best approach?

Use a single page layout and rely on the record type picklist to show fields.

Create a validation rule to conditionally display fields.

Create a separate page layout for each record type and assign them accordingly.

Use field-level security to hide fields based on record type.

SalesforceCertified Administrator

Domain 4Objective 2

Explain How to Create, Delete, and Customize Fields and Page Layouts on Standard and Custom Objects, and Understand the Implications of Deleting Fields. PLATFORM-ADMINISTRATOR Practice Questions (Page 3)

Part of the STANDARD AND CUSTOM OBJECTS domain, which accounts for 15% of the PLATFORM-ADMINISTRATOR exam.

22questions here

5free pages

6concepts

15%of the exam

Questions 11–15

11expert · hard
A company has a custom object 'Audit__c' that is referenced by a custom button on the Account page. The admin wants to delete the object. What is the most important consideration?
Select an answer first
12foundation · easy
An administrator is asked to delete a custom object that is no longer in use. What is a direct consequence of deleting a custom object?
Select an answer first
13foundation · easy
An administrator wants to rearrange the order of fields on a record's detail page. Where should they go to make this change?
Select an answer first
14application · medium
A company has a custom field 'Legacy_Code__c' on the Account object that is referenced in a Flow. The admin wants to delete the field. What is the likely outcome?
Select an answer first
15expert · hard
A company has multiple record types for the Opportunity object. The sales team wants different fields visible for each record type. The admin has created custom fields and wants to ensure each record type shows the appropriate fields. What is the best approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PLATFORM-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Salesforce. “PLATFORM-ADMINISTRATOR” is a trademark of its owner, used for identification only.