Salesforce-Certified-Administrator Sample Questions Answers

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://he lp.salesforce.com/s/articleView?id=sf.app_builder_utility_bar.htm&type=5

Assignment rules and queue configuration are two options that should be used to help the support team work on some of UC’s cases. Assignment rules can be used to automatically assign cases to a queue based on certain criteria, such as case origin or priority. Queue configuration can be used to add Case as an available object to the existing queue and specify which users or groups can access the queue. References: https://help.salesforce.com/s/articleView?id=sf.case_ass ignment_rules.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.customize_queues.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

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

Master-detail lookup is a type of relationship field that can be used to create a relationship between Account and Shoe and prevent orphaned Shoe records. Master-detail lookup establishes a parent-child relationship between two objects, where the parent record controls certain behaviors of the child record, such as security, ownership, and deletion. If the parent record is deleted, all the child records are deleted as well. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.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.app rovals_considerations.htm&type=5

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

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

• A. Dependent Picklist

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

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

• Record Type: New Account
• Picklist Values: Residential, Commercial
• Record Type: Existing Account
• Picklist Values: Renewal, Upsell, Cross-sell

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

• B. Custom Picklist

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

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

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

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

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

The mass transfer tool allows you to transfer up to 250 records at a time from one user to another user while keeping the existing team members intact. You can access this tool from Setup by entering Mass Transfer Records in the Quick Find box. References: https://help.salesforce.com/s/articleView?id=sf.mass_transfer_overview.htm &type=5

Email-to-Case allows administrators to set up routing addresses that automatically create cases from incoming emails and assign them to queues based on predefined criteria. This way, emails from customers can generate cases automatically and be sent to the correct queue. A flow is a tool for building automated processes, but it is not designed for email routing. A custom email service is a way to process inbound emails using Apex code, but it requires coding skills and is more complex than Email-to-Case. An escalation rule is a way to escalate cases based on certain conditions, but it does not create cases from emails or assign them to queues. References: https://help.salesforce.com/s/articleView?id=sf.customize_email2case.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

Split views are a feature that allows users to view records as a split list on object home pages in Lightning Experience apps that use console navigation. Split views show records in two panes: a list view pane on the left and a record detail pane on the right. Users can switch between different list views and records without losing context or scrolling. However, split views are only available on standard objects such as accounts, contacts, leads, opportunities, cases, etc., and not on custom objects such as shipments. References: https://help.salesforce.com/s/articleView?id=sf.lex_split_view.htm &type=5

Path is a feature that can be used to visually see the sales stages on an opportunity page. Path can include guidance and key fields for each stage to help users move opportunities along the sales process. Guidance can provide tips, policy information, or best practices for each stage. Key fields can display important fields that users need to fill in or update for each stage. References: https://help.salesforce.com/s/articleView?id=sf.path_overview.htm &type=5

To use Data Loader to mass import new records to a custom object from a new API, the administrator will need to append their security token at the end of their password to login. The security token is an alphanumeric code that is required for API access when logging in from an IP address that is not trusted by Salesforce. The security token can be obtained from the user’s personal settings or by resetting it via email. Adding a permission set, resetting the password and the security token, or using the Data Import Tool are not necessary for using Data Loader. References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_token.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

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 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

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

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/article View?id=sf.customize_casesupport_assign.htm&type=5

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

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

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

Component visibility allows you to restrict the visibility of a related list based on a permission set.

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

A junction object is a type of custom object that allows administrators to create many-to-many relationships between two other objects. A many-to-many relationship means that each record of one object can be related to multiple records of another object, and vice versa. For example, a junction object can represent that a contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.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

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_whi ch_tool.htm&type=5

Field update and email alert are two types of automated actions that can be added as part of the approval process. Field update allows you to change the value of a field on a record when it is submitted, approved, rejected, or recalled. Email alert allows you to send an email to one or more recipients when a record is submitted, approved, rejected, or recalled.

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

Case escalation rules are a way to automatically escalate cases that meet certain criteria, such as being open for more than a specified time or having a certain priority. Escalation rules can assign cases to a different owner or queue and send email notifications to the support manager or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5

Validation rules allow you to enforce data quality by preventing users from saving records that do not meet certain criteria.

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

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

Process Builder is an automation tool that allows you to create processes that perform actions based on criteria that you specify. You can use Process Builder to update fields on related records when a record is created or updated. To meet the requirement of updating the parent object Referral when the Referral Date field is updated on the custom object Referral Source, you need to create a process that triggers when a Referral Source record is updated, checks if the Referral Date field has changed, and updates the Referral Date field on the related Referral record. References: https://help.sa lesforce.com/s/articleView?id=sf.process_overview.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.h tm&type=5

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

References: https://appexchange.salesforce.com/

To require the Amount field during the negotiation stage for sales users but allow their managers to make changes, the administrator should configure a validation rule that checks if the user profile is not a sales manager, the stage is negotiation, and the amount is blank. This will prevent sales users from saving the record without entering an amount, but allow sales managers to do so. Making the field required for all users will not meet the requirement. Creating a formula field or assigning the administrator profile to the managers will not affect field requirement. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_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

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.salesfo rce.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/article View?id=sf.domain_mgmt_redirect.htm&type=5

Report type is a tool that can be used to pull contact fields into the custom report for Event. Report type defines the set of records and fields available to a report based on the relationships between a primary object and its related objects. To edit the custom Event report type and add fields related via lookup, go to Setup > Report Types and select the Event report type. Then click Edit Layout and drag the fields from the Contact object to the layout. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_create_report_type.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

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

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

To surface important values based on stage of opportunity , an administrator should use Path Key fields feature on Opportunity object . This feature allows adding up to five fields that display key information about each stage along path . Users can edit these fields inline without leaving path . For example , an administrator can add Amount , Close Date , Next Step , Probability , and Stage fields as key fields for Opportunity path . Opportunity Processes , Dynamic Forms , and Workflow Rules are not tools for surfacing important values based on stage of opportunity . References : https :// help . salesforce . com / s / articleView ? id = sf . lex_path_setup_key_fields . 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

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

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

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

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 scheduled flow is a type of flow that runs at scheduled times on batches of records that meet certain criteria. It can be used to count the number of open cases associated with each account and update the account with this value every Friday evening by using an assignment element to loop through the accounts and cases and assign the count value to a field on the account record. Using a record trigger flow, a scheduled process builder, or a roll-up summary field are not suitable options for this requirement because they would not run at scheduled times or on batches of records; they would run every time a record is created or updated, which may not reflect the accurate count of open cases at the end of each week. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_scheduled.htm&type=5

To require users to choose a specific search engine from a picklist when lead source is “Search Engine”, and hide it otherwise, the administrator should create a picklist for specific search engine on the same screen as lead source, and set conditional visibility so that it is only shown when lead source is “Search Engine”. This will make sure that users see only relevant fields based on their input. A decision element will create an extra screen that may disrupt user experience. An assignment element will not affect field visibility. A validation rule will not hide fields but only show errors when values are invalid. References: https://help.salesforce.com /s/articleView?id=sf.flow_ref_elements_screen_components_picklist.htm&type=5 https://help.salesforce.com/s/articleView?id =sf.flow_ref_elements_screen_components_conditional_visibility.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

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/articl eView?id=sf.monitoring_login_history.htm&type=5

To provide a summary of org’s security health, an administrator should run a Health Check that compares org’s settings against baseline settings defined by Salesforce Security Baseline Standard or industry standards such as CIS (Center for Internet Security) Benchmark Standard. Health Check generates an overall health score based on how org’s settings match with baseline settings for various security categories such as Password Policies, Network Access, Session Settings etc. Health Check also provides recommendations for improving org’s security health score by adjusting settings that do not match with baseline settings. Changing Org-Wide Default to private, turning on Event Monitoring, or downloading user login data will not provide a summary of org’s security health. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm &type=5

The Stage Setup Flow is a tool that allows administrators to customize stages for leads and opportunities based on best practices from Salesforce experts. The Stage Setup Flow guides administrators through a series of questions about their sales process and then creates or updates stages for leads or opportunities accordingly. The Stage Setup Flow also provides tips and resources for each stage such as key fields, guidance for success, reports and dashboards, etc. References: https://help.salesforce.com/s/articleView?id=sf.stages_setup_flow_overview.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. References: https://help.salesforce.com/s/articleView?id=sf.cust omize_layoutoverview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.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

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

When an administrator deletes a custom field, Salesforce moves it to the deleted fields list for 15 days, during which time it can be undeleted or erased permanently. If the administrator undeletes the field within 15 days, most of its properties and data are restored, except for its field history data, which remains deleted and cannot be recovered. References: https://help.salesforce.com/s/articleView?id=sf.custom_field_delete.htm &type=5

To route new leads to the correct sales person based on the lead address, the administrator should use lead assignment rules that specify criteria based on lead fields such as City, State/Province, or Country, and assign leads that match those criteria to queues or users. Lead assignment rules can be triggered automatically when leads are created or manually by users. Creating a formula field, assigning with an escalation rule, or configuring a validation rule will not route leads to sales people. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

A permission set group is a collection of permission sets that can be assigned to users as one unit; it simplifies permission management by reducing the number of permission assignments needed for users who require multiple permission sets. A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce; it can be used to extend users’ access beyond their profile without changing their profile. Creating permission sets and assigning permission set groups can help Cloud Kicks give access to new custom object with custom fields to more than one user by creating permission sets that include access to new custom object with custom fields and assigning permission set groups that contain those permission sets to users who need them. Adding users to manual sharing list or editing organization-wide defaults are not options for giving access to new custom object with custom fields to more than one user; they either do not apply to custom objects or do not grant object-level access. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_overview.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

A master-detail relationship is a parent-child relationship in which the master object controls certain behaviors of the detail object. The master object can be a standard or custom object, but not all standard objects support being a master. Roll-up summaries are fields that calculate the sum, count, min, or max of child records. The owner field on the detail records is not available and is automatically set to the owner of the master record.

References: https://www.forcetalks.com/blog/master-detail-relationship-in-salesforce/ https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.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

Role hierarchy and sharing rules are two features that should be used to open up access to Opportunity records for sales users working on collaborative deals. Role hierarchy can be used to grant access to records owned by or shared with users who are below them in the hierarchy. Sharing rules can be used to extend sharing access to users in public groups, roles, or territories based on certain criteria, such as record owner or field value. References: https://help.salesforce.com/s/articleView?id=sf.admin_sh aring.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm &type=5

One of the possible reasons why an administrator is unable to add a new user in Salesforce is that the username is already in use by another user in any Salesforce org. Usernames must be globally unique across all Salesforce orgs, so the administrator needs to choose a different username for the new user. References: https://help.salesforce.com/s/articleView?id=sf.users_add.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

To automate an outbound message, the administrator should use a workflow rule that defines the criteria for sending the message and the actions to perform when those criteria are met. One of the actions available for workflow rules is sending an outbound message to a designated endpoint URL with specified fields as parameters. Process builder, task assignment, and flow builder are not able to send outbound messages directly. References: https://help.salesforce.com/s/articleView?id=sf.workflow_define.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_action_outboundmessaging.htm &type=5

Two functions that an administrator should use when creating a validation rule are:

• Error condition formula, which defines when an error should occur based on record fields and values
• Error message location, which specifies where on the page layout an error message should appear when triggered by an error condition formula Formula return type and rule active date are not functions used for validation rules. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm&type=5

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

To help sales reps prioritize and close more deals, the administrator should use Einstein Opportunity Scoring, which is a feature that assigns each opportunity a score from 1 to 99 based on how likely it is to be won. The score is calculated using historical data and machine learning models, and can help reps focus on the most promising opportunities and take actions to improve their chances of winning. Einstein Activity Capture, Einstein Search Personalization, and Einstein Lead Scoring are not related to opportunity management. References: https://help.salesforce.com/s/articleView?id=sf.einstein_sales_oppty_scoring.htm &type=5

Probability is a standard percentage field on the Opportunity object that indicates how likely an opportunity will close successfully. It is automatically calculated based on the opportunity stage unless you make it editable on page layouts. To allow sales reps to change the probability field value of their opportunities, you need to make the field editable on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.opportunity_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5