To ensure that sales reps’ managers can view records containing customer’s credit information but

their colleagues cannot, NTO should grant access using hierarchies via the sharing settings. This

option allows users above another user in the role hierarchy to have access to records owned by or

shared with users below them in the hierarchy. Reference:

https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5

Two practices that the administrator should adhere to in order to ensure a successful deployment to

production are:

Add permissions and access settings to outbound change sets in addition to the dependent

component list. This can help avoid deployment errors or access issues caused by missing

permissions or settings for the components in the change set. For example, if the change set includes

a new custom object, the administrator should also include the object permissions, field-level

security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This

can help test the change set for any errors or conflicts before deploying it to production. Deployment

validations simulate the deployment without actually making any changes and report any issues or

warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It

only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the

change set. It can be deployed along with other components as long as they are compatible and have

the required dependencies.

Reference: https://help.salesforce.com/s/articleView?id=sf.change_sets_components.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.change_sets_deploy.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.change_sets_validate.htm&type=5

Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will

build this functionality. A master-detail relationship creates a parent-child relationship between two

objects, where the child records inherit the sharing and security settings of their parent. A Roll-up

Summary field calculates values from related child records, such as count, sum, min, or max. In this

case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and

subtract it from the Invoice amount to get the current outstanding value. Reference:

https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5

This option will allow the administrator to change the recipient of the fault messages from the

consultant’s email to the system admin’s email without modifying any flows or processes. The other

options are either not feasible or not effective. Reference:

https://help.salesforce.com/articleView?id=flow_concepts_error_email.htm&type=5

The Show Unique Count option on the account name column will create a report showing all open

opportunities and the total number of accounts represented. This option will count each account

only once, even if it has multiple opportunities. The report can be grouped by account name or any

other field to show more details. Reference:

https://help.salesforce.com/s/articleView?id=sf.reports_builder_unique_count.htm&type=5

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. Reference:

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. Reference:

https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm&type=5

Another quote is already synced with the opportunity will prevent a user from syncing a quote with

an opportunity. Only one quote can be synced with an opportunity at a time. If a user tries to sync

another quote, they will get an error message saying that the opportunity already has a synced

quote. Reference: https://help.salesforce.com/s/articleView?id=sf.quotes_syncing.htm&type=5

A matching rule is a rule that defines how records are compared for duplication based on certain

fields or fuzzy logic. By including more fields or changing the matching method, you can make the

matching rule more or less strict and reduce false positives or negatives. In this case, including the

email field to the existing matching rule for contacts can help avoid duplicate messages for common

names by checking if the email addresses are also identical. Reference:

https://help.salesforce.com/s/articleView?id=sf.matching_rules_create.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.matching_rules_considerations.htm&type=5

Building a process that updates the record type field to B2C Customer after conversion will correct

this issue. The conversion layout for person accounts does not allow selecting different record types

for accounts and contacts. The default record type for person accounts is determined by the

organization-wide default settings. However, a process can be triggered after conversion to update

the record type field based on the lead record type or other criteria. Reference:

https://help.salesforce.com/s/articleView?id=sf.convert_leads_considerations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.convert_leads_mapping.htm&type=5

The sales manager and system administrator will be able to edit this new contact record because

they are either the owner or have Modify All Data permission respectively. Users above or below the

sales manager in the role hierarchy will not be able to edit this contact record because contacts are

controlled by parent and accounts are set to Public Read Only. All users in the organization will be

able to view but not edit this contact record because accounts are set to Public Read Only. Reference:

https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5