Salesforce Salesforce-Certified-Administrator Salesforce Certified Administrator Exam (SP23) Exam Practice Test

Security Health Check is a tool that can be used to identify and fix potential session vulnerabilities. Security Health Check scans the security settings in an org and compares them to a baseline set of standards, such as the Salesforce Baseline Standard or the Salesforce Optimized Standard. Security Health Check provides a health check score and a list of issues and recommendations for improving the security settings. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.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 Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

To make sure the custom picklist field values are populated on contact when leads are converted, you need to create a custom picklist field on contact and map it to the corresponding field on lead.

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

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields such as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.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

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

Flow builder is an automation tool that allows administrators to create flows that guide users through screens, collect data, and perform actions on records. It can be used to simplify the account creation process by creating a screen flow that shows only the essential fields for creating an account and hides any unnecessary fields or sections from the page layout. Approval process, workflow rule, and validation rule are not automation tools that can simplify the account creation process; they are used for different purposes such as approving records, updating fields, or enforcing data quality. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.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

Manual sharing allows record owners to share individual records with other users or groups. This is useful when one-off sharing is needed for a specific situation. Hierarchical sharing, criteria-based sharing and owner-based sharing are not suitable for this scenario because they are based on predefined rules or roles that do not match the requirement. References: https://help.salesforce.com/s/articleView?id=sf.sharing_overview.htm &type=5

Permissions and tab visibility are two options that administrators can adjust to fully restrict access to records for certain users or profiles. Permissions determine what users can do with records, such as create, read, edit, delete, view all, or modify all. Tab visibility determines whether users can see a specific object tab in their app launcher or navigation bar. By setting permissions and tab visibility to none or hidden for deal records for service users or profiles, administrators can prevent them from accessing deal records via search or other methods. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_tabs.htm &type=5

Validation rules allow you to prevent users from changing an opportunity close date to a date in the past.

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

Case escalation rules are used to escalate cases that have not been resolved within a certain time frame by changing the case owner, sending email notifications, or triggering workflow actions. You can use these actions to alert the appropriate users or groups when a case needs urgent attention or escalation. References: https://help.salesforce.com/s/articleView?id=sf.customize_caseesc.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

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 also use page layout editor to customize related lists on detail pages by adding or removing fields, changing column order, sorting records, etc. To meet the requirement of showing different fields on the Case related list from the Account record for Sales and Customer Care users, you need to use page layout editor to modify the related list properties for each page layout assigned to those users. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutrelatedlists.htm &type=5

A criteria-based sharing rule is a tool that allows administrators to share records with certain users based on field values rather than ownership. For example, a criteria-based sharing rule can share all opportunities with a cross-sell opportunity type with a specific group of users. A public group is a collection of individual users, roles, roles and subordinates, or other groups that can be used to simplify sharing settings and other processes. In this case, the administrator can add the subject matter experts to a public group and give them access to records with a criteria-based sharing rule that matches the cross-sell opportunity type. References: https://help.salesforce.com/s/articleView?id=sf.sharing_criteria_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.public_groups.htm &type=5

Default language and currency locale are two options that an administrator should configure in the company settings to support a global team of Salesforce users. Default language determines the language that is used for labels, buttons, tabs, help text, and messages in Salesforce for all users unless they override it in their personal settings. Currency locale determines the format of currency fields and numbers in Salesforce for all users unless they override it in their personal settings or enable multiple currencies. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.htm &type=5

Big Deal Alerts are notifications that are sent to users when an opportunity reaches a certain amount, probability, or stage. They can be configured by administrators to alert sales reps or managers when they have a high likelihood of winning a big deal. Key Deals are a feature of Einstein Opportunity Scoring that shows the top opportunities based on their score and stage, but they do not send notifications. Activity Timeline is a component of Lightning Experience that shows the past and upcoming activities related to a record, but it does not notify users of big deals. Performance chart is a type of report chart that shows how well users or teams are performing against their goals, but it does not alert users of big deals. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_big_deal.htm &type=5

Two considerations for preventing users from accessing Salesforce from outside of their network are:

• IP address restrictions are set on the profile or globally for the org, which limit login access based on IP ranges specified by an administrator
• Restrict U2F Security Keys on the user’s profile to enforce login hours, which require users to use security keys during certain hours of day Assigning single sign-on to a permission set or enforcing Login IP Ranges on Every Request will not prevent users from accessing Salesforce from outside of their network. References: https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_keys_restrict.htm&type=5

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

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

A lookup field is a type of field that creates a relationship between two objects and allows users to select a record from one object as a value for another object. A lookup relationship creates a one-to-many relationship between two objects, where each parent record can have many child records but each child record can have only one parent record. A lookup relationship also allows limited access to child records, meaning that users can see only those child records that they have access to based on their profile permissions and sharing settings. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.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

Running the flow using it to create contacts and using debug to test the flow in Flow Builder are two key components of testing a new screen flow that creates contacts. Running the flow allows the administrator to see how the flow behaves in real time and check for any errors or unexpected results. Debugging the flow allows the administrator to simulate how the flow runs with different inputs and outputs and check for any logic or syntax errors. Setting up a flow interview or testing the flow in a sandbox are not necessary for testing a screen flow that creates contacts. References: https://help.salesforce.com/s/articleView?id=sf.flow_test.htm &type=5

The AppExchange is an online marketplace where customers can find apps, components, consultants, developers, and more to extend Salesforce functionality or solve specific business challenges. Some of the actions that can be accomplished via AppExchange are finding certified developers and consultants who can help with custom development or implementation projects; installing industry-specific solution templates that provide preconfigured apps, dashboards, reports etc., for various industries such as manufacturing or healthcare; downloading free tools or components that enhance productivity or user experience; browsing reviews or ratings from other customers who have used certain products or services; etc. References: https://appexchange.salesforce.com/

Native debug feature is a tool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings that indicate where the flow failed or might fail. References: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm &type=5

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. References: https://help.salesforce.com/s/articleView?id=sf.reports_opportunity_stage_duration_report.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

Two considerations when installing a managed package in a sandbox are:

• The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
• The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5

To automate applying discounts on opportunity products when an opportunity is won, the administrator should use Flow Builder, which is a tool that allows creating complex business processes with clicks. The administrator can create an autolaunched flow that runs when an opportunity is updated, checks if its stage is “Closed Won”, and updates its related opportunity products with discounts from a formula or variable. Approval Process, Prebuilt Macro, and Formula Field are not able to update related records based on criteria. References: https://help.salesforce.com/s/articleView?id=sf.flow_build_overview.htm &type=5

To re-assign cases that meet the 24 hour SLA to the next tier queue, the administrator should use a case escalation rule that defines the criteria for escalating cases, such as age or priority, and the actions to perform when those criteria are met, such as changing owner or sending email alerts. Case escalation rules can help ensure that cases are handled in a timely manner and escalated to appropriate users or queues. Einstein Case Routing, Auto-response rule, and Case assignment rule are not able to re-assign cases based on SLA or age. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.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

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

Two-factor authentication requires users to verify their identity with two pieces of information when they log in to Salesforce. One piece is their username and password, and the other is a verification code from an authenticator app or email or SMS.

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

Utility bar is a feature that is available in a Lightning app where visibility is limited to the Salesforce mobile app. Utility bar allows users to access common productivity tools, such as notes, history, recent items, and more, from any page in the app. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_utility_bar.htm &type=5

Lightning record page is a type of page that should be created to meet this requirement. Lightning record page allows an administrator to customize the layout and components for a specific object record page in Lightning Experience or the Salesforce mobile app. To create tabs for account details, related lists, and chatter feeds, use the Tabs component in the Lightning App Builder and drag the desired components to each tab. References: https://help.salesforce.com/s/articleView? id=sf.app_builder_record_page.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_tabs.htm &type=5

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

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

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

Dynamic dashboards allow you to display data according to the security settings of the running user. If users have different access levels to data on dashboards, you can use dynamic dashboards to show them only what they are allowed to see.

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

Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

Flow Builder supports creating a screen that can launch a simple discount calculator when a button is clicked on an opportunity.

References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_button.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. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Einstein Opportunity Scoring is a feature that helps sales reps prioritize and close more deals by assigning each opportunity a score from 1 to 99 based on how likely it is to be won. The score is calculated using artificial intelligence and machine learning based on historical data and patterns from similar opportunities. Sales reps can use the score to focus on high-value opportunities and take actions to improve low-scoring ones. References: https://help.salesforce.com/s/articleView?id=sf.einstein_sales_oppty_scoring.htm &type=5

To enable users to add repeating tasks in Salesforce, the administrator needs to do two things: first, enable the creation of recurring tasks in activity settings under setup; second, add the create recurring series of tasks field on the page layouts for tasks. This will allow users to create a series of tasks that repeat based on a specified frequency and end date. References: https://help.salesforce.com/s/articleView?id=sf.tasks_repeating.htm &type=5

Standard objects are objects that are included with Salesforce by default, such as Account, Contact, Lead, Opportunity, etc. They have predefined fields and functionality that support common business processes. Custom objects are objects that you create to store information that is specific to your organization or industry. You can create new standard objects using the Object Manager in Setup. References: https://trailhead.salesforce.com/en/content/learn/modules/data_modeling/standard_and_custom_objects

Case escalation rules allow you to escalate cases based on certain criteria, such as time or priority.

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

Minimum password length and password complexity requirement are two settings that administrators can configure to increase the security of user passwords in Salesforce. They determine how long and how complex the passwords must be to meet the security standards. Password different than username and prevent common words are not valid settings in Salesforce, although they are good practices for creating strong passwords. References: https://help.salesforce.com/s/articleView?id=sf.admin_password_policies.htm &type=5

To capture the expiration date of warranty based on installation date and warranty length (1 year by default), the administrator should use a formula as the default value of Warranty Expiration Date field on Installation object. The formula can calculate one year from installation date using DATE function or DATEVALUE function. For example, DATE(YEAR(Installation_Date__c) + 1 , MONTH(Installation_Date__c) , DAY(Installation_Date__c)) will return one year from installation date. Creating a formula field, adding a validation rule, or including Warranty Expiration Date field on mobile page layout will not capture expiration date based on installation date and warranty length. References: https://help.salesforce.com/s/articleView?id=sf.formula_using_date_datetime.htm &type=5

Business hours are used to specify the days and hours when your company’s employees work. You can create multiple sets of business hours for different time zones or regions and assign them to users based on their location or function. To meet the requirement of having different business hours for reps on pacific time and eastern time, you need to create one set of business hours per time zone and assign them accordingly. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_supporthours_assign.htm &type=5

To protect data with backups by using Data Export Service, two considerations that the administrator should remember when scheduling export are:

• Data Backups are limited to weekly or monthly intervals depending on edition and license type
• Metadata backups must be run via a separate process such as Metadata API or change sets because Data Export Service only exports data (records) Metadata backups are not limited by sandbox refresh intervals. Data Export Service should be run from production orgs unless testing purposes require otherwise. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm&type=5

To create a contact and an opportunity from a lead that is associated with a campaign, and keep the campaign member history, the administrator should convert the lead from the campaign member detail page. This will automatically create a contact, an account, and an opportunity that are linked to the campaign. Deleting, cloning, or adding a contact will not preserve the campaign member history. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_leads.htm &type=5

To identify why a user is unable to log in to Salesforce, the administrator should review the login history for the user. The login history shows the date and time of each login attempt, the source IP address, the browser and platform used, the login type (such as username and password or single sign-on), and the status (such as success or failure). The login history can help troubleshoot common login issues such as incorrect username or password, invalid security token, IP restrictions, or login hours violations. Checking the attempted logins by running the setup audit trail, pulling the password history, or resetting the security token for the profile will not help identify why a user is unable to log in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

To share report folders with different groups of users with different levels of access, an administrator can use folder sharing settings under setup. Folder sharing settings allow administrators to share report folders with public groups, roles, roles and subordinates, territories, or portal roles with view or edit access. In this case, the administrator can share the Helpdesk folder with Support Agents with view access so they can run Helpdesk reports but not edit them; and share the R&D folder with Support Managers with edit access so they can view and edit R&D reports. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_folders_sharing.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

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.

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

Report folders are used to organize and secure reports in Salesforce. You can set different levels of access for different users or groups on each report folder. To preserve the integrity of the source reports for dashboards, you can create a new report folder with viewer access only and move the dashboard reports to that folder. This way, users can view the reports but not edit them. References: https://help.salesforce.com/s/articleView?id=sf.reports_folders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_dashboard_folder_access.htm &type=5

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

Record types allow you to update the options in a picklist based on the kind of opportunity.

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

To debug a screen flow that creates contacts, one of the possible causes for a variable missing on the debug screen is that the available for input checkbox was unchecked for that variable. This means that variable cannot be set by external sources such as debug inputs or URL parameters. To fix this issue, check this checkbox for any variable that needs to be set externally. The flow version or field type does not affect variable availability for input. The available for output checkbox only affects whether variables can be passed out of flows or subflows. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_variables.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_debugging.htm &type=5

Prebuilt email templates are email templates that have been created and provided by Salesforce for common use cases such as sending welcome messages, confirmation emails, etc. They can be used by Cloud Kicks to have consistency when communicating with customers on cases via email channel with categories to help search for the proper message. Prebuilt email templates can be accessed from the email action in the case feed or from the email composer in Lightning Experience. They can also be filtered by category to find the most relevant template for each case. Prebuilt quick texts, prebuilt flow templates, and prebuilt auto-responses are not solutions for having consistency when communicating with customers on cases via email channel; they are used for different purposes such as inserting common phrases, creating guided processes, or sending automated replies. References: https://help.salesforce.com/s/articleView?id=sf.email_templates_prebuilt.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.email_templates_use.htm &type=5

Process Builder is a tool that can be used to implement this request. Process Builder can create record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can create a flow that executes when a contact with a title of CEO is created and updates the contact’s account record with the CEO’s name. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.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

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

When you mark a field as required in Object Manager, the field is universally required to save a record on that object in the user interface. However, the field is not required to save records via the API on that object, unless you also mark it as required on the page layout.

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

To transfer data from a lead custom field to an opportunity field upon lead conversion, an administrator needs to create a custom field on the opportunity object that matches the data type and length of the lead custom field, and then map the two fields using the lead field mapping tool under setup. This will ensure that the value of the product category field on the lead is copied to the corresponding field on the opportunity when the lead is converted. References: https://help.salesforce.com/s/articleView?id=sf.leads_customize_map.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

Support processes allow you to define different status values for different record types on cases.

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

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadrules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.htm &type=5

Dependent picklist and global picklist are two options that can be used to meet this requirement. Dependent picklist allows users to create a conditional relationship between two picklist fields, where the available values in one field depend on the value selected in another field. Global picklist allows users to create a set of picklist values that can be shared across multiple fields and objects, ensuring consistent values and reducing maintenance. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_dependent_picklists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.picklist_global_picklists.htm &type=5

Email-to-Case allows you to create cases from incoming emails. You need to enable this feature and set up routing addresses and case creation settings.

References: https://help.salesforce.com/s/articleView?id=sf.customizesupport_email_to_case.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

The login history is a tool that allows administrators and users to view information about recent login attempts, such as date, time, status, source IP address, browser type, platform, application, and login type. Administrators can use this tool to identify why a user is unable to login to Salesforce by checking for any failed login attempts and their corresponding error messages or reasons. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.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

Get Records is a flow element that allows you to retrieve one or more records from an object that meet certain conditions and store them in a collection variable or a record variable for use later in the flow. You can also choose which fields from those records you want to store in variables. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_data_getrecords.htm &type=5

A custom profile is a profile that can be created and customized by administrators to define what users can see and do in Salesforce based on their job function or role. It can be used by Cloud Kicks to give read, create, and edit access for objects and restrict users from deleting any records by creating and assigning a custom profile with delete access removed for each object in the object settings. Assigning the standard system administrator profile to analytical user, giving user view all access and assigning them to highest role in role hierarchy, or creating and assigning permission set that includes read, create, and edit access are not solutions for giving read, create, and edit access for objects and restricting users from deleting any records; they either give too much access or do not remove delete access. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles.htm &type=5