Universal Containers has found duplicate contacts in Salesforce. The sales team administrator prevent duplicate records from being created.
Which two ways should the administrator customize duplicate management?
Choose 2 answers
Answer : B, C
Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.
B) Configure custom duplicate rules.
Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for contacts or other objects. Reference: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm&type=5
C) Create custom matching rules.
Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads. Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are detected for contacts or other objects. Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5
Cloud Kicks has created a new flow that deletes records.
What should the administrator consider when testing the flow?
Answer : B
Debugging a flow allows administrators to test how a flow behaves before activating it or making changes to it. Debugging a flow runs it in real time using test data provided by the administrator or default values from the flow. However, debugging a flow also performs any actions defined in the flow, such as creating, updating, or deleting records. Therefore, if a flow has a delete element that deletes a record based on certain criteria, debugging the flow will delete the test record even if the flow is inactive. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm&type=5
What should the administrator consider before enabling Person Accounts?
Answer : A
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
The Service team at Cloud Kicks needs a way to show the current status from the Account on the Case. This value should be on the page and is used in validation rules.
What should the administrator recommend to solve this?
Answer : A
A cross-object formula is a formula that references fields from related objects. The administrator can create a cross-object formula field on the Case object that displays the current status from the Account. This field can be used in validation rules and other processes. Reference: https://help.salesforce.com/s/articleView?id=sf.tips_on_building_formulas_cross_object_formulas.htm&type=5
The sales department has asked to limit access to the Amount field on the Opportunity to only tnose users. In the sales department and on the executtve team, Northern Trail Outfitters uses six custom profiles including Sales User. Marketing user, call Center user. Executive User Sales Manager user, ana call Center Manager user. Field level access is removed from three or the profiles In the sandbox.
What action should an administrator take to make sure this change is in production?
Answer : C
A change set is a tool that allows you to send customizations from one Salesforce org to another. A change set can contain components such as objects, fields, profiles, permission sets, workflows, and more. You can use change sets to migrate changes from a sandbox org to a production org or between two sandbox orgs that are affiliated with the same production org. In this case, you can deploy a change set from the sandbox to production that includes the Amount field and all the custom profiles that need access to it. This way, you can update the field-level security settings for the field on each profile in one deployment. Reference: https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_components_field.htm&type=5
An administrator at Universal Containers has been asked to configure product schedules.
What should the administrator consider before enabling this feature?
Answer : B
Product schedules are features that allow administrators to track revenue or quantity over time for products in opportunities or orders. Product schedules can be either revenue schedules or quantity schedules, depending on whether the product is sold by amount or by quantity. Product schedules can be either standard or customizable, depending on whether they use predefined settings or custom settings.
Line item schedules are records that represent each installment of revenue or quantity for a product over time. Line item schedules are created automatically when a product with a product schedule is added to an opportunity line item or an order product.
One limitation of product schedules is that line item schedules are unavailable in Process Builder and Workflow. This means that administrators cannot use these tools to automate actions based on line item schedules, such as sending email alerts, creating tasks, updating fields, or invoking flows. Reference: https://help.salesforce.com/s/articleView?id=sf.forecasts3_product_schedules.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.orders_line_item_schedules.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.product_schedule_considerations.htm&type=5
The administrator at AW Computing has been asked to review whether any users are making configuration changes directly in production.
Which item should the administrator review to find these details?
Answer : A
The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org's Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5