Salesforce-Certified-Administrator Exam Dumps - Salesforce Certified Administrator Exam (SP23)

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Lead object to display an error message if the Lead Status field is marked as qualified and the Budget field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

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

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

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

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

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

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 enable record sharing and collaboration with groups, you need to add the groups related list to the object layouts and configure the Add Record action in the group publisher.

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

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

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

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

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

Screen flow allows you to create a form that collects user input and performs actions based on that input. You can use screen components to display questions and instructions, and use flow logic to update records or send notifications.

References: https://trailhead.salesforce.com/content/learn/modules/screen-flows/get-started-with-screen-flows https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.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

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

Big Deal Alerts allow you to notify users when an opportunity reaches a certain amount or probability.

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

Two reasons that would prevent a user from being deactivated are that the user is part of a territory hierarchy or that the user is assigned in workflow email alert. A territory hierarchy is a structure that defines how territories are related to each other in Salesforce; if a user is part of a territory hierarchy, they cannot be deactivated until they are removed from all territories. A workflow email alert is an action that sends an email to one or more recipients when a workflow rule is triggered; if a user is assigned in workflow email alert, they cannot be deactivated until they are removed from all email alerts. The user being in a custom hierarchy field or being the highest role in role hierarchy are not reasons that would prevent deactivation; they may affect data visibility or record ownership after deactivation, but they do not block deactivation itself. References: https://help.salesforce.com/s/articleView?id=sf.users_deactivate_considerations.htm &type=5

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

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

To create a many-to-many relationship between two existing custom objects, the administrator needs to create a junction object that has two master-detail relationships, one to each of the custom objects. This will allow each record of one object to be linked to multiple records from another object and vice versa. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

Permission sets are a flexible way to grant additional access to users without changing their profiles. To provide access to the lead object for a team of support users, create a permission set that includes the appropriate object and field permissions for leads, and then assign it to the users. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.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

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.

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

Recurring tasks are tasks that repeat at regular intervals, such as daily, weekly, monthly, etc. They can be created by users who have the permission to create recurring tasks, which can be enabled by administrators in the user profile settings. Flow, workflow rule, and recurring activities are not valid options for creating recurring tasks in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.tasks_recurring.htm &type=5

Compact layouts determine which fields appear in the highlights panel on record pages and in the Salesforce mobile app. To create a custom compact layout, go to the Account object manager and select Compact Layouts from the sidebar menu. Then click New and add the desired fields to the layout. References: https://help.salesforce.com/s/articleView?id=sf.compact_layouts_create.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

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

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

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

To assign agent capacity and skill set, the administrator should enable Omni-Channel, which is a feature that allows agents to work on multiple cases or chats at once based on their availability and expertise. Omni-Channel can route work items to agents based on their predefined capacity and skills, ensuring that they are working on the right tasks at the right time. Knowledge Management, Escalation Rules, and Territory Management are not related to agent capacity and skill set. References: https://help.salesforce.com/s/articleView?id=sf.omnichannel_overview.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

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

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 track assigned licenses and permission sets in Salesforce instead of using a spreadsheet, an administrator should use User Report type on Report object. User Report type allows creating reports that show information about users such as their profile, role, license type, active status, login history etc. It also allows adding fields related to permission sets such as Permission Set Assignments or Permission Set License Assignments. For example, an administrator can create a User Report that shows user name, profile name, user license name, permission set assignments count etc. Login History, Lightning Usage App, or Permission Set Groups are not features that can be used to track assigned licenses and permission sets in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_report_types_standard_user.htm &type=5

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

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

To 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

Flow Builder is a tool that can be used to create an automated way to delete records based on field values. Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm &type=5

Delegated approver is a feature that should be used to fulfill this requirement. Delegated approver allows users to delegate their approval authority to another user for a specified period of time, such as when they are out on vacation. Users can specify which approval requests they want to delegate and who they want to delegate them to. References: https://help.salesforce.com/s/articleView?id=sf.approvals_delegate.htm &type=5

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

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

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

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

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

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

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

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

A flow can be active or inactive depending on whether you want it to run or not. An inactive flow cannot be run by users or processes until you activate it. If a flow in production is supposed to create new records but it is not doing so, it could be because the flow is inactive and needs to be activated. References: https://help.salesforce.com/s/articleView?id=sf.flow_distribute_activate.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

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

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

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

Setup audit trail is a tool that allows administrators to review recent configuration changes made in their org. It shows a list of up to 180 days of setup changes made by anyone in the org, including the date, time, user, and type of change. It can help administrators track who made what changes and when, and troubleshoot any issues caused by configuration changes. Critical updates are notifications that inform administrators of new features or enhancements that may impact their org; they do not show configuration changes made by users. Debug logs are records of database operations, system processes, and errors that occur when executing a transaction or running unit tests; they do not show configuration changes made by users either. Field history tracking is a feature that allows administrators to track changes to the values of certain fields on records; it does not show configuration changes made in setup. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

Contract is a standard object that represents a contractual agreement between your company and a customer. Case is a standard object that represents a customer’s question or problem that needs to be resolved by your support team. Account is a standard object that represents an individual or an organization involved in your business, such as customers, competitors, partners, etc. These three objects are commonly used for service use cases in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.contract_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account_fields.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

App page and record page are two types of pages that an administrator can build and customize using Lightning App Builder for Salesforce mobile app. App pages are pages that display information or tools that don’t belong to a specific record; they can be accessed from navigation menus or tabs in Salesforce mobile app. Record pages are pages that display information or actions related to a specific record; they can be accessed by opening any record in Salesforce mobile app. User page and dashboard page are not types of pages that can be built using Lightning App Builder for Salesforce mobile app; they are types of pages that can be built using other tools such as Profile settings or Dashboard Builder. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_mobile_pages.htm &type=5

One of the possible causes for being unable to add a new user in Salesforce is that the username is already in use by another organization. Usernames must be globally unique across all Salesforce orgs, so if another user has claimed that username before, it cannot be used again. To fix this issue, choose a different username that is not taken by anyone else. The username is not restricted to a domain specific to my domain unless specified by an administrator. The email address used for the username does not have to match a contact record. The email used for the username can be any valid email address. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_add.htm &type=5

 Discount is not a standard field on the Opportunity object, so you need to create a custom field to capture the discount amount or percentage for each opportunity. To set up an approval process where opportunity discounts over 30% need to be approved by the VP of sales, and any discounts above 10% need to be approved by the user’s manager, you need to configure two separate approval processes with different entry criteria based on the discount field value and different approvers based on their roles. References: https://help.salesforce.com/s/articleView?id=sf.approvals_getting_started.htm &type=5

To track shoe designs by products, prevent them from being deleted, and allow multiple designs for one product across various stages, the administrator should create a custom object for shoe designs and configure a custom lookup field for shoe designs on the Product object. This will create a one-to-many relationship between products and shoe designs, and allow users to link multiple shoe designs to one product record. To prevent shoe designs from being deleted, the administrator can use validation rules or permissions. Adding a custom master-detail field for shoe designs on the Product object will create a many-to-one relationship, which is not desired. Using the standard object for designs or configuring a validation rule will not meet the requirement. References: https://help.salesforce.com/s/articleView?id=sf.customize_object_relationships_overview.htm &type=5

To provide appropriate access to a report that contains shoe records for all of the sales reps on their team, the administrator should configure three items:

• A custom report type that includes the shoe object and its fields
• A folder access that grants access to the sales manager and their team members to view and run reports in that folder
• A field level security that allows the sales manager and their team members to see all the fields on the shoe object Report subscription, while useful for scheduling and delivering reports, does not affect access to the report itself. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_create_report_type.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_manage_folders.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.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

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

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

A sales process is a set of stages that an opportunity goes through as it moves from creation to close. A record type is a way to offer different business processes, picklist values, and page layouts to different users based on their profiles. A page layout controls the layout and organization of detail and edit pages for a specific object and record type combination. To meet the requirement of having different fields and stages for each team, you need to create three sales processes for each market segment, three record types for each sales process, and three page layouts for each record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_salesprocess.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_layout.htm &type=5

Outbound message allows you to send information to an external system as part of a workflow rule or approval process. You can use outbound message to specify which fields to send and which endpoint URL to send them to.

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