Free Practice Questions for Salesforce CRT-211 Exam

Product schedules allow users to track revenue or quantity over time for products in opportunities or orders by creating schedules manually or automatically based on predefined criteria such as start date, end date, frequency etc. However, product schedules have some limitations that administrators should consider before enabling this feature. One of these limitations is that line item schedules are unavailable in Process Builder and Workflow rules; only revenue schedules are available. References: https://help.salesforce. com/s/articleView?id=sf.products_schedules_def.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.products_schedules_considerations.htm &type=5

An after-save autolaunched flow is a type of flow that runs in the background when a record is saved and performs actions based on the record data or changes. An after-save autolaunched flow does not require user input or interaction and can be triggered by a record-triggered flow element or by an Apex trigger. In this case, you can create an after-save autolaunched flow that runs when a Project record is created and creates a standard set of related Project Milestone records based on predefined values or variables. References: https://help.salesforce. com/s/articleView?id=sf.flow_trigger_types.htm&type=5 https://help.sales

Before installing a managed package from the AppExchange, the administrator should take into consideration several factors, such as:

Custom objects and custom fields used by the app count against the org’s limits. The administrator should check how many custom objects and fields are available in their org and how many are used by the app.

Apps may require certain Salesforce editions or features to be enabled. The administrator should check the app’s requirements and compatibility with their org’s edition and features.

Apps may require external, third-party web services to function properly. The administrator should check if the app integrates with any external services and if they need to set up any authentication or configuration for them.

The other two options are incorrect because:

Managed apps do undergo a formal security review by Salesforce before they are listed on the AppExchange.

Apps can be installed in a sandbox before they are installed in production.

The error condition formula of a validation rule should return TRUE when the validation rule should fire and display an error message. In this case, the validation rule should fire when the Title field has the value of ‘CEO’ and the Phone field is blank. The formula Title = ‘CEO’ && ISBLANK(Phone) returns TRUE when both conditions are met, and FALSE otherwise. References: https://help.sales force.com/s/articleView?id=sf.fields_useful_field_validation_formulas.htm&type=5

Setup Audit Trail is a tool that tracks the recent setup changes made by anyone in an org. It can help identify who made what changes and when, as well as any errors or failures that occurred during the changes. Setup Audit Trail can help troubleshoot deployment issues by comparing the changes made in production with those made in sandbox

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by replacing it with fictitious data. This can help you protect your data privacy and comply with regulations while testing in a realistic environment. You can use the data masking tool to mask data for standard and custom objects, including person accounts, and choose from different masking formats and options. References: https://help.salesforce.com/s/ar ticleView?id=sf.data_mask.htm&type=5

Workflow is the debug log category that should be used to troubleshoot an issue with a flow. Workflow is a debug log category that captures information about workflow rules, flows, processes, approval processes, and entitlement processes. Workflow can help identify errors or issues related to these automation tools by showing details such as evaluation criteria, actions executed, variables assigned, and outcomes reached.

A summary report with a cross-filter is a type of report that allows you to summarize data by grouping rows and columns and applying filters based on related objects and fields. A cross-filter is a filter that lets you include or exclude records in your report based on related objects and their fields. In this case, you can create a summary report that includes a cross-filter to the Account object with a sub-filter for credit card number equal to null. This will show you all B2C accounts that are missing the credit card number, regardless of whether it is encrypted or not. References: https://help.salesforce.com/s/ar ticleView?id=sf.reports_summary_charts.htm&type=5 https://help.salesforce.com/s/articleView? id=sf.reports_cross_filters.htm&type=5

To make inventory data from a legacy application available in Salesforce, the administrator can create an external object that maps to the inventory application. An external object is similar to a custom object, except that it maps to data that’s stored outside your Salesforce organization. External objects enable users to view and report on external data in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.external _object_overview.htm&type=5

Run the standard Data Classification report is what the administrator should recommend to the compliance team. Data Classification is a feature that allows administrators to flag where sensitive information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data Classification also provides a standard report that shows field level sensitivity and classification for all fields in an org. The administrator can run this report and share it with the compliance team to meet their requirement.