Salesforce Certified Administrator Practice Test - Questions Answers, Page 10

The Opportunity Stage Duration report is a standard report that shows how long opportunities spend in each stage before they are closed. It can be used to measure the average stage duration for all closed opportunities by grouping and summarizing the data by stage name and duration fields. Using process builder to capture the daily average on each opportunity is not feasible because it would require creating multiple fields and formulas on the opportunity object and updating them every day. Adding formula fields to track stages on each opportunity is also not practical because it would require creating multiple fields and formulas on the opportunity object and maintaining them every time a stage changes. Refreshing weekly reporting snapshots for closed opportunities is not necessary because the report can run on real-time data without snapshots.

Reference: https://help.salesforce.com/s/articleView?id=sf.reports_opportunity_stage_duration_report.htm&type=5

Validation rules are a way to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. They can be used to require users to follow the status values as they are on the path and prevent them from reverting the case back to a previous status by using formulas that compare the old and new values of the status field. Global value picklists are a way to create and maintain picklist values that can be shared across multiple fields, but they do not enforce any logic or order on the values. Predefined field values are a way to set default values for fields on path settings, but they do not prevent users from changing them later. Dependent picklists are a way to filter the values of one picklist based on the value of another picklist, but they do not prevent users from going back to a previous value.

Reference: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm&type=5

Guided selling, validation rules, and required fields on the page layout are three options that can be used to ensure sales reps fill out key fields when working on an opportunity through the process. Guided selling allows administrators to add prompts and guidance at each stage of the path to help reps move forward with confidence. Validation rules allow administrators to enforce data quality and business logic by preventing reps from saving records that do not meet certain criteria. Required fields on the page layout allow administrators to make certain fields mandatory for reps to enter before saving records. Configuring opportunity path can help reps visualize and update key fields at each stage, but it does not make them required or prevent them from moving forward without entering them. Using flow to mark fields required is not possible because flows cannot modify page layouts or field properties.

Reference: https://help.salesforce.com/s/articleView?id=sf.path_guided_selling.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_properties.htm&type=5

The User Licenses related list in Company Information shows the types of licenses that have been purchased for an org and how many are available or used. It also shows the expiration date of each license type if applicable. This information can help administrators plan for license purchases and manage user access. Searching for license types in setup does not show how many licenses have been purchased or how many are available or used. User Management settings in setup does not show license information either, but rather settings related to user login, session, identity, etc. Usage-based entitlement related list in company information shows information about usage-based licenses such as API requests or sandboxes, but not user licenses.

Reference: https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm&type=5

Auto response rules are a way to automatically send email responses to leads or cases based on certain criteria such as lead source, industry, etc. They can be used to send personalized emails whenever a lead fills out a web-to-lead form on a website and send different messages based on the lead industry field value. Using validation rule to trigger workflow to email the lead is not possible because validation rules cannot trigger workflows or send emails; they only prevent records from being saved if they do not meet certain criteria. Adding a public group and process builder to email the lead is unnecessary because auto response rules can handle this requirement without additional configuration or customization. Creating an assignment rule to email the lead is also unnecessary because assignment rules are used to assign leads or cases to users or queues based on certain criteria, not send emails; although they can have email alerts as part of their actions, they are not as flexible as auto response rules for personalizing email messages.

Reference: https://help.salesforce.com/s/articleView?id=sf.customize_leadsautoresponse.htm&type=5

A user with manager role above the agent can change ownership on multiple cases that are owned by the agent or by users below the agent in the role hierarchy. A user with the System Administrator profile can change ownership on any case, regardless of the owner or role hierarchy.

Reference: https://help.salesforce.com/s/articleView?id=sf.case_change_owner.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_userperms.htm&type=5

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Lead object to display an error message if the Lead Status field is marked as qualified and the Budget field is blank.

Reference: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm&type=5

Page layout and field level security are two factors that determine whether a user can see a new field on a record. To troubleshoot this issue, the administrator should ensure that the page layout for the user's profile has been updated to include the new field and that the field level security of the field for the user profile allows read or edit access.

Reference: https://help.salesforce.com/s/articleView?id=sf.customize_layoutoverview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.htm&type=5

Profile assignment and page layout assignment are two assignments that should be used to display a new record type to users. Profile assignment determines which profiles can access a record type and which record type is the default for each profile. Page layout assignment determines which page layout is assigned to each record type and profile combination.

Reference: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_assign.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_pagelayoutassign.htm&type=5