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/articleView?id=sf.reports_summary_charts.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm & type=5

The resume event is recalculated and the email goes out to the account owner immediately because the flow uses a scheduled path that evaluates the expiration date field every time it changes. When the expiration date is changed to yesterday, the flow resumes immediately and executes the action of sending the email

The Automated Case User is the default user for cases created via Email-to-Case. This user needs to have permissions to the new record type in order to assign it to the incoming cases. If the Automated Case User does not have the permissions, the cases will receive a different record type based on the organization-wide default settings. References: https://help.salesforce.com/s/articleView?id=sf.case_email_to_case.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.case_automated_user.htm & type=5

UESTION NO: 187

The administrator at Cloud Kicks recently replaced several case workflow rules with a single before save flow. Since this change, some cases are routing In unexpected ways.

What could be the cause or the charges to routing?

A. The old workflow rules are still active and impacting routing.

B. The flow precedes assignment rules; workflow rules are after assignment rules.

C. Assignment rules no longer reference the correct fields.

D. Multiple automation tools have been used and the automation is executed in a different order.

Answer: D

Multiple automation tools have been used and the automation is executed in a different order. This could cause some cases to route in unexpected ways, because the before save flow might override or conflict with the assignment rules or other automation tools that run after the record is saved. The administrator should review the order of execution and ensure that the flow logic is consistent with the other automation tools. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm & type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm

Validation rules and page layouts are two tools that can be used to require data to be entered in a field and improve data quality on a record in Salesforce. Validation rules are a way to enforce data quality and integrity by checking the values of fields before a record is saved and displaying an error message if the values do not meet the specified criteria. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Page layouts can also make fields required so that users must enter a value before saving a record.

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 two considerations 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 that currency 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

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.