Free CRT-211 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

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

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

A lookup relationship is a type of field that links one object to another object. It allows you to access

related data from another object and display it on a record page. A lookup relationship can be used

to link the custom object that stores financial information to the Account object, so that only finance

team members can see the related financial information about the account. Reference:

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

A joined report is a type of report that allows you to create multiple report blocks that provide

different views of your data. Each report block can have its own fields, columns, sorting, and filtering.

A joined report can only be created from summary or matrix reports. You can use a joined report to

show data from different report types or data sources on a single report. In this case, you can use a

joined report to show Accounts with Open Cases by creating two report blocks: one for accounts and

one for cases with a filter for open status. You can then join the two blocks by a common field such as

Account ID or Account Name. Reference:

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

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

Three reasons CK should utilize Data Categories when creating articles in Knowledge are:

Data Categories help organize the Knowledge base content displayed. 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 categories help you organize your articles by topic or criteria and make them

easier to find and browse by your users or customers.

Data Categories provide a way to secure access to the Knowledge base content. 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 category visibility to control access to your articles based on their

data categories and ensure that only relevant and appropriate content is displayed to different users

or customers.

A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a

document that provides information or answers to common questions or issues. A Knowledge article

can be tagged to one or more data categories within each data category group that is assigned to its

article type. This allows you to classify your articles by multiple criteria and make them searchable

and accessible by different users or customers.

One possible reason why the before trigger fails is that the code could be trying to create duplicates

in the archive when it is unable to. A before trigger is a type of trigger that executes before a record

is saved and can be used to validate or modify record data. In this case, the before trigger is

supposed to save the original version of a record to an external database before it is updated or

deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try

to create duplicate records in the external database when it is not allowed or possible. This could

cause the trigger to fail and prevent the record from being saved in Salesforce. Reference:

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm

https://developer.salesforce.com/docs/atlas.enus.apexcode.meta/apexcode/apex_triggers_context_variables.htm

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

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

The flow debug option is a tool that allows you to test and troubleshoot your flow by running it in

debug mode and inspecting the values of variables and resources at each step. You can also set the

debug mode to run as another user and see how the flow behaves for different users with different

permissions and settings. In this case, using the flow debug option and setting the selection to run as

another user can help identify why one user is experiencing a flow error while others are not.

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

Shield Platform Encryption is a Salesforce feature that allows you to encrypt sensitive data at rest

while preserving critical platform functionality. It uses a combination of tenant secrets, encryption

keys, and masking policies to protect your data. A field encryption policy is a set of rules that defines

which fields are encrypted and how they are masked when displayed. A field encryption policy can

be used to encrypt and mask the identification number field, except for the last two digits.

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

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

The change can be made through the desktop site by using the Edit All button on the related list of

products on the opportunity page. This button allows you to edit multiple products at once and

change their price book entries. You cannot use this button on the mobile app, as it is not supported.

You also cannot change the price book on the opportunity once it has products added to it, unless

you remove all the products first. Reference:

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

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

=5

A lookup relationship with Read/Write sharing setting is the recommended option to use when

adding a field to Case Outcome custom object. A lookup relationship is a type of relationship that

links two objects together and allows users to associate one record with another. A lookup

relationship does not affect the security or deletion of either record and can be optional or required.

In this case, you can create a lookup relationship field on Case Outcome object that

Case

object and allows users to link multiple Case records to multiple Case Outcome records. You can also

set the sharing setting for the lookup field to Read/Write, which means that users who have access to

the parent record can also access and edit the child record. Reference:

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

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

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