Soles reps at AW Computing hove asked the Administrator to help them close deals faster on the Salesforce mobile app when they're in the new. They want to be able to quickly close an opportunity and have key fields, like status, pre populated to Closed Won.What should an administrator create to achieve this?
Answer(s): A
An object-specific quick action is a type of action that allows users to do something in the context of a specific object, such as creating or updating a record, logging a call, sending an email, or launching a custom action. In this case, the administrator can create an object-specific quick action on the opportunity object that pre-populates certain fields with predefined values and allows users to quickly close an opportunity from the Salesforce mobile app.
https://help.salesforce.com/s/articleView?id=sf.actions_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.actions_objectspecific_actions.htm&type=5
Sales reps at AW Computing hove been reporting that contact phone numbers sometimes revert book to on old value after being updated.What should the administrator do to resolve this issue?
Answer(s): D
One possible cause of unexpected changes to record values is having multiple automation tools that update the same field on the same object. This can create conflicts and overwrite each other's values. To resolve this issue, the administrator should consolidate automation tools and use only one tool per object and field combination. This can help avoid confusion and ensure consistent results.
https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm&type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/automa tion_considerations
AW Computers has enabled the feature for Contact to multiple Accounts. A rep is trying to remove the primary Account from a Contact but Is unable to do so. The administrator has already updated the page layout to no longer require an Account.What could be the issue?
When the feature for Contacts to multiple Accounts is enabled, a Contact can have a direct relationship with multiple Accounts. However, one of these relationships must be designated as the primary Account relationship. This relationship is required on a Contact regardless of the page layout settings and cannot be removed unless the Contact is deleted or merged with another Contact.
https://help.salesforce.com/s/articleView?id=sf.shared_contacts_set_up.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.shared_contacts_considerations.htm&type=5
An administrator created two record types on the Account object: Internal Customers and External Customers. A custom profile called Sales has the External Customers record type assigned. The sharing rules for Accounts arm set to Public Read Only. On occasion. Sales users notice that an Account record has the wrong record type assigned. The administrator has created a screen flow that will change the record type on the user's behalf.What will happen to the Sales user's record access after running this flow?
Answer(s): C
Changing the record type of a record does not affect the record access of a user. Record access is determined by the organization-wide default, role hierarchy, sharing rules, manual sharing, teams, and ownership. Record type only affects the page layout and picklist values that are available for the record. Therefore, if a user has access to a record before changing its record type, they will still have the same access after changing its record type.
https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&type=5
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?
Answer(s): B
One possible reason for the changes to case routing is the difference in the order of execution between before save flow triggers and workflow rules. Before save flow triggers run before assignment rules, which means that any field updates made by the flow can affect how the assignment rules assign the case. Workflow rules run after assignment rules, which means that any field updates made by the workflow do not affect how the assignment rules assign the case. Therefore, replacing workflow rules with before save flow triggers can change the case routing logic.
https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.order_of_execution.htm&type=5
Post your Comments and Discuss Salesforce Certified Platform Administrator II exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Certified Platform Administrator II content, but please register or login to continue.