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

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

To track all cases that reference the new product and give read/write access to the product's two lead engineers, the administrator should create a queue and a criteria-based sharing rule. The queue will allow assigning cases that meet certain criteria, such as having a specific value in the Product field, to a group of users. The criteria-based sharing rule will grant read/write access to the queue members for cases that match the same criteria. Reference: https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_criteria.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. Reference: https://help.salesforce.com/s/articleView?id=sf.path_key_fields.htm&type=5