Plat-Admn-301 Exam Dumps - Salesforce Administrator Questions and Answers

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

Tableau CRM is a product that allows you to create complex dashboards with supporting charts based on data from a variety of sources, including Salesforce data and external data sources. Tableau CRM uses an analytics platform that stores data in datasets and lets you explore and visualize data using lenses and dashboards. You can also use artificial intelligence and machine learning features to discover insights and make predictions from your data. Tableau CRM is integrated with Salesforce and can be accessed from various apps and objects. References: https://help.salesforce.com/s/articleView?id=sf.bi_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.bi_data_overview.htm &type=5

Two considerations that the administrator should remember about roll-up summary fields are:

Roll-up types include COUNT, SUM, and AVG. A roll-up type is a function that determines how the data from the child records is aggregated and displayed on the parent record. The available roll-up types are COUNT, which counts the number of child records; SUM, which adds up the values of a numeric field on the child records; AVG, which calculates the average value of a numeric field on the child records; MIN, which displays the lowest value of a field on the child records; and MAX, which displays the highest value of a field on the child records.

Roll-up summary fields are created on the master side of a master-detail relationship. A master-detail relationship is a type of relationship that links two objects together such that the master object controls certain behaviors of the detail object, such as security and deletion. A roll-up summary field is a type of field that displays a value that is calculated from child records related to a parent record. Roll-up summary fields can only be created on the master object of a master-detail relationship or on a lookup relationship if it is set as required.

The other two options are incorrect because:

Roll-up summary fields do not prevent the conversion of a master-detail relationship to a lookup. They only prevent it if they reference a formula field that includes another relationship.

Rollup fields are not calculated prior to save. They are calculated after save and may take some time to update.

A lightning action is a type of quick action that can invoke a Lightning component, a Visualforce page, or a URL. The administrator can use a lightning action to redirect the user to a different page after they finish the screen flow. This way, the user will not see the initial screen again and will not misuse the flow tool.

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.

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. References: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm &type=5

The resume event is recalculated and the email goes out to the account owner immediately because the flow uses a scheduled path that evaluates the expiration date field every time it changes. When the expiration date is changed to yesterday, the flow resumes immediately and executes the action of sending the email

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. One of the changes that the Setup Audit Trail tracks is when a user grants login access to another user. This means that you can use the Setup Audit Trail to see if any other administrators or delegated administrators are using the Log In As a User feature. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.remoteaccess_granting_login_access.htm &type=5

A lookup relationship is a type of field that links one object to another object. It allows you to access related data from another object and display it on a record page. A lookup relationship can be used to link the custom object that stores financial information to the Account object, so that only finance team members can see the related financial information about the account. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5