Free Practice Questions for Salesforce CRT-211 Exam

Person Account cannot be disabled is something that the administrator should consider before enabling Person Accounts. Person Accounts are a special type of accounts that allow storing information about individual people who are not associated with an organization or business account. Once Person Accounts are enabled, they cannot be disabled or removed from the org without contacting Salesforce support

A rich text component allows administrators to add custom text or images to a Lightning page. Conditional visibility allows administrators to control when a component is visible based on criteria such as field values or device type. By using these features, administrators can highlight Canadian customers as a potential challenge for fulfillment without modifying the page layout or creating a new record type. References: https://help.salesforce.com/articleView?id=sf.app_builder_components_rich_text.htm &type=5 https://help.salesforce.com/articleView?id=sf.app_builder_component_visibility.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 administrator should 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 they are selling to. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.products_ define.htm&type=5

To debug platform events in Apex code, you need to set a debug log on the Automated Process entity. This entity represents an automated process user that runs flows and processes in your org. By setting a debug log on this entity, you can capture the events that are published and consumed by your flow and Apex code, as well as any errors or exceptions that occur during the execution. References: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_debug.htm https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm &type=5

A row-level formula is a formula that evaluates each row in a report and returns a value based on one or more fields in that row. A row-level formula can be used to create a new column in a report that indicates whether the case subject contains the words ‘Alpha Shoe’ or not. References: https://help.salesforce.com/s/articleView?id=sf.reports_row_level_formulas.htm &type=5

Move some page components behind a tab, remove some of the fields displayed, and reduce the number of related lists displayed are three options available to the administrator to help with this issue. Moving some page components behind a tab can help reduce the loading time of a record page by hiding some components until they are needed by the user.

Field history tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. Field history tracking can help you audit data quality, compliance, or business processes. Field history tracking cannot be configured from Schema Builder, but it can be configured from Object Manager. In Object Manager, you can select an object and enable field history tracking from its settings page. Then, you can choose up to 20 fields per object to track and add the history related list to the page layout. References: https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.h tm&type=5 https://help.salesforce.com/s/articleView?id=sf.schema_builder_overview.htm &type=5

Flows deployed with change sets are inactive by default and need to be manually activated in the destination org before they can run. Deploying or redeploying a flow with change sets creates a new version of the flow in the destination org, which preserves the previous versions and allows for rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are automatically added to the change set when a flow is added

A permission set is a collection of settings and permissions that can extend users’ functional access without changing their profiles. By creating a permission set with view All on Accounts and assigning it to the service and sales managers, an administrator can grant them access to all account records in their org without modifying their existing profiles. References: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm &type=5