Free Practice Questions for Salesforce Plat-101 Exam

 Selecting Fields to Display is what the associate should do to add the missing key columns to the custom Contact list view. Selecting Fields to Display is a feature that allows the user to choose which fields to show as columns in the list view, and in what order. The user can select up to 15 fields to display, and drag and drop the fields to rearrange the column order. Editing list filters is a feature that allows the user to apply one or more criteria to filter the records that are displayed in the list view. The user can select a field, an operator, and a value for each filter, and combine multiple filters with AND or OR logic. Editing sharing settings is a feature that allows the user to control the access and visibility of records for different users and groups. The user can define the organization-wide default, role hierarchy, sharing rules, and manual sharing for each object.

 Contacts to multiple accounts is a feature that allows a contact to be related to more than one account. This is useful for scenarios where a contact works at multiple companies or has different roles at different accounts. Creating two contact records would result in duplicate data and confusion. Merging the two account records would not solve the problem of relating the contact to two accounts.

 Validation rules are what GCC should use to ensure that opportunities meet the standards for the Annual Revenue field. Validation rules are a type of metadata that define a condition and an error message to display when the condition is not met. Validation rules can be used to enforce data quality and integrity by preventing users from saving records that do not meet the specified criteria. For example, a validation rule could be set up on the Opportunity object to check that the Annual Revenue field is a positive amount and does not exceed $100. Assignment rules are a type of metadata that define how records are assigned to users or queues based on certain criteria. Assignment rules can be used to automate business processes by distributing records to the appropriate owners or teams. For example, an assignment rule could be set up on the Lead object to assign leads to sales reps based on their territory. Default values are a type of metadata that define a value that is automatically populated in a field when a new record is created, unless the user enters a different value. Default values can be used to save time and ensure data consistency by prefilling fields with common or expected values. For example, a default value could be set up on the Lead Source field to indicate the most frequent source of leads, such as Web or Phone.

Excel (.xlsx or .xls) file or comma-separated values (.csv) are the types of files that the report can be exported into. Exporting a report allows the user to save the report data as a file that can be opened and edited in other applications, such as Microsoft Excel or Google Sheets. The user can choose to export the report as a formatted report, which preserves the report formatting and layout, or as a details only report, which includes only the report data without the formatting and layout. A formatted report can be exported as an Excel (.xlsx or .xls) file or a PDF (.pdf) file. A details only report can be exported as a comma-separated values (.csv) file. A Word (.doc or .docx) file is not a type of file that the report can be exported into.

The action that the team members should do to ensure they receive the weekly results of the dashboard by email is to subscribe to the dashboard. Subscriptions let users schedule dashboards to run at regular intervals and send notifications to them or other recipients by email or Chatter. Users can also set conditions for when the notifications are sent, such as when the dashboard returns no results or the results change.

Changing the default value of the Lead Source field from ‘Web’ to ‘Trade Show’ is the best way to help the sales reps when they create these lead records, as it will automatically populate the field with the correct value, and save them time and effort.

 Salesforce Help is where the associate should go to understand the differences between the data types. Salesforce Help is a resource that provides documentation, guides, videos, and support for Salesforce users who need assistance with using or troubleshooting Salesforce products and features. Salesforce Help has a section called Data Types that explains the characteristics and use cases of each data type, such as text, number, date, picklist, checkbox, and so on. Customer Support is a service that provides technical support and assistance for Salesforce users who encounter issues or errors with Salesforce products and features. Customer Support is not a resource that explains the differences between the data types, but rather a resource that helps resolve problems or incidents. App Launcher is a feature that allows the user to access all the apps and objects in Salesforce, such as Sales, Service, Marketing, and so on. App Launcher is not a resource that explains the differences between the data types, but rather a feature that helps navigate the user interface.

 The type of org that the associate should create from within Trailhead to quickly learn, practice, and develop Salesforce skills is a Playground. A Playground is a free, fully functional Salesforce org that you can use to test and explore the platform. You can create multiple Playgrounds from Trailhead and use them to complete hands-on challenges and projects1. A Developer Edition is a type of org that you can create from the Salesforce website, not from Trailhead. A Sandbox is a type of org that you can create from a production org as a copy of it for testing and development purposes

Selecting the personalization button (pencil icon), then clicking and dragging the item name up or down to adjust its location is the correct way to customize the items on the navigation bar, as shown in the screenshot.

The user can clone the list view with a new name, and filter by the specific city to see only contacts from that city on the list view. This will not affect what other users see on the original list view.