CRT-211 Practice Questions

A dashboard is a visual display of key metrics and trends for records in your org. Dashboards allow

users to quickly monitor performance and identify trends or issues at a glance. To make it easier for

users to see a dashboard they use frequently, administrators can add it to their home page using

Lightning App Builder. This way, users can see their dashboard every time they log in or go to their

home tab without having to navigate elsewhere. Reference:

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

https://help.salesforce.com/s/articleView?id=sf.dashboards_add_to_home_page.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

Creating a new quote record for each of the different product configurations and syncing the most

likely to be purchased back to the opportunity will ensure that their quotes and opportunities reflect

their sales. This way, sales reps can show customers different options and prices, and keep track of

which one is most likely to close. Syncing a quote with an opportunity will update the opportunity

amount, stage, and expected revenue fields based on the quote information. Reference:

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

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

A junction object is a custom object that has two master-detail relationships with two other objects.

A junction object allows administrators to create many-to-many relationships between objects, such

as relating multiple accounts to multiple regions.

To create a junction object called Account Region to link the standard Account object with a custom

object called Region, an administrator needs to do the following steps:

A) Make a master-detail relationship field on the junction object to the Region object.

A master-detail relationship field is a field that links a child record to a parent record. The child record

inherits the sharing and security settings of the parent record. By making a master-detail relationship

field on the junction object to the Region object, an administrator can link each Account Region

record to one Region record and make Region the first master of the junction object. Reference:

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

D) Configure a master-detail relationship field on the junction object to the Account object.

By configuring a master-detail relationship field on the junction object to the Account object, an

administrator can link each Account Region record to one Account record and make Account the

second master of the junction object. This allows administrators to relate multiple accounts to

multiple regions through the junction object. Reference:

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

The user profile permissions on the Opportunity object is the item that the administrator should

review to find out why the user is unable to delete the duplicate record. The user profile permissions

determine what users can do with records and objects in Salesforce, such as creating, editing,

deleting, viewing, or sharing. In this case, the administrator should check if the user has the Delete

permission on the Opportunity object, which allows them to delete opportunity records that they

own or have access to. If not, the administrator can either grant them this permission or delete the

record for them. Reference:

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

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

Data categories and visibility are features that allow you to organize and control access to your

Salesforce Knowledge articles based on different topics or criteria. Data categories are logical

groupings of articles that reflect your business needs and processes. You can create a data category

group and assign it to one or more article types, and then create data categories and subcategories

within that group. Data category visibility is a setting that determines which data categories users

can access based on their profiles or permission sets. You can use data categories and visibility to

provide relevant and appropriate product documentation to your customers and support team.

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

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

To create 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 have a storage limit of 1GB and

can be refreshed every day. Both sandboxes can include test data from production. Reference:

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

Confirm the object is marked as deployed and not in development is what the administrator should

do to resolve the issue. A custom object can be marked as deployed or in development depending on

its readiness for use. A custom object that is marked as in development is not visible to users or

available for data import or export. A custom object that is marked as deployed is visible to users and

available for data import or export. Therefore, the administrator should make sure that the new

custom object is marked as deployed before using Data Loader to upload records to it

Change sets are tools that allow administrators to move customizations such as fields, page layouts,

profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators

need to establish a deployment connection between a source org (such as a sandbox) and a target

org (such as production). Then, administrators can create an outbound change set in the source org

that contains the components they want to deploy, and upload it to the target org. In the target org,

administrators can view and validate the inbound change set before deploying it to their org.

Reference: https://help.salesforce.com/s/articleView?id=sf.changesets.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