Advanced-Administrator Exam Dumps : Salesforce Certified Platform Administrators II (Plat-Admn-301)

While the Schema Builder is a powerful tool in Salesforce for visually creating and managing custom objects and fields, there are certain configurations that must be done in Object Manager rather than Schema Builder. One of these configurations is enabling field history tracking.

Field History Tracking:

Field history tracking cannot be configured directly within Schema Builder. This setting must be enabled from within the Object Manager, where administrators can specify which fields on an object should have their changes tracked.

Enabling field history tracking involves navigating to the object in Object Manager, accessing the field history tracking settings, and selecting specific fields to track.

Limitations of Schema Builder:

Schema Builder is useful for quickly creating custom objects, relationships, and fields, but it does not support all configurations, such as enabling field history tracking, defining object-level permissions, or setting advanced object configurations.

For these types of configurations, administrators need to return to Object Manager where these settings are available.

Incorrect options:

Add custom fields to the page layout: This task is typically done within Object Manager, but Schema Builder does allow customization of page layouts to a certain extent through drag-and-drop.

Make available for Customer Portal: Schema Builder does not control portal availability; however, this is managed through Object Manager settings related to record visibility for portal users.

Allow Reports and Activities: This setting can be configured in Schema Builder when initially creating an object, but further refinements and permission settings must often be done in Object Manager.

In conclusion, enabling field history tracking requires access to the Object Manager, as it cannot be configured through Schema Builder.

An after save flow is a type of flow that runs in the background after a record is saved and performs actions based on the record data or changes. An after save flow does not require user input or interaction and can be triggered by a record-triggered flow element or by an Apex trigger. In this case, you can create an after save flow that runs when a case record is updated and delivers status update email to customers based on certain criteria or conditions. References: &type=5 &type=5

A delegated administrator is a user who has been granted limited administrative privileges by an administrator through delegated administration groups. Delegated administrators can perform some administrative tasks without having full access to Setup.

Some functions that delegated administrators can perform are:

B) Build automation and validation rules using screen flows

Screen flows are types of flows that guide users through screens with elements such as text boxes, picklists, radio buttons, etc. Screen flows can also perform actions such as creating records, updating fields, sending emails, etc. Delegated administrators can build automation and validation rules using screen flows if they have been granted access to create and edit flows by an administrator. References: &type=5 &type=5

D) Make updates to permission set configurations

Permission sets are collections of settings and permissions that can extend users’ functional access without changing their profiles. Delegated administrators can make updates to permission set configurations if they have been granted access to manage users by an administrator. References: &type=5 &type=5