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

To help the finance team use Opportunity data to keep an eye on their pipeline without manually calculating anticipated income for the quarter, the administrator should set up collaborative forecasting. Collaborative forecasting allows users to view quota against open pipeline and make adjustments based on changing business conditions. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm &type=5

Salesforce Authenticator is an app that allows users to verify their identity when logging in to Salesforce using two-factor authentication (2FA). 2FA adds an extra layer of security by requiring users to enter a verification code or approve a notification on their mobile device after entering their username and password.

To look at how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two ways:

A) Run a session setting report, specifying login methods by user.

A session setting report is a report that shows information about users’ login sessions, such as login time, location, IP address, browser, platform, etc. A session setting report can also show the login methods used by users, such as password, verification code, or notification. By running a session setting report, specifying login methods by user, an administrator can see how many users have used Salesforce Authenticator to log in to Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_session.htm &type=5

C) Create a new view in Identity Verification History, specifying Method.

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

To resolve the issue with the Process Builder, the administrator should do the following steps:

Review the Error Email for the Process Builder and rectify the issues. The error email contains information about what caused the error and how to fix it.

Deactivate the Process Builder in production. This will prevent further errors from occurring while the administrator fixes the Process Builder.

Fix the Process Builder in a sandbox and migrate the change to production. This will ensure that the Process Builder is tested and validated before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.flow_troubleshoot_error_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_deploy.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

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

A record type allows administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating a record type for the type of property (single-family home or condo), DreamHouse Realty can assign different page layouts to each record type that display only relevant fields for each property type. The record type can also determine which sales process and path are available for each opportunity. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Force logout on session timeout is the recommended security setting to configure because it prevents users from resuming their sessions after they time out due to inactivity, which reduces the risk of unauthorized access to Salesforce data from unattended devices. References: https://help.salesforce.com/s/articleView?id=sf.security_sessions_logout.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