Free Salesforce CRT-211 Practice Exam with Questions & Answers

A Text Area (Rich) field allows users to format the text with fonts, colors, images, and hyperlinks. It also supports mapping to an opportunity when converting a lead. References:https://help.salesforce.com/s/articleView?id=sf.fields_using_rich_text_area.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 withinthat 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 isa 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.

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 accountsto 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 thejunction 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. References: 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 recordto 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. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

When a currency is added to an organization’s list of supported currencies, it cannot be deleted and once enabled, advanced currency management cannot be disabled are twoconsiderations that AW Computing should be aware of prior to implementing this change to the existing system. Adding a currency to an organization’s list of supported currencies is an irreversible action that allows users to enter and view amounts in thatcurrency for standard and custom objects that have currency fields. Enabling advanced currency management is also an irreversible action that allows administrators to define dated exchange rates for opportunities and opportunity products based on close dates or product dates instead of using static conversion rates

A permission set is a collection of settingsand permissions that give users access to various tools and functions in Salesforce. A permission set can be used to extend users’ functional access without changing their profiles. You can assign permission sets to individual users or groups of users based on their business needs. In this case, you can create a permission set with Read access to the Government ID field on the custom object and assign it to the Institutional Team users who need access to this field via reports. References: https://help.sale sforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5https://help.salesforce.com/s/articleView?id=sf.perm_sets_create.htm &type=5

Using a Get Record component allows the flow to dynamically retrieve records based on criteria or record IDs without hard coding them. This makes the flow more flexible and maintainable. Updating record elements outside the flow loop prevents unnecessary DML operations and reduces the risk of hitting governor limits.

Salesforce Authenticator is an app that adds an extra layer of security for logging into Salesforce by requiring users to verify their identity using their mobile device after entering their username and password on Salesforce login page. To see how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two methods:

• A) Create a new view In Identity Verification History, specifying Method.

Identity Verification History is a tool that shows information about each identity verification event for users in your org, such as the date and time, the verification method used, the IP address, and the status of the verification. By creating a new view in Identity Verification History and specifying the method as Salesforce Authenticator, an administrator can see how many users have used the app to verify their identity when logging in. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5

• D) Export Login History and filter based off of Authentication Method Reference.

Login History is a tool that shows information about each login attempt for users in your org, such as the date and time, the username, the source IP address, the login type, and the status of the login. By exporting Login History as a CSV file and filtering based on the Authentication Method Reference column, an administrator can see how many users have used Salesforce Authenticator as their authentication method when logging in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

A price book is a list of products and their prices that can be added to an opportunity. A product can have different prices for different markets or segments, and these prices are stored in different price books. In this case, the administratorshould create a new price book for the new retail pricing and add the products that are sold to retail locations for resale. This way, the users can select the appropriate price book and products for their opportunities based on the type of customer theyare selling to. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm &type=5https://help.salesforce.com/s/articleView?id=sf.products_ define.htm&type=5

Allow Forecasting is what the administrator should review to solve this issue. Allow Forecasting is a user permission that enables users to access and edit forecasts. If a user does not have this permission, they will not be able to see their own forecast or any forecasts below them in the role hierarchy. Therefore, the administrator should make sure that the sales rep has this permission enabled on their profile or permission set.

The setup audit trail tracks the recent setup changes that you and other administrators have made to your org. It can help you troubleshoot issues by showing you what changes were made, who made them, and when. In this case, the setup audit trail can help the administrator identify if someone changed the field-level security, page layout, or profile settings for the industry picklist field. References:https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5