Explanation
Escalation rules are rules that automatically escalate cases if they have not been resolved within a certain time frame or meet certain criteria such as priority or status. Escalation rules can perform actions such as changing ownership of cases, sending email notifications, or creating tasks for users or queues. By using escalation rules, AW Computing can ensure that cases are properly prioritized and handled within their SLA time limit.
Assignment rules are rules that automatically assign cases to users or queues based on criteria such as case origin, type, or product. Assignment rules can also send email notifications to users or customers when a case is assigned. By using assignment rules, AW Computing can ensure that cases are routed to the right agents or teams based on their skills and availability. References:
https://help.salesforce.com/s/articleView?id=sf.case_escalation_rules_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.customize_caseassign.htm&type=5

Explanation
When deploying profiles using change sets, the field-level security settings are not included unless the fields themselves are also part of the change set. Therefore, the administrator should consider adding the new custom fields to change set 2 along with the profiles, or manually adjust the field-level security after deployment.
References: https://help.salesforce.com/articleView?id=changesets_about_components.htm&type=5

Explanation
Process Builder and Flow Builder are tools that allow administrators to automate business processes in Salesforce without writing code. Process Builder and Flow Builder can perform actions such as creating records, updating fields, sending emails, posting to Chatter, invoking Apex classes, calling flows, etc.
To automate several updates to lead records and update unrelated records at Cloud Kicks, an administrator can use two options:
B) Create a Process Builder that runs when a record is changed
Process Builder is a tool that allows administrators to create processes that consist of criteria nodes and action groups. Criteria nodes define the conditions that trigger the process and action groups define the actions that the process performs. Processes can run when a record is created or when a record is created or edited.
By creating a Process Builder that runs when a record is changed, an administrator can automate updates to lead records based on certain criteria and perform actions such as updating fields, sending emails, posting to Chatter, invoking Apex classes, calling flows, etc. References:
https://help.salesforce.com/s/articleView?id=sf.process_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.process_considerations.htm&type=5 C) Create a flow that runs when a record is created or updated Flow Builder is a tool that allows administrators to create flows that consist of elements such as screens, assignments, decisions, loops, etc. Elements define the logic and user interface of the flow. Flows can run in different ways such as when a user clicks a button, when a record is updated by Process Builder, when an event occurs in the system (such as record creation), etc.

Explanation
Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than
100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records.
Bulk API is an API that allows fast and parallel processing of large batches of records. References:
https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5

Explanation
Two options that the administrator should use to meet these criteria are:
Share with roles and subordinates of the finance director role. This option allows you to grant access to records based on the role hierarchy of your org. You can share records with users who are in a specific role or in roles below that role in the hierarchy. In this case, you can share records with roles and subordinates of the finance director role, which includes all the members of the finance team.
Create a criteria-based sharing rule where the won field = true. This option allows you to grant access to records based on certain field values or formulas. You can create a criteria-based sharing rule on opportunities that grants access to records where the won field is true, which means that the opportunity stage is closed won.
The other two options are incorrect because:
Make an owner-based sharing rule where the won field = true is not an option because owner-based sharing rules do not allow you to specify field values or formulas as criteria. Owner-based sharing rules only allow you to share records based on who owns them or what role or group they belong to.
Select all opportunities owned by the sales manager role is not an option because it does not meet the criteria of sharing all closed won opportunities. It only shares opportunities that are owned by users who are in the sales manager role, regardless of their stage.
References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm&type=5