Salesforce Salesforce-Certified-Administrator - Salesforce Certified Administrator (SU24)

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

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

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

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

To test the impact of a critical update before it is auto-activated, you should activate it in a sandbox first. This way, you can verify that your customizations and integrations work as expected without affecting your production org.

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

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_i mplementation_dashboards_and_reports/dashboards

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 typesfor each sales process, and three page layouts for each record type. References: https://help.salesforce.com/s/artic leView?id=sf.customize_salesprocess.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5https://help.salesforce.com/s/articl eView?id=sf.customize_layout.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 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

Flow Solutions are pre-built flows or templates that can be installed from AppExchange and customized to meet specificbusiness needs. For example, Flow Solutions can provide common use cases such as lead generation, document generation, payment processing, and more. In this case, the administrator can use a Flow Solution that provides a mortgage calculator and generates leads for loans. Flow Solutions are easy to install and configure, and can help save time and budget for projects. References:https://help.salesforce.com/s/articleVi ew?id=sf.flow_solutions.htm&type=5

Lightning pages are custom layouts that let you design pages for your Salesforce org using Lightning App Builder. You can assign different Lightning pagesfor different apps, record types, and profiles using Lightning page assignments. To meet the requirement of displaying different Lightning pages for Accounts in Sales Console and Service Console, you need to assign Lightning pages as app default for each app. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.lightn ing_page_assignments.htm&type=5