Free Practice Questions for Salesforce ADM-201 Exam

A PriceBook is a feature that allows administrators to define different prices for the same products based on different criteria such as customer segment, region, channel, etc. For example, a PriceBook can provide reseller partners with discounted prices on the products they purchase compared to regular customers. A PriceBook consists of one or more PriceBook entries that specify the product ID, pricebook ID, list price, currency, and active status for each product-pricebook combination. References: https://help.salesforce.com/s/articleView?id=sf.pricebook_overview.htm &type=5

A dependent picklist and a custom picklist are the two features that can be used to fulfill the requirement. A global picklist and a multi-select picklist are not features that can be used to fulfill the requirement.

Here is a more detailed explanation of why A and B are the correct answers:

A. Dependent Picklist

A dependent picklist is a picklist whose values are dependent on the value selected in another picklist. This is useful for ensuring that only valid values are selected for a field. In this case, the administrator can create a dependent picklist for the category field on accounts and cases, with the values for the picklist being dependent on the record type selected. This will ensure that only the relevant picklist values are available for selection based on the record type selected.

For example, the administrator could create a dependent picklist for the category field on accounts and cases with the following values:

Record Type: New Account

Picklist Values: Residential, Commercial

Record Type: Existing Account

Picklist Values: Renewal, Upsell, Cross-sell

This would ensure that only the relevant picklist values are available for selection when creating a new account or an existing account.

B. Custom Picklist

A custom picklist is a picklist that is created by the administrator. This is useful for creating picklists with values that are specific to the organization's needs. In this case, the administrator can create a custom picklist for the category field on accounts and cases, with the values for the picklist being specific to the organization's needs. This will ensure that the picklist values are relevant to the organization and its customers.

For example, the administrator could create a custom picklist for the category field on accounts and cases with the following values:

Picklist Values: Residential, Commercial, Land, Multi-Family

This would ensure that the picklist values are relevant to the organization and its customers.

To identify new leads entered by interns from existing leads, the administrator should define a record type and assign it to the interns. This will allow them to select a different record type when creating leads, and distinguish them from other leads based on record type. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

To save time and budget, you can check the AppExchange for prebuilt solutions that can be easily customized for your needs. AppExchange is a marketplace for apps, components, and consulting services that extend Salesforce functionality.

A roll-up summary field is a type of field that calculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

The $Record global variable allows you to reference the values of the active record the flow is running on.

Flow Builder supports creating a wizard that can collect user input and perform actions.

Dashboards show data from source reports as visual components that provide a snapshot of key metrics and performance indicators. Dashboards need to be refreshed manually or scheduled to run on a regular basis to reflect the most recent data from the reports. The running user of a dashboard determines whose security settings are applied when the dashboard is run. If the running user is different from the viewer of the dashboard, they may see different data based on their permissions and sharing settings. References: https://trailhead.salesforce.com/en/content/learn/modules/lex_implementation_dashboards_and_reports/dashboards

To test the impact of a critical update before it is auto-activated, you should activate it in a sandbox first. This way, you can verify that your customizations and integrations work as expected without affecting your production org.

There are two possible reasons why users are unable to access a report based on a custom report type created by an administrator. One is that the custom report type is in development mode, which means that it is not deployed and available for use by other users except for administrators and users with manage custom report types permission. The other is that the report is saved in a private folder, which means that it is visible only to its owner and not shared with other users or groups. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_custom_report_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_folders.htm &type=5