Advanced-Administrator Exam Dumps : Salesforce Certified Platform Administrators II (Plat-Admn-301)

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: &type=5 &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: &type=5

Identity Verification History stores up to 20,000 records of users’ identity verification attempts for various features that require MFA, such as logging in from an unknown browser or device, resetting a password, or changing personal information. The data is stored for up to 6 months and then deleted automatically. Therefore, if a user has been inactive for more than 6 months or if there are more than 20,000 records in total, their data may be missing from Identity Verification History. References: &type=5

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. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data. References: &type=5