Explanation
Permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. By assigning a permission set that has View All on Leads to the contractor, Cloud Kicks can grant them view access to all lead records without modifying their profile or creating a new one. References:
https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5

Explanation
Run the standard Data Classification report is what the administrator should recommend to the compliance team. Data Classification is a feature that allows administrators to flag where sensitive information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data Classification also provides a standard report that shows field level sensitivity and classification for all fields in an org. The administrator can run this report and share it with the compliance team to meet their requirement.

Explanation
Use an Insert operation to load data because the data is not already in Salesforce and does not need to be updated or deleted3. Map an External ID data value to the object because External IDs are used to create relationships between records that are being imported and records that already exist in Salesforce4.
References: 3 https://help.salesforce.com/s/articleView?id=sf.data_loader_insert.htm&type=5 4
https://help.salesforce.com/s/articleView?id=sf.data_loader_relationships.htm&type=5

Explanation
Salesforce Authenticator is an app that allows users to verify their identity when logging in to Salesforce using two-factor authentication (2FA). 2FA adds an extra layer of security by requiring users to enter a verification code or approve a notification on their mobile device after entering their username and password.
To look at how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two ways:
A) Run a session setting report, specifying login methods by user.
A session setting report is a report that shows information about users' login sessions, such as login time, location, IP address, browser, platform, etc. A session setting report can also show the login methods used by users, such as password, verification code, or notification. By running a session setting report, specifying login methods by user, an administrator can see how many users have used Salesforce Authenticator to log in to Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_session.htm&type=5 C) Create a new view in Identity Verification History, specifying Method.
Identity Verification History is a page that shows the history of identity verification attempts for each user in the org. Identity verification history includes information such as date, time, status, method, and IP address of each attempt. By creating a new view in Identity Verification History, specifying Method as a filter criterion, an administrator can see how many users have used Salesforce Authenticator to verify their identity when logging in to Salesforce. References:
https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm&type=5

Explanation
Manual sharing is a way of granting access to individual records by manually sharing them with other users, roles, or groups. Manual sharing can override the organization-wide default and role hierarchy settings and give additional access to specific records. In this case, manual sharing could be the reason why only one user can see the account record, even though they have the same profile and role as another user who cannot see it.
References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_manual.htm&type=5