Salesforce-Certified-Administrator Salesforce Certified Administrator (SU24) Questions and Answers

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

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

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

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

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

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

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

Contact, lead, and person account are three objects that will have the individual field available for tracking data privacy information when data protection and privacy is enabled for an org. The individual object is an object that stores data privacy preferences and requests for customers who are subject to privacy regulations such as GDPR; it can be linked to contact, lead, or person account records using the individual field. Case and opportunity, account and user, or individual, user, and account are not combinations of objects that will have the individual field available for tracking data privacy information; they either do not store customer data or do not support individual object relationships. References: https://help.salesforce.com/s/articleView?id=sf.individual_object.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

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

A formula field is a type of field that calculates a value based on an expression or formula that references other fields or constants. For example, a formula field can display today’s date by using the TODAY() function. In this case, the administrator can create a formula field on the account object that updates the audited date field with today’s date when the status of the account is changed to ‘Audited’. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

IP address restrictions allow you to prevent users from accessing Salesforce from outside of their network. You can set IP address restrictions on the profile level or globally for the org. To enforce IP restrictions for API logins, you must select Enforce Login IP Ranges on Every Request in Session Settings.

References: https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_enforce_ip_ranges.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

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

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

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

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

To ensure extra steps only appear when creating open house records for condominiums, an administrator can use two methods: create two page layouts; and use business processes and record types to display appropriate picklist values. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. An administrator can create two page layouts for open house records - one for houses and one for condominiums - and include different fields or sections for each page layout based on their requirements. A business process is a feature that allows administrators to define and enforce stages that records must go through based on their record type such as lead status or opportunity stage. A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts etc., to different users based on their profile or role. An administrator can create two record types for open house records - one for houses and one for condominiums - and assign different business processes and picklist values for each record type based on their requirements. References: https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.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 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

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.

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

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

Splits is a feature that should be used to meet this requirement. Splits allows users to assign credit to opportunity team members based on the level of effort contributed by each person toward each deal. Users can create different types of splits, such as revenue or overlay splits, and specify the percentage or amount of credit for each team member. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_splits_overview.htm &type=5

Account teams are groups of users who work together on an account. You can enable account teams in Setup and assign team roles and access levels for each team member. Users can set up a default account team that is automatically added to any account that they own or create. This makes it easier for teams to collaborate with the same customer without manually sharing each account. References: https://help.salesforce.com/s/articleView?id=sf.accountteam.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.accountteam_default.htm &type=5

A list view is a feature that allows users to filter and display records based on certain criteria and fields. A Kanban view is a feature that allows users to view records as cards organized by columns that represent stages in a process such as opportunity stages or case statuses. Users can switch between list view and Kanban view by clicking on a toggle button on any object tab that supports Kanban view such as opportunities or cases. Users can also edit records by dragging and dropping cards from one column to another or by clicking on an inline edit icon on each card. In this case, the administrator can create a list view on the opportunity object that filters opportunities by expected close date in the next 90 days; and recommend users switch the view to Kanban to edit opportunities by drag and drop. References: https://help.salesforce.com/s/articleView?id=sf.lex_list_views.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.kanban_view.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

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

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

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.

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

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

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

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

A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts, etc., to different users based on their profile or role. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. In this case, since Universal Containers has three separate lines of business with specific fields for each line; and since sales team needs different fields than service team; the administrator should create three record types for each line of business; and create two page layouts for each record type - one for sales team and one for service team. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.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 roll-up summary field is a type of field that calculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

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

Case escalation rules are a feature that can be used to meet this requirement. Case escalation rules can 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

A restricted picklist is a type of picklist that enforces the integrity of the picklist values by allowing only values defined in the picklist during data entry or import operations. If the restricted picklist checkbox is checked for a picklist field, then any records with values not defined in the picklist will cause errors during import operations. However, if the restricted picklist checkbox is unchecked for a picklist field, then any records with values not defined in the picklist will be imported without errors. References: https://help.salesforce.com/s/articleView?id=sf.picklist_limitations.htm &type=5

The likely cause for why a rehired user is no longer able to access records they worked on before leaving the company is that the records were manually shared with the user. Manual sharing allows granting access to individual records to specific users or groups. However, manual sharing is removed when a record owner changes or when a user’s role changes. When a user is deactivated, their role is removed and any manual sharing involving that user is deleted. When a user is reactivated, their role is restored but manual sharing is not. Therefore, the rehired user will not have access to records that were manually shared with them before deactivation. The stage of Opportunity records, permission sets, or record type of Opportunity records are not likely causes for why a rehired user is no longer able to access records they worked on before leaving the company. References: https://help.salesforce.com/s/articleView?id=sf.sharing_manual.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

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

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

Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.

References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.quick_actions_overview.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

The equals operator is an operator that compares two values and returns true if they are equal or false if they are not equal; it can be used in decision elements in flow builder to check if two values match certain criteria. The {!$GlobalConstant.True} value is a global constant value that represents true in flow builder; it can be used in decision elements in flow builder as one of the values being compared. Using equals operator and {!$GlobalConstant.True} as value can help Cloud Kicks update screen flow so that if checkbox field High Value Customer is set true first screen is skipped by using equals operator compare High Value Customer field value with {!$GlobalConstant.True} value in decision element output connector conditions; if condition is met first screen is skipped else first screen is shown. Using equals operator “High Value Customer” as value contains operator {!$GlobalConstant.False} as value contains operator “High Value Customer” as value are not valid options for updating screen flow skip first screen if checkbox field High Value Customer is set true because they either use wrong values wrong operators compare checkbox field values. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_operators.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.htm &type=5

To boost productivity by providing insights at the start of each day, the administrator should add three sales-specific standard Lightning components to the homepage:

• Activities, which shows tasks and events related to records that matter most to users
• Assistant, which provides personalized suggestions and reminders for key updates and actions
• Key Deals, which highlights important opportunities that need attention or are close to closing Path and Performance Chart are not standard Lightning components, but custom components that can be added to specific objects or pages. References: https://help.salesforce.com/s/articleView?id=sf.home_components.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

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

To see certain information about one or more cases when referencing the contact record, an administrator can use two methods: edit the Related List component in the Lightning App Builder and choose Related List as the related list type; and use the page layout editor to include the appropriate column in the Cases related list. The Related List component is a component that allows users to view and edit records related to a parent record on a record page. The Related List component has two types: Related List and Enhanced List. The Related List type shows records in a table format with columns that match the page layout of the parent record. The Enhanced List type shows records in a compact format with fewer columns and actions. To change the type of the Related List component, an administrator can use the Lightning App Builder and select either Related List or Enhanced List from the properties panel. The page layout editor is a tool that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. To include appropriate columns in a related list, such as case name, case ID, customer name, case reason, case status, and case creation date for cases related to contacts, an administrator can use the page layout editor and drag and drop the desired fields from the palette to the Cases related list on the contact page layout. References: https://help.salesforce.com/s/articleView?id=sf.lex_related_lists_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.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

A user with manager role above the agent can change ownership on multiple cases that are owned by the agent or by users below the agent in the role hierarchy. A user with the System Administrator profile can change ownership on any case, regardless of the owner or role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.case_change_owner.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_userperms.htm &type=5

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

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

Grant access using Hierarchies is a setting that can be used to configure the custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_custom_objects.htm &type=5

An ID variable is a type of variable that can store an ID value of a record or a record type in a flow. It can be used to store the ID of a record type for later use in a flow, such as assigning it to a record or using it in a condition. A boolean variable is a type of variable that can store a true or false value in a flow. A text variable is a type of variable that can store a text value in a flow. A record variable is a type of variable that can store one or more field values of a record in a flow. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_variables.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

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.salesforce.com/s/articleView?id=sf.process_overview.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

 Geolocation fields allow you to store the latitude and longitude coordinates of a location. They can be used to calculate distances between records and display maps of accounts, contacts, leads, or other custom objects. References: https://help.salesforce.com/s/articleView?id=sf.customize_geoloc.htm &type=5

Flow Builder and Process Builder are two automation tools that should be used to accomplish this request. Flow Builder can be used to create a flow that defines the logic and actions for creating a renewal opportunity, such as setting the stage, close date, and amount. Process Builder can be used to create a process that triggers the flow when an opportunity is closed won. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

To access the account object in Salesforce, users need to have permission to the account object on their profile or permission set. Permission to an object determines what users can do with records of that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission to an object, they will not be able to see or access that object in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.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

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.customize_layoutoverview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.htm &type=5

Lightning app pages, Chatter, and dashboards are three items that are available in the mobile navigation menu. The mobile navigation menu allows users to access different items in the Salesforce mobile app, such as objects, apps, or utilities. Users can customize their mobile navigation menu by adding or removing items and changing their order. References: https://help.salesforce.com/s/articleView?id=sf.app_nav_setup.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

Contacts to multiple accounts is a feature that allows you to associate a single contact with multiple accounts, both business and person accounts. This way, you can maintain the historical accuracy of the contact record without creating duplicate records for each account. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.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