Bucket column allows you to categorize report data into groups without creating a formula or custom field. You can create buckets for different ranges of values and assign labels to them.

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

Currency locale and default language are two of the company settings that an administrator can configure in Salesforce. Currency locale determines how currency amounts are formatted and displayed in reports and other places. Default language determines the language used for labels, buttons, tabs, and other elements in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm &type=5

Data Export Wizard allows administrators to export data from Salesforce in CSV files. It can be used to export data for backup purposes or to analyze data in external tools. Data Import Wizard is used to import data into Salesforce, not export. Data Loader is a desktop tool that can also export data, but it is more complex and requires installation. Report Builder is used to create reports in Salesforce, not export data. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm &type=5

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

An external ID is a custom field that has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using Salesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating records from an external system because it is generated by Salesforce and may not match with the external system’s IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier when importing and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records from an external system because it may not be available or consistent across systems. References: https://help.salesforce.com/s/articleView?id=sf.custom_field_attributes.htm &type=5

To display the screen flow, the administrator should create a tab and add the screen flow to the page. The administrator can also use a flow element and add the screen flow to the record page.

The other options are not relevant to this scenario. Adding the flow in the utility bar of the console will not display the screen flow. Installing an app from the AppExchange is not necessary to display the screen flow.

Here are the steps on how to create a tab and add the screen flow to the page:

• Go to Setup > Tabs.
• Click New.
• Enter a name and label for the tab.
• Select the Screen Flow tab type.
• Select the screen flow that you want to display.
• Click Save.

Here are the steps on how to use a flow element and add the screen flow to the record page:

• Go to Setup > Customize > Lightning App Builder.
• Select the record page that you want to add the screen flow to.
• Click Edit.
• Drag the Flow element from the Palette to the canvas.
• Select the screen flow that you want to display.
• Click Save.

A pending Chatter post is a post that has been scheduled to be published at a future date and time. However, if the user who created the pending Chatter post is deactivated before the scheduled date and time, then the pending Chatter post will be canceled and will not be published. This is because deactivated users cannot create or edit posts in Chatter. References: https://help.salesforce.com/s/articleView?id=sf.collab_scheduled_posts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.collab_deactivated_users.htm &type=5

Freezing a user is a way to temporarily prevent them from logging in to Salesforce without deactivating their user record. This is useful when you need to perform some cleanup tasks before deactivating a user, such as removing them from being referenced in a hierarchy field like Direct Manager. References: https://help.salesforce.com/s/articleView?id=sf.users_freeze.htm &type=5

Two data loss considerations when changing a custom field type from Text to Picklist are:

• Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.
• Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. References: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_considerations.htm&type=5

To make a quick action available on the Salesforce mobile app, you need to add it to the Salesforce Mobile and Lightning Experience Actions section of the page layout. You can use the Page Layout Editor to drag and drop the quick action onto the section.

References: https://help.salesforce.com/s/articleView?id=sf.actions_in_lex.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_page_layouts.htm &type=5

Flow Builder allows you to create an automated business process that can update records based on certain criteria. You can use a scheduled flow to run once a week and count the number of open cases related to an account.

References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_scheduled_start.htm &type=5

My Domain is a feature that allows administrators to create a custom domain name for their Salesforce org that replaces their instance URL (such as na35.salesforce.com). My Domain provides benefits such as improved security; enhanced branding; faster navigation; access to Lightning components; etc. However, one of the considerations when enabling My Domain is that it changes how users log in to Salesforce - instead of using their instance URL login (such as login.salesforce.com), they have to use their My Domain login (such as mydomain.my.salesforce.com). This applies to all internal and external users who access Salesforce via web browser or mobile app. References: https://help.salesforce.com/s/articleView?id=sf.domain_name_overview.htm &type=5

Making a field universally required is a way to ensure that the field needs to be filled on every record; it prevents users from saving a record without entering a value in that field. It can be used to ensure that the billing system field needs to be filled on every invoice record by making it universally required in the field settings. Creating a process builder to set the field, defining an approval process for the child, or requiring the field on the record type are not ways to ensure that the field needs to be filled on every record; they either do not enforce data entry or only apply to certain scenarios or users. References: https://help.salesforce.com/s/articleView?id=sf.customize_fields.htm &type=5

To free up user licenses for new users, the administrator should deactivate the former employees user record. This will prevent them from logging in and using Salesforce resources, but preserve their historical activities and data. Deleting or freezing user records will not release user licenses. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_licensing.htm &type=5

A sales process is a set of stages that an opportunity goes through as it moves from creation to close. It can be customized by administrators to match different business models or product lines within an org. Creating a new sales process can help Dreamhouse Realty define a different set of stages for its new home concierge offering that is unlike anything the company has offered in the past and follows a different business model. Creating a quick action, a new approval process, or a new opportunity product are not solutions for creating a customized sales process; they are used for different purposes such as creating records, approving records, or adding products to opportunities. References: https://help.salesforce.com/s/articleView?id=sf.customize_salesprocess.htm &type=5

One possible reason why a manager receives an error when trying to approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields that are updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process are visible does not solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

To acknowledge cases with a Case Reason of Installation immediately via email and assign them to appropriate agents, and escalate cases that are still in New status after 4 hours to support management, an administrator should use Auto-response rules, Queues, and Escalation Rules for case management. Auto-response rules allow sending automatic email responses to customers based on case criteria. Queues allow grouping cases that share common characteristics and assigning them to a group of users who can access and work on them. Escalation rules allow escalating cases that meet certain criteria to higher-level users or groups and sending email notifications. Macros and Entitlements are not case management tools that can be used for this requirement. References: https://help.salesforce.com/s/articleView?id=sf.case_autoresponse.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_escalation.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. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

The Knowledge Lightning component is a component that allows users to access articles from the Service Cloud Console app. However, if users want to access articles from a different app that does not use the console, they can use the Knowledge related list instead. The Knowledge related list shows articles related to a record based on data categories and shows article details such as title, summary, rating, and view count. To add the Knowledge related list to a record page, an administrator can use the page layout editor and drag and drop the Knowledge related list to the appropriate section on the page layout. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_lightning_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.htm &type=5

Opportunity contact roles allow you to track ROI for contacts that are key stakeholders for opportunities. You need to customize the contact role field and add the related list to the opportunity page layout.

References: https://help.salesforce.com/s/articleView?id=sf.opportunity_contact_roles.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_opportunity_contact_role.htm &type=5

Picklist values, help text, and decimal places are three aspects of standard fields that an administrator can customize to suit their business needs. Picklist values are the options that users can choose from a picklist field; they can be added, edited, or deleted by administrators. Help text is the text that appears when users hover over a field; it can be customized by administrators to provide additional information or guidance for users. Decimal places are the number of digits that appear after the decimal point in a number or currency field; they can be changed by administrators to adjust the precision of the field values. Field history tracking and field name are not aspects of standard fields that can be customized; they are only available for custom fields. References: https://help.salesforce.com/s/articleView?id=sf.customize_picklists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_edit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_number.htm &type=5

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can require users to select a product type or check a needs review box when saving an opportunity by using an OR function that evaluates both fields. If neither field is populated, then the validation rule will prevent users from saving records with an error message. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

Auto-response rules are used to automatically send email responses to lead or case submissions based on the criteria you define. You can create one auto-response rule per object (lead or case) and configure multiple rule entries with different criteria and actions within that rule. To meet the requirement of sending different email notifications based on case priority, you need to create one auto-response rule for cases and configure three rule entries with filters for low-priority, medium-priority, and high-priority cases respectively. Then you need to select the appropriate email template for each rule entry action. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadsautor.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesautor.htm &type=5

To make sure that all of the Salesforce users log in using the branded login URL after deploying my domain, and give them a grace period for updating their bookmarks, the administrator should set the Redirect policy to Redirect with a warning to the same page within the domain. This will redirect users who try to log in from https://login.salesforce.com or another domain to https://nto.my.salesforce.com, and show them a warning message that they need to update their bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not redirect users or give them a warning. Filtering with Form Factor will not affect login URL. References: https://help.salesforce.com/s/articleView?id=sf.domain_mgmt_redirect.htm &type=5

To make a tab hidden in the All App Launcher or visible in any app, but still allow a user to view records that would normally be found under this tab, the administrator should use Tab Settings on a profile. Tab Settings control the visibility and default behavior of tabs for each app in an org. The administrator can set a tab to Hidden, which means it will not appear in any app or in the All App Launcher, but users can still access records via other means such as search or reports. Object Permissions, App Permissions, and Org-Wide Defaults are not related to tab visibility. References: https://help.salesforce.com/s/articleView?id=sf.customize_tabs.htm &type=5

The dashboard’s running user determines the data that is displayed on the dashboard. If the running user has access to more data than the intended viewers, the dashboard will show more data than expected. To prevent this, the admin can set the running user to a specific user or a logged-in user, depending on the use case1. Alternatively, the admin can use dynamic dashboards to show data based on each viewer’s access level2.

Fault connector and screen component are two features that can be used to address the issue of users seeing error messages when they use one of their screen flows. Fault connector can be used to handle errors that occur when a flow element fails, such as a record create or update element. Screen component can be used to display a message to the user with text explaining what went wrong and how to correct it. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_display_text.htm &type=5

To allow a user to add new Campaign Members or update Member statuses, the administrator should make sure that Marketing User Checkbox is checked on the user record page. This checkbox enables users to create, edit, and delete campaigns, configure advanced campaign setup, import leads, manage campaign members, and update campaign history via mass update. The checkbox also requires users to have Read and Edit permissions on campaigns and leads/contacts. Creating a permission set, providing access to both Leads and Contacts, or running a Campaign report will not enable users to manage Campaign Members. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_enable.htm &type=5

A Trailhead Playground is a free, online learning environment that allows you to try out Salesforce features and apps. You can use a Trailhead Playground to test out an app from the AppExchange before you install it in your production org.

A sandbox is a copy of your production org that you can use to test changes and new features. You can install an app from the AppExchange in a sandbox to see how it works in your environment.

Testing an app in a production org is not recommended, as it could affect your live data. Checking edition compatibility is important, but it is not a way to try out an app.

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or position within the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to 3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharing settings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References: https://help.salesforce.com/s/articleView?id=sf.contacts_hierarchy.htm &type=5

Process builder can be used to create a record-triggered flow that executes when an opportunity is closed as won and creates a follow-up task for the owner. Field update can be used to update a date field on the opportunity that can be referenced by a time-dependent workflow rule to create another task after 60 days. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_time_action_considerations.htm &type=5

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

Flow Builder supports creating a scheduled flow that can run at specified intervals and perform actions on a set of records that meet certain criteria.

References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_scheduled_start.htm &type=5

Mass delete records and data loader are two tools that can be used by Ursa Major Solar administrator undo import records into object mistake. Mass delete records tool allows administrators delete large numbers records meet certain criteria once setup interface; it can used undo import records into object mistake selecting records imported mistake deleting them mass delete records tool setup interface Data loader tool allows administrators import export delete large numbers records using CSV files command line interface API calls; it can used undo import records into object mistake using CSV file contains IDs records imported mistake deleting them data loader tool command line interface API calls Weekly data export data import wizard are not tools undo import records into object mistake because they either export import records but not delete them. References: https://help.salesforce.com/s/articleView?id=sf.admin_massdelete.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5

Web-to-Case and Email-to-Case are two solutions that allow customers to create cases from a web form or an email. Web-to-Case generates HTML code for a web form that you can place on your website. Email-to-Case converts incoming emails into cases.

References: https://help.salesforce.com/s/articleView?id=sf.customizesupport_web_to_case.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customizesupport_email_to_case.htm &type=5

Component visibility filters are a way to make the record pages more dynamic and easier to use by showing or hiding components based on certain criteria. For example, users can see different components based on their profile, role, record type, or field values. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_component_visibility.htm &type=5

When users log in to Salesforce via the user interface, the system checks for authentication based on their profile settings and permissions. One of the settings is login hours, which specify the time range when users can log in to Salesforce based on their profile. Another setting is Two-Factor Authentication for User Interface Logins permission, which requires users to enter a verification code along with their username and password when they log in to Salesforce via the user interface. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_loginhours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_2fa_perm_ui_logins.htm &type=5

To make it easy for approvers to respond to approval requests, the administrator should configure three settings:

• Update the organization’s chatter setting to allow approvals, which enables approvers to approve or reject requests from chatter feeds or email notifications
• Enable the organization’s Email approval response setting, which allows approvers to reply to approval request emails with keywords such as APPROVE or REJECT
• Add the Items to approve component to the approvers home page, which shows a list of pending approval requests that can be acted upon with one click Specifying initial submission actions within the approval process will not affect how approvers respond to requests. Creating a flow to automatically approve all records will bypass the approval process altogether. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_email.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_one_click.htm&type=5

Record types are a way to assign different page layouts and picklist values to different users based on their business needs. To use two different page layouts for customer and partner accounts, create one record type for each account type and assign them to the appropriate page layouts and profiles. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Campaign influence is a feature that allows users to track how campaigns have influenced opportunities and measure the return on investment (ROI) of marketing efforts. Users can see which campaigns have influenced an opportunity on the related list and assign different attribution models to calculate the campaign influence. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_influence.htm &type=5

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

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

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

Process Builder is a tool that can be used to automate business processes by creating record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can be used to create a flow that executes when an opportunity is closed won and creates a client welcome task and a welcome email for the primary contact. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5

A Chatter private group is a type of Chatter group that allows members to share feedback and ideas with each other in a secure and exclusive space; only members can see and post in a private group. It can be used by Ursa Major Solar to create a space for product owners to collaborate with just the product team by creating a Chatter private group and adding product owners as members. Using quick actions to log communication, configuring a Chatter public group, or adding activity history to document tasks are not solutions for creating a space for product owners to collaborate with just the product team; they either do not provide privacy or do not support collaboration. References: https://help.salesforce.com/s/articleView?id=sf.collab_groups_overview.htm &type=5

To customize the campaign member status picklist values themselves, marketing users need two things: a marketing user feature license and edit permission for campaigns. A marketing user feature license enables users to create, edit, and delete campaigns; manage campaign members; and update campaign history via the import wizards or API. Edit permission for campaigns allows users to modify existing campaigns and their related records such as campaign members and campaign member statuses. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_enable.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.htm &type=5

Themes are a way to customize the look and feel of Salesforce by changing the colors, images, and logos that appear on Lightning Experience pages. However, there are some limitations and considerations when using themes, such as: only one theme can be active at a time, and a theme applies to the entire org; themes apply only to Lightning Experience and do not affect Salesforce Classic or the Salesforce mobile app; up to 300 custom themes can be created, modified, or cloned from the built-in themes; Chatter external users see the built-in Lightning theme only and cannot see custom themes. References: https://help.salesforce.com/s/articleView?id=sf.themes_overview.htm &type=5

Custom object and master detail field are two steps that should be configured to meet this requirement. Custom object can be used to create a new object for shoe design that can store information about different designs and stages. Master detail field can be used to create a relationship between Product and Shoe Design that prevents deletion of Shoe Design records and allows multiple designs for one product. References: https://help.salesforce.com/s/articleView?id=sf.customize_customobjects.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

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

Forecasting is a feature that allows you to predict and plan the sales cycle from pipeline to closed sales, and manage sales expectations throughout your organization. Opportunity stages are the steps that an opportunity goes through as it moves from creation to close, and they determine the probability and forecast category of the opportunity. References: https://help.salesforce.com/s/articleView?id=sf.forecasting3_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_opptystages.htm &type=5

Page layout editor is a tool that allows you to customize the layout and organization of detail and edit pages for a specific object and record type combination. You can use page layout editor to make fields editable or read-only on page layouts for different profiles or record types. After resetting a password, the user may be required to activate their device by entering a verification code sent to their email address or phone number before they can log in to Salesforce. This is a security feature that helps prevent unauthorized access to Salesforce from unknown devices or browsers. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.identity_verification.htm &type=5

Lead assignment rule is a feature that can be used to route new leads to the correct sales person based on the lead address. Lead assignment rule can assign leads to users or queues based on certain criteria, such as lead source, industry, or location. Lead assignment rule can also send email notifications to the new lead owners or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

Muting permission sets allow you to remove permissions that are granted by a permission set group.

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

A related record component is a type of component that allows users to view and edit fields from a parent record on a child record page without leaving the page. For example, a related record component can allow users to update the account status from the case layout by selecting an account record from a drop-down list. A rich text component is a type of component that allows users to display formatted text on a record page using rich text editor tools such as bold font, bullet points, images, and links. For example, a rich text component can display a message in bold font when a case is saved as acriticalrecord type by using conditional visibility rules. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_related_record.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_rich_text.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. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

To show a component that shows LinkedIn data only to sales users when they are on their mobile phones, the administrator should filter the component visibility with two conditions:

• User > Profile > name = sales User, which checks if the user’s profile name is “sales User”
• Form Factor = phone, which checks if the user’s device is a phone Filtering with view or role will not achieve the desired result. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_page_visibility_rules.htm&type=5

Conditional visibility is a feature that allows administrators to show or hide screen components in a flow based on certain conditions or criteria. For example, conditional visibility can show only one question on a screen depending on the value of another field or variable. Conditional visibility consists of one or more rules that define when to show or hide a component based on an expression that evaluates to true or false. In this case, the administrator can use conditional visibility to hide the unnecessary question on the screen flow based on the scenario. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp.htm &type=5

Escalation rules allow you to escalate cases based on certain criteria, such as time or priority. You can use escalation rules to transfer unassigned cases to the appropriate service representative within a specified time frame.

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

Two options that should be added to Lightning record pages to make sales reps aware when they are speaking with high-profile customers are:

• Custom Component, which can display a custom message or icon on the record page based on certain criteria such as account rating or industry. For example, an administrator can create a custom Lightning Web Component that shows a star icon on account record pages if account rating is Hot or Warm.
• Component Visibility Filter, which can control when a component is visible on a record page based on field values of that record. For example, an administrator can add a component visibility filter to an existing component such as Path or Highlights Panel that makes it visible only if account rating is Hot or Warm. Highlight Panel, Action and Recommendations, and Rich Text Area are not options that can be used to make sales reps aware when they are speaking with high-profile customers. References: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.htm&type=5

To surface important values based on the stage of the opportunity, the administrator should use path key fields that display fields relevant to each stage along with guidance for success. Path key fields can be customized for each stage and can help users focus on key information and actions as they move opportunities through the sales process. Dynamic forms, opportunity processes, and workflow rules are not designed to show values based on stages. References: https://help.salesforce.com/s/articleView?id=sf.path_key_fields.htm &type=5

A standard fiscal year starts on January 1 and ends on December 31. A custom fiscal year can be set to start on any month and end on any month. In this case, Cloud Kicks wants its fiscal year to start on February 1 and end on January 31. This can be achieved by setting the fiscal year to Custom and the starting month to February.

Setting the fiscal year to Standard and the starting month to February will not work, as the standard fiscal year starts on January 1. Setting the fiscal year to Custom and the duration to 4 quarters will not work, as the duration of a fiscal year is 12 months. Setting the fiscal year to Standard and the duration to 12 months will not work, as the standard fiscal year starts on January 1.

Custom fiscal years are fiscal years that follow a custom-defined structure that differs from the Gregorian calendar. They can be used by organizations that have fiscal years that start on a different month than January or have fiscal years that are divided into custom periods such as quarters or weeks. To set up a custom fiscal year that starts on February 1 and has 12 months, an administrator needs to set the fiscal year to custom and the starting month as February in the fiscal year settings. Setting the fiscal year to standard or the duration to 4 quarters does not meet the requirement of having a custom fiscal year that starts on February 1. References: https://help.salesforce.com/s/articleView?id=sf.admin_fiscal_year.htm &type=5

One thing that an administrator should be aware of before changing an auto-number field to text field is that this change is prevented by Salesforce; it cannot be done because it would cause data loss and inconsistency. Auto-number fields are fields that automatically assign unique numeric values to each record; they cannot be changed to text fields because text fields do not have this functionality and may allow duplicate or invalid values. Existing field values remaining unchanged, being converted, or being deleted are not things that would happen before changing an auto-number field to text field because this change cannot happen at all. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_auto_number.htm &type=5

Permission sets are used to grant additional permissions and access settings to individual users without changing their profiles or requiring a new profile to be created. You can use permission sets to extend users’ functional access without changing their existing profiles. To meet the request of giving comprehensive edit access on Campaigns to a few marketing users who have read-only access by default, you need to create a permission set with edit access on Campaigns and assign it to those users. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5

Two ways that marketing users can now access converted leads for editing are:

• Find them in the global search result, by entering the lead name or other keywords in the global search box and selecting Leads from the drop-down menu. Converted leads will appear in the search result with a check mark icon next to them.
• Utilize a list view where lead status equals Qualified, by creating or modifying a list view on the Leads tab and adding a filter for Lead Status equals Qualified. Converted leads will have Qualified as their lead status and will be visible in the list view. Searching the Recent Records component on the homepage or using Data Import Wizard will not allow users to access converted leads for editing. References: https://help.salesforce.com/s/articleView?id=sf.leads_view_converted.htm&type=5

A gauge component shows a single value along with its percentage of a total value within predefined ranges using colors (red-yellow-green). It is useful for showing key performance indicators (KPIs) such as total sales amount and progress towards sales goal. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_gauge_component_type.htm &type=5

A validation rule is a tool that allows administrators to enforce data quality and integrity by preventing users from saving records that do not meet certain criteria or conditions. For example, a validation rule can display an error message if a user enters an invalid value in a field. In this case, the administrator can create a validation rule on the account object that displays an error if the account annual revenue field is below 0 or greater than 100 billion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

Knowledge articles are documents that provide information or solutions about products, services, or processes in Salesforce. You can use knowledge articles to respond to customers quickly and consistently with accurate information. You can create different types of articles with different templates and fields, such as FAQ articles, troubleshooting articles, how-to articles, etc. To meet the requirement of responding to customers with the top five troubleshooting tips that could help solve their issue, you need to create knowledge articles with those tips and attach them to your email responses or case comments. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_article_types.htm &type=5

Campaign hierarchy is a feature that allows administrators to organize campaigns into a parent-child relationship, where the parent campaign represents a larger initiative and the child campaigns represent smaller or more specific activities within that initiative. Using campaign hierarchy can help Ursa Major Solar report on campaign ROI by month and series by creating a parent campaign for the series of networking events and creating individual child campaigns for each monthly event. The parent campaign can show the aggregated metrics and ROI for the entire series, while the child campaigns can show the metrics and ROI for each month. Adding different record types for the monthly event types, creating individual campaigns that all have the same name, or configuring campaign member statuses to record which event members attended are not solutions for reporting on campaign ROI by month and series; they either do not group campaigns into a hierarchy or do not track campaign metrics or ROI. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_hierarchy.htm &type=5

A support process is a feature that allows administrators to define and enforce the stages that a case or work order must go through based on its record type. A support process determines which values are available for the status field for each record type. If a support process omits a certain value for the status field, such as Closed, then users will not be able to see or select that value when working with cases or work orders of that record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthome.htm &type=5

Data Import Wizard allows you to import up to 50,000 records at a time.

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

Log in as the user is a feature that can be used to validate the error the user is receiving. Log in as the user allows an administrator to access Salesforce as another user and perform actions on their behalf, such as editing an opportunity. This can help troubleshoot issues that are specific to a user’s profile, role, or permissions. References: https://help.salesforce.com/s/articleView?id=sf.admin_login.htm &type=5

To advertise on TV, radio, print, and social under one banner called New Runners and aggregate total statistics for this marketing effort, an administrator should use Parent campaign field on Campaign object. This field allows creating hierarchical relationships between campaigns by specifying one campaign as parent of another campaign. Parent campaigns roll up statistics from child campaigns such as number of leads generated, amount of revenue won etc. For example, an administrator can create four child campaigns for TV, radio, print and social ads respectively and link them to one parent campaign called New Runners using Parent campaign field. Junction object, lookup relationship, and master-detail relationship are not features related to Campaign object or hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_parent.htm &type=5