The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to tra ck configuration changes directly in production and identify any unauthorized or problematic changes. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit T rail to see when a user’s profile has been changed and who changed the data. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm & type=5

Time-based workflows are a type of workflow that execute actions based on a specific time trigger, such as a certain number of days before or after a date field on a record. Time-based workflows can cause delays in processing because they are added to a queue and processed in one-hour batches. If the queue is large or the system is busy, the actions may not execute at the exac t time they are scheduled. Therefore, time-based workflows can contribute to reaching the hourly limit for processing workflow time triggers. References: https://help.salesforce.com/s/articleView?id=sf.workflow_time_action_considerations.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_limits.htm & type=5

An object-specific quick action is a type of action that allows users to do something in the context of a specific object, such as creating or updating a record, logging a call, sending an email , or launching a custom action. In this case, the administrator can create an object-specific quick action on the opportunity object that pre-populates certain fields with predefined values and allows users to quickly close an opportunity from the Salesfor ce mobile app. References: https://help.salesforce.com/s/articleView?id=sf.actions_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=s f.actions_objectspecific_actions.htm & type=5

To cre ate a training sandbox with 160MB of test data that needs to be refreshed every other day, NTO should use either Partial or Developer Pro sandboxes. Partial sandboxes have a storage limit of 10GB and can be refreshed every 5 days. Developer Pro sandboxes h ave a storage limit of 1GB and can be refreshed every day. Both sandboxes can include test data from production. References: https://help.salesforce.com/s /articleView?id=sf.data_sandbox_environments.htm & type=5

Go into the user record and freeze the user is the action that should be taken to ensure the user’s access is immediately revoked. Freezing a user is a way to temporarily prevent a user from logging in to Salesforce without deactivating their user record or changing their profile. Freezing a user can be useful when an employee has resigned or left the company and their access needs to be removed immediately. Freezing a user does not affect the ownership of records or email alerts that are assigned to them

Delegated administration allows administrators to delegate certain user management tasks to other users without granting them full administrative privileges. Delegated administrators can create and manage users only within specified roles or public groups. This option will meet the requirement of allowing each division to create and manage users only within their division. References: https://help.salesforce.com/articleView?id=delegated_administration_overview.htm & type=5

Identity verification history and login history are two areas that the administrator can review to understand potential root causes of mul ti-factor authentication issues. Identity verification history shows the methods and results of identity verification attempts for a user, such as email verification, SMS verification, or app verification. Login history shows the status, source, and locati on of login attempts for a user, as well as any login errors or challenges that occurred. These two areas can help the administrator identify if the user entered the correct verification code, if the user’s device or app is compatible with multi-factor aut hentication, or if there are any network or security issues that prevent successful verification. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm & type=5

The Campaign Member option is only available for Update when using Data Import Wizard. This means that you can use Data Import Wizard to update existing campaign members with new or modified information, but you cannot use it to create new campaign members from a spreadsheet. To create new campaign members from a spreadsheet, you need to use other tool s such as Data Loader, Import Wizard for Leads and Contacts, or Manage Members button on the campaign page. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_members_adding_parent.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.data_importer.htm & type=5

To add a user to an opportunity team, you need Edit access on the account associated with the opportunity and either own the opportunity or be above the owner in the role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.teams_adding.htm & type=5

The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page. References: https://help.salesforce.com/s/articleView?id=sf.customize_layouts.htm & type=5