Pass the Salesforce Advanced Administrator Advanced-Administrator Questions and answers with ValidTests

Escalation rules are rules that automatically escalate cases if they have not been resolved within a certain time frame or meet certain criteria such as priority or status. Escalation rules can perform actions such as changing ownership of cases, sending email notifications, or creating tasks for users or queues. By using escalation rules, AW Computing can ensure that cases are properly prioritized and handled within their SLA time limit.

Assignment rules are rules that automatically assign cases to users or queues based on criteria such as case origin, type, or product. Assignment rules can also send email notifications to users or customers when a case is assigned. By using assignment rules, AW Computing can ensure that cases are routed to the right agents or teams based on their skills and availability. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation_rules_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_caseassign.htm &type=5

The equivalent field is the field that matches the dashboard filter field on the source report object. For example, if the dashboard filter is on Account Owner, then the equivalent field on the Opportunity object is Opportunity Owner. Changing the equivalent field ensures that the dashboard filter applies correctly to the Opportunity components. References: https://help.salesforce.com/s/articleView?id=sf.dashboard_filters.htm &type=5

A rich text component allows administrators to add custom text or images to a Lightning page. Conditional visibility allows administrators to control when a component is visible based on criteria such as field values or device type. By using these features, administrators can highlight Canadian customers as a potential challenge for fulfillment without modifying the page layout or creating a new record type. References: https://help.salesforce.com/articleView?id=sf.app_builder_components_rich_text.htm &type=5 https://help.salesforce.com/articleView?id=sf.app_builder_component_visibility.htm &type=5

The Highlights Panel is a Lightning component that displays key information about a record at the top of the page. You can customize the Highlights Panel to show different actions based on the record type or other criteria. In this case, you can define dynamic action buttons for the Planet object that appear only if the gaseous field is true or false. This way, you can show different actions for different types of planets. References: https://help.salesforce.com/s/articleView?id=sf.lex_page_layouts_highlights_panel.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.dynamic_actions_considerations.htm &type=5

Workflow debug log category captures information about workflow rules, flows, processes, and actions that are executed as a result of a DML operation. References: 

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

The View Setup Audit Trail page lets you view the 20 most recent setup changes made to your org. You can also download a file of the last six months of setup changes. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_setup_audit_trail.htm &type=5

A validation rule can enforce data quality by preventing users from saving records that do not meet certain criteria. In this case, the validation rule can check if both the Sales Engineer and the Account Executive lookup fields are blank, and display an error message if so. This way, the director of sales can ensure that every opportunity has either a sales engineer or an account executive assigned to the deal. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm &type=5

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

Salesforce Authenticator is an app that adds an extra layer of security for logging into Salesforce by requiring users to verify their identity using their mobile device after entering their username and password on Salesforce login page. To see how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two methods:

A) Create a new view In Identity Verification History, specifying Method.

Identity Verification History is a tool that shows information about each identity verification event for users in your org, such as the date and time, the verification method used, the IP address, and the status of the verification. By creating a new view in Identity Verification History and specifying the method as Salesforce Authenticator, an administrator can see how many users have used the app to verify their identity when logging in. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5

D) Export Login History and filter based off of Authentication Method Reference.

Login History is a tool that shows information about each login attempt for users in your org, such as the date and time, the username, the source IP address, the login type, and the status of the login. By exporting Login History as a CSV file and filtering based on the Authentication Method Reference column, an administrator can see how many users have used Salesforce Authenticator as their authentication method when logging in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5