Ursa Major Solar's administrator has configured multiple record-triggered flows to run before or after the record is saved on the Account object.
What should the administrator consider when a record-triggered flow executes first?
Answer : D
The order in which record-triggered flows are executed is not guaranteed. If there are multiple record-triggered flows on the same object and trigger type, Salesforce does not guarantee which one runs first. Therefore, the administrator should consider this when designing record-triggered flows that depend on each other's outcomes. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm&type=5
Users at AW Computing are receiving a duplicate message when they enter contacts with common first and last names. Management wants to improve the user experience but also keep the data Integrity of contacts.
What should an administrator implement for this issue?
Answer : C
A matching rule is a rule that defines how records are compared for duplication based on certain fields or fuzzy logic. By including more fields or changing the matching method, you can make the matching rule more or less strict and reduce false positives or negatives. In this case, including the email field to the existing matching rule for contacts can help avoid duplicate messages for common names by checking if the email addresses are also identical. Reference: https://help.salesforce.com/s/articleView?id=sf.matching_rules_create.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.matching_rules_considerations.htm&type=5
Cloud Kicks has a Process Builder which should trigger upon a status change from on approval process. The Process Builder triggers if the status is updated manually, but not as a result or the approval process update.
What could the administrator do to troubleshoot the issue?
Answer : B
Check the Reevaluate Workflow Rules After Field Change box on the Approval Process Field Update Action is what the administrator should do to troubleshoot the issue. This option allows the approval process field update to trigger any workflow rules or processes that are based on the updated field value. If this option is not checked, the approval process field update will not trigger any workflow rules or processes, and the Process Builder will not fire
AW Computing (AVVC) has customers In multiple countries. AWC would li Which two considerations should AWC be aware or prior to implementing this change to the existing system? Choose 2 answers
Answer : A, D
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
Cloud Kicks (CK) completed a project in a sandbox environment and wants to migrate the changes to production. CK split the deployment into two distinct change sets. Change set 1 has new custom objects and fields. Change set 2 has updated profiles and automation.
What should the administrator consider before deploying the change sets?
Answer : A
When deploying profiles using change sets, the field-level security settings are not included unless the fields themselves are also part of the change set. Therefore, the administrator should consider adding the new custom fields to change set 2 along with the profiles, or manually adjust the field-level security after deployment. Reference: https://help.salesforce.com/articleView?id=changesets_about_components.htm&type=5
Cloud Kicks (CK) has a backup team of employees that helps short-staffed departments. These users could be working with sales one day and service the next. CK is implementing new Lightning record pages for each department so that they view records In a way that makes sense for each department.
How should the administrator ensure this Is configured correctly?
Answer : A
Configure one app per department and activate record pages for each app is how the administrator should ensure this is configured correctly. An app is a collection of items that work together to serve a particular function for a group of users. An app can include items such as tabs, objects, reports, dashboards, and record pages. A record page is a type of Lightning page that displays details about a specific record. A record page can be customized using Lightning App Builder and activated for different apps, profiles, or record types. By configuring one app per department and activating record pages for each app, the administrator can ensure that the backup team users can view records in a way that makes sense for each department depending on which app they are using.
A user accidentally created a duplicate opportunity and is unable to delete the duplicate record.
What should an administrator do to troubleshoot this issue?
Answer : B
The user profile permissions on the Opportunity object is the item that the administrator should review to find out why the user is unable to delete the duplicate record. The user profile permissions determine what users can do with records and objects in Salesforce, such as creating, editing, deleting, viewing, or sharing. In this case, the administrator should check if the user has the Delete permission on the Opportunity object, which allows them to delete opportunity records that they own or have access to. If not, the administrator can either grant them this permission or delete the record for them. Reference: https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_object_permissions.htm&type=5