Platform Foundations Plat-101 Passing Score

 Permission sets are used to grant additional access to users based on their functional or departmental needs. A permission set can be assigned to multiple users, regardless of their profile. A permission set can include field-level security settings that allow edit access to specific fields on an object. Queues are used to group records and assign them to a team of users who can work on them. Public groups are used to group users, roles, or other groups for the purpose of sharing records or sending email.

The opportunities Kanban view is a visual summary of opportunities in a list view, where the associate can summarize, filter, and move opportunities along the pipeline by dragging and dropping them.

 A gauge is a dashboard component type that shows a single value within a range of custom values. A gauge is useful for showing whether a metric, such as revenue or customer satisfaction, is within a desired range. For example, a gauge could show the current revenue as a needle pointing to a green, yellow, or red zone, indicating whether the revenue is above, below, or on target. A metric is a dashboard component type that shows a single value, such as the total number of accounts or the average deal size. A metric does not show a range of values. A chart is a dashboard component type that shows data in a graphical format, such as a pie chart, a bar chart, or a line chart. A chart is useful for showing the distribution or trend of data, but not a single value within a range.

Creating record types on Account called Partner and Customer is the recommended way to display only the information applicable to each group. Record types allow different page layouts, picklist values, and business processes to be assigned to different users based on their profile. For example, the Partner record type could have a page layout that includes fields specific to partners, such as Partner Type, Partner Level, and Partner Status. The Customer record type could have a different page layout that excludes those fields. Using Account for customers and creating a custom object for partners would not be advisable, because it would create data silos and make reporting and sharing more difficult. Creating custom objects called Partner and Customer would not make sense, because they are both types of accounts and should use the standard Account object.