Explanation
To show a component that shows LinkedIn data only to sales users when they are on their mobile phones, the administrator should filter the component visibility with two conditions:
User > Profile > name = sales User, which checks if the user's profile name is "sales User" Form Factor = phone, which checks if the user's device is a phone Filtering with view or role will not achieve the desired result. References:
https://help.salesforce.com/s/articleView?id=sf.app_builder_page_visibility_rules.htm&type=5

Explanation
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

Explanation
Themes are a way to customize the look andfeel 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 Lightningtheme only and cannot see custom themes.
References:https://help.salesforce.com/s/articleView?id=sf.themes_overview.htm&type=5

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