Plat-Admn-301 Sample Questions Answers

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

The Show Unique Count option on the account name column will create a report showing all open opportunities and the total number of accounts represented. This option will count each account only once, even if it has multiple opportunities. The report can be grouped by account name or any other field to show more details. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_unique_count.htm &type=5

Email logs provide information about email delivery, such as the sender, recipient, date and time, delivery status, and any error messages. The administrator can use email logs to troubleshoot why users are missing expected email alerts and identify which emails are hitting the daily limit. References: https://help.salesforce.com/articleView?id=email_logs.htm &type=5

 To make sure that the changes are in production, you need to add the components to an outbound change set and deploy it to production. A change set is a tool that allows you to send customizations from one Salesforce org to another. A change set can contain components such as objects, fields, profiles, permission sets, workflows, and more. You can use change sets to migrate changes from a sandbox org to a production org or between two sandbox orgs that are affiliated with the same production org. In this case, you need to add the master-detail field and all the affected profiles to an outbound change set in your sandbox org and then deploy it to your production org. References: https://help.salesforce.com/s/articleView?id=sf.changesets.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_components_field.htm &type=5

Go into the user record and freeze the user is the action that should be taken to ensure the user’s access is immediately revoked. Freezing a user is a way to temporarily prevent a user from logging in to Salesforce without deactivating their user record or changing their profile. Freezing a user can be useful when an employee has resigned or left the company and their access needs to be removed immediately. Freezing a user does not affect the ownership of records or email alerts that are assigned to them

 Record-triggered flow is a feature that allows administrators to automate actions that occur when a record is created or updated. Record-triggered flow can perform actions such as updating fields, creating records, sending emails, or invoking Apex code. Record-triggered flow can be used to update the account checkbox field ‘Opportunity Created’ when at least one related opportunity has been created

Dynamic actions are a way to conditionally display actions on a record page based on criteria such as field values, user profile, device type, or record type. Dynamic actions can help streamline the user interface and guide users to take the right actions at the right time. Dynamic actions can be used to show or hide the Create Contract button based on the opportunity stage value

One of the IDs in the batch referenced a record that was in the recycle bin because deleting records with Bulk API does not delete records permanently but moves them to the recycle bin. Therefore, if a record ID in the batch matches an existing record ID in the recycle bin, an ‘entity is deleted’ error will occur.

A permission set is a collection of settings and permissions that can extend users’ functional access without changing their profiles. By creating a permission set with view All on Accounts and assigning it to the service and sales managers, an administrator can grant them access to all account records in their org without modifying their existing profiles. References: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm &type=5

The Data Import Wizard is a tool that allows you to import data for standard and custom objects, including person accounts, into Salesforce. You can access it from the Setup menu and use it to import up to 50,000 records at a time. You can also use it to update, upsert, or delete existing records. The Data Import Wizard can help you match your data with Salesforce fields, prevent duplicates, and run import jobs in the background. References: https://help.salesforce.com/s/articleView?id=sf.data_importer.htm &type=5

Login Forensics is a Salesforce feature that allows you to monitor and analyze login behavior and trends in your org. It can help you identify and prevent brute-force password attacks by showing you the number of login attempts, successes, and failures per user, location, and device. You can also set up alerts to notify you when a user exceeds a certain number of login failures or when a login originates from an unusual location or device. References: https://help.salesforce.com/s/articleView?id=sf.security_loginforensics.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_loginforensics_alerts.htm &type=5

A sandbox is a copy of a production org that can be used for development, testing, or training purposes. Sandboxes allow administrators to make changes and test them without affecting the live production org. A shared sandbox is a type of sandbox that can be used by multiple users or teams to collaborate on development or testing projects. By testing changes in a shared sandbox, the AW Computing administrator team can avoid conflicts and errors when deploying changes to production. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm &type=5

Account teams are groups of users who work together on an account. Administrators can enable account teams and grant team members different levels of access to accounts and related records such as contacts, opportunities, and cases. By using account teams, Cloud Kicks can grant engineers access to the necessary accounts when they need assistance from them, while maintaining data security for other accounts that they do not need to access. References: https://help.salesforce.com/s/articleView?id=sf.accountteam.htm &type=5

A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. A roll-up summary field can be used to count, sum, min, or max values from child records. You can create a roll-up summary field on an object that has a master-detail relationship with another object. In this case, you can create a roll-up summary field on Room that counts the number of Equipment records related to it. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_types.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

Query and export the Account History object using Data Loader is how the administrator can acquire the field history data for analysis. Data Loader is a tool that allows administrators to import, export, insert, update, delete, or upsert records in Salesforce using CSV files. Data Loader can handle large data sets and complex data transformations. Data Loader can be used to query and export the Account History object, which stores the field history data for accounts, using SOQL statements. 

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. References: 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

When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible. References: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.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.

Use a custom permission set that is assigned to the user because custom permissions are a way to grant access to custom processes or functionality based on user profiles or permission sets. Custom permissions can be referenced by Apex code, validation rules, flows, or other logic to control whether a process should run for a user or not. Custom permissions can be used to declaratively control process execution by assigning them to users or profiles.

Giving the account owner Read access to both the Account and the Quota objects will give access to all Item records. Since Item is a junction object between Account and Quota, users need to have at least Read access to both parent objects to see Item records. If users have access to only one parent object, they will not be able to see Item records related to the other parent object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

The Security Health Check tool in Salesforce provides a detailed overview of an organization’s security posture, which includes information on how objects are shared externally. This tool is particularly useful for administrators who need to review and assess various security configurations, including the visibility of objects to external users.

Security Health Check:

This tool helps administrators quickly identify and manage risks related to security settings, including those pertaining to data sharing externally.

By using Health Check, administrators can access a report that shows the sharing settings of objects, allowing them to confirm if any objects have been shared as "Public" externally, which is crucial during an audit.

It provides insights into high-risk settings and areas where the configuration does not align with Salesforce security best practices, such as public access levels.

Use Case:

For an audit focused on understanding external access to objects, Security Health Check is the most appropriate choice because it gives a quick snapshot of how data sharing settings compare against Salesforce's recommended security baseline.

This can help AW Computing immediately identify which objects have broader public access than desired, addressing potential security vulnerabilities.

Incorrect options:

Setup Audit Trail: This tool tracks configuration changes within Salesforce over time, but it does not provide specific details about data sharing settings or external visibility of objects.

Session Security Settings: These settings control session policies and timeouts but are not related to object sharing or external visibility.

Object Manager: While Object Manager allows administrators to configure object-specific settings, it does not provide an overall view or quick audit of external sharing configurations.

Case Source updates to ‘email’ before the record is saved because the Process Builder runs before the auto-response rule. Then, an email is sent out using Template2 because the auto-response rule evaluates the Case Source value after it is updated by the Process Builder and matches the criteria for Template2

The Campaign Member option is only available for Update when using Data Import Wizard. This means that you can use Data Import Wizard to update existing campaign members with new or modified information, but you cannot use it to create new campaign members from a spreadsheet. To create new campaign members from a spreadsheet, you need to use other tools such as Data Loader, Import Wizard for Leads and Contacts, or Manage Members button on the campaign page. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_members_adding_parent.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_importer.htm &type=5

An after-save autolaunched flow is a type of flow that runs in the background when a record is saved and performs actions based on the record data or changes. An after-save autolaunched flow does not require user input or interaction and can be triggered by a record-triggered flow element or by an Apex trigger. In this case, you can create an after-save autolaunched flow that runs when a Project record is created and creates a standard set of related Project Milestone records based on predefined values or variables. References: https://help.salesforce.com/s/articleView?id=sf.flow_trigger_types.htm &type=5 https://help.sales

The Fields component is a Lightning component that allows administrators to display fields from a record on a Lightning page based on certain conditions or criteria. For example, administrators can use filter logic to show or hide fields based on field values or user profiles. In this case, the administrator can use the Fields component to display fields that only apply to condos based on the value of a field that indicates the type of property. References: https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_fields.htm &type=5

Lightning Object Creator is a tool that allows you to create custom objects and fields from a spreadsheet in a few clicks. Lightning Object Creator analyzes the spreadsheet data and suggests the best way to map it to Salesforce fields and relationships. You can also import the data from the spreadsheet into the new custom object and view it in a list view or a related list. In this case, you can use Lightning Object Creator to create a custom Project object from the spreadsheet that tracks installations and also import the data into the new object. References: https://help.salesforce.com/s/articleView?id=sf.object_creator_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.object_creator_create_object.htm &type=5

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

VisualStudio Code is a recommended tool to make the change in the displayed text in one of the Lightning web components. VisualStudio Code is an integrated development environment (IDE) that supports Salesforce development tools such as Salesforce Extensions for Visual Studio Code, Salesforce CLI, and Lightning Web Components. You can use VisualStudio Code to create, edit, debug, and deploy Lightning web components and other Salesforce metadata. To make the change in the displayed text, you need to open the HTML file of the Lightning web component in VisualStudio Code and modify the text element accordingly. References: https://developer.salesforce.com/tools/vscode https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components

Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will build this functionality. A master-detail relationship creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent. A Roll-up Summary field calculates values from related child records, such as count, sum, min, or max. In this case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and subtract it from the Invoice amount to get the current outstanding value. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

Two reasons why the user cannot find the Location object while using Data Loader are:

The label of Location may have been changed. The label of an object is the name that is displayed in the user interface and can be different from the API name that is used by Data Loader and other tools. If the label of Location has been changed to something else, such as Site or Venue, then the user may not be able to find it by searching for Location in Data Loader. The user should check the API name of the object in Object Manager or use the Describe Global operation in Data Loader to see all available objects and their labels.

The user’s profile needs create access to Location. The user’s profile determines what objects and fields they can access and what actions they can perform on them, such as creating, reading, updating, or deleting records. If the user’s profile does not have create access to Location, then they will not be able to load records into that object using Data Loader. The user should check their profile permissions in Setup or ask their administrator to grant them create access to Location.

The other two options are incorrect because:

Data Loader should only be used with standard objects is not a reason because Data Loader can be used with both standard and custom objects, as long as they are accessible and queryable via the API.

Location has a master-detail field to Account is not a reason because having a master-detail field does not prevent an object from being available in Data Loader, as long as it meets the other requirements such as accessibility and queryability.

Move any Potential Name records with blank lookup fields to the recycle bin or assign any Potential Name records with blank lookup fields to an existing record from Product Development are two options available for altering the existing Potential Name records for the deployment of this change to be successful. Changing a lookup relationship to a master-detail relationship requires that all child records have a parent record. Therefore, any Potential Name records that have blank lookup fields to Product Development need to be either deleted or assigned to a valid Product Development record before changing the relationship type

 Omni-Channel is a feature that allows service reps to receive work assignments based on their availability, capacity, and skills. It also allows administrators to define routing rules and priorities for different types of work items, such as cases, chats, or leads. Omni-Channel can help reduce the wait time for customers and improve the efficiency of service reps.

To review the performance of a Lightning record page, administrators can utilize two key tools:

Lightning Usage App:

The Lightning Usage App provides insights into user engagement and performance metrics for Lightning Experience.

Within this app, administrators can view specific metrics related to page load times and other performance factors.

This is a helpful resource for tracking usage and identifying potential issues with page speed or performance across the org.

Analyze Button:

The Analyze button is available within the Lightning App Builder when editing a Lightning record page.

By clicking this button, administrators can run a performance analysis on the page layout, which provides specific recommendations for optimizing page load times and improving overall user experience.

The tool evaluates components, their configuration, and potential sources of delay, giving direct feedback on areas to improve.

These two options directly provide performance analysis capabilities for Lightning record pages. The other options listed do not offer direct access to page performance metrics:

Activation Button is used for setting page visibility rules and activating a page, not for performance analysis.

Pages Menu helps in navigating and managing pages but does not provide performance metrics.

Using both the Lightning Usage App and the Analyze button allows administrators to comprehensively review and optimize Lightning page performance for improved user experience.

Chat must be routed with Omni-Channel in Lightning Experience because Omni-Channel is the only way to route chats to agents in Lightning Experience1. Chat can only be added to Console navigation Lightning apps because Chat is a console app feature and requires a console app with a console navigation style2. References: 1 https://help.salesforce.com/s/articleView?id=sf.live_agent_chat_omnichannel.htm &type=5 2 https://help.salesforce.com/s/articleView?id=sf.live_agent_chat_app.htm &type=5

While the Schema Builder is a powerful tool in Salesforce for visually creating and managing custom objects and fields, there are certain configurations that must be done in Object Manager rather than Schema Builder. One of these configurations is enabling field history tracking.

Field History Tracking:

Field history tracking cannot be configured directly within Schema Builder. This setting must be enabled from within the Object Manager, where administrators can specify which fields on an object should have their changes tracked.

Enabling field history tracking involves navigating to the object in Object Manager, accessing the field history tracking settings, and selecting specific fields to track.

Limitations of Schema Builder:

Schema Builder is useful for quickly creating custom objects, relationships, and fields, but it does not support all configurations, such as enabling field history tracking, defining object-level permissions, or setting advanced object configurations.

For these types of configurations, administrators need to return to Object Manager where these settings are available.

Incorrect options:

Add custom fields to the page layout: This task is typically done within Object Manager, but Schema Builder does allow customization of page layouts to a certain extent through drag-and-drop.

Make available for Customer Portal: Schema Builder does not control portal availability; however, this is managed through Object Manager settings related to record visibility for portal users.

Allow Reports and Activities: This setting can be configured in Schema Builder when initially creating an object, but further refinements and permission settings must often be done in Object Manager.

In conclusion, enabling field history tracking requires access to the Object Manager, as it cannot be configured through Schema Builder.

Bucket field is a feature that allows administrators to group report values into categories without changing the data in Salesforce. Bucket field can help simplify reports and charts by reducing the number of values displayed and summarizing data based on criteria such as ranges or groups. Bucket field can be used to group specific picklist values together into one of two lists

Sharing rules are automatic exceptions to organization-wide sharing settings that grant additional access to records based on record ownership or criteria. By creating a sharing rule on the Account object for all members of the account services role to have Read/Write access, the administrator can allow users in that role to edit and change ownership of Accounts owned by any of their team members, regardless of the organization-wide sharing setting for Account. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.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

Confirm the object is marked as deployed and not in development is what the administrator should do to resolve the issue. A custom object can be marked as deployed or in development depending on its readiness for use. A custom object that is marked as in development is not visible to users or available for data import or export. A custom object that is marked as deployed is visible to users and available for data import or export. Therefore, the administrator should make sure that the new custom object is marked as deployed before using Data Loader to upload records to it

Entitlement templates are a way to automatically create and associate entitlements with products or service contracts. They can help simplify the management of entitlements and ensure that customers receive the correct level of service. Entitlement templates can also be used to define service levels, milestones, and entitlement processes for different types of products or service contracts.

Data Categories are a way to organize and classify knowledge articles into a hierarchical structure based on topics or criteria. Data Categories can help service reps quickly narrow down the number of articles by filtering or browsing by category. Data Categories can also be used to control the visibility and access of articles for different users or roles.

A junction object is a custom object that has two master-detail relationships with two other objects. A junction object allows administrators to create many-to-many relationships between objects, such as relating multiple accounts to multiple regions.

To create a junction object called Account Region to link the standard Account object with a custom object called Region, an administrator needs to do the following steps:

A) Make a master-detail relationship field on the junction object to the Region object.

A master-detail relationship field is a field that links a child record to a parent record. The child record inherits the sharing and security settings of the parent record. By making a master-detail relationship field on the junction object to the Region object, an administrator can link each Account Region record to one Region record and make Region the first master of the junction object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

D) Configure a master-detail relationship field on the junction object to the Account object.

By configuring a master-detail relationship field on the junction object to the Account object, an administrator can link each Account Region record to one Account record and make Account the second master of the junction object. This allows administrators to relate multiple accounts to multiple regions through the junction object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

A managed package is a type of app that can be installed from the AppExchange. Managed packages are typically created by ISV partners or developers who want to distribute and sell applications that are upgradeable and have intellectual property protection. Before installing a managed package, an administrator should consider the following:

A) Custom objects and custom fields used by the app count against the org’s limits.

Managed packages may include custom objects and custom fields that are used by the app. These custom objects and custom fields count against the org’s limits and may affect the performance or functionality of the org. Administrators should review the components and requirements of the app before installing it and make sure they have enough space and resources for the app. References: https://help.salesforce.com/s/articleView?id=sf.packaging_limits.htm &type=5

C) Apps may require certain Salesforce editions or features to be enabled.

Managed packages may require certain Salesforce editions or features to be enabled in order to work properly. For example, some apps may require Lightning Experience, API access, custom permissions, or specific user licenses. Administrators should check the app’s description and documentation before installing it and make sure they meet the prerequisites for the app. References: https://help.salesforce.com/s/articleView?id=sf.packaging_install.htm &type=5

D) Apps may require external, third-party web services to function properly.

Managed packages may require external, third-party web services to function properly. For example, some apps may integrate with other platforms or systems such as Google Maps, PayPal, or Twilio. Administrators should check the app’s description and documentation before installing it and make sure they understand the implications and costs of using external web services. References: https://help.salesforce.com/s/articleView?id=sf.packaging_install.htm &type=5

Data Loader is a tool that allows administrators to import, export, insert, update, delete, or upsert records in Salesforce using CSV files. Data Loader can handle large data sets and complex data transformations. Data Loader can be used to import records for a custom object from a spreadsheet. Lightning Object Creator is a tool that allows administrators to create custom objects in Salesforce from spreadsheets. Lightning Object Creator can automatically map spreadsheet columns to fields and create relationships between objects. Lightning Object Creator can be used to create a custom object from a spreadsheet and import records at the same time.

The PARENTGROUPVAL function is a formula function that returns the value of a parent group in a report. It can be used to compare values across different groupings and show relative performance. In this case, the administrator can use this function to show the lead source effectiveness for each country by calculating the percentage of leads from each lead source divided by the total number of leads for each country. References: https://help.salesforce.com/s/articleView?id=sf.reports_formulas_parentgroupval.htm &type=5

An entitlement process is a feature that allows you to define and enforce service-level agreements (SLAs) for your customers based on certain criteria and timelines. An entitlement process consists of milestones and actions that represent required steps and time limits for resolving customer issues. You can use entitlement processes to track if your support team is meeting your SLAs and provide consistent service quality to your customers. In this case, you can set up and configure entitlement processes for different types of cases and assign them to accounts or contacts based on their service contracts or warranties. References: https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.entitlements_process.htm &type=5

A session security level is a setting that determines how secure a user’s session is based on factors such as their login method, their IP address, their browser, or their device. Administrators can configure different session security levels for different user profiles and assign different actions or permissions to each session security level.

Multi-factor authentication (MFA) is a feature that requires users to verify their identity using two or more factors of authentication when they log in to Salesforce, such as their username and password plus a verification code or an app-generated token. MFA can enhance the security of user sessions and prevent unauthorized access.

If an administrator recently implemented MFA with a standard security level selected and is receiving cases that users are unable to log in, they should check the session security level required at login on the user profile. This setting determines what session security level users need to have when they log in based on their profile. If this setting is higher than the standard security level, users may not be able to log in with MFA alone and may need additional factors of authentication. References: https://help.salesforce.com/s/articleView?id=sf.security_sessions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.identity_mfa.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

Shield Platform Encryption is a Salesforce feature that allows you to encrypt sensitive data at rest while preserving critical platform functionality. It uses a combination of tenant secrets, encryption keys, and masking policies to protect your data. A field encryption policy is a set of rules that defines which fields are encrypted and how they are masked when displayed. A field encryption policy can be used to encrypt and mask the identification number field, except for the last two digits. References: https://help.salesforce.com/s/articleView?id=sf.security_pe_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_pe_field_encryption_policies.htm &type=5

Two practices that the administrator should adhere to in order to ensure a successful deployment to production are:

Add permissions and access settings to outbound change sets in addition to the dependent component list. This can help avoid deployment errors or access issues caused by missing permissions or settings for the components in the change set. For example, if the change set includes a new custom object, the administrator should also include the object permissions, field-level security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This can help test the change set for any errors or conflicts before deploying it to production. Deployment validations simulate the deployment without actually making any changes and report any issues or warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the change set. It can be deployed along with other components as long as they are compatible and have the required dependencies.

An authentication app is a mobile app that generates verification codes for logging in to Salesforce or other services that require multi-factor authentication (MFA). A username and password are also required for logging in to Salesforce, but they are not sufficient for MFA. References: https://help.salesforce.com/s/articleView?id=sf.identity_auth_apps.htm &type=5

This option will allow the administrator to change the recipient of the fault messages from the consultant’s email to the system admin’s email without modifying any flows or processes. The other options are either not feasible or not effective. References: https://help.salesforce.com/articleView?id=flow_concepts_error_email.htm &type=5

Flow is the automation tool that should be configured to utilize the major listing service endpoint. Flow is a tool that allows administrators to automate complex business processes by building flows that can collect, update, or delete data, invoke Apex code, call external services, and more. Flow can use an Apex action or an HTTP request action to send messages to an external endpoint using REST API

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

Debugging a flow allows administrators to test how a flow behaves before activating it or making changes to it. Debugging a flow runs it in real time using test data provided by the administrator or default values from the flow. However, debugging a flow also performs any actions defined in the flow, such as creating, updating, or deleting records. Therefore, if a flow has a delete element that deletes a record based on certain criteria, debugging the flow will delete the test record even if the flow is inactive. References: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm &type=5

The error condition formula of a validation rule should return TRUE when the validation rule should fire and display an error message. In this case, the validation rule should fire when the Title field has the value of ‘CEO’ and the Phone field is blank. The formula Title = ‘CEO’ && ISBLANK(Phone) returns TRUE when both conditions are met, and FALSE otherwise. References: https://help.salesforce.com/s/articleView?id=sf.fields_useful_field_validation_formulas.htm &type=5

Use separate record types, page layouts, and sales processes for the Rental and Real Estate Teams is how the administrator should extend the Opportunity object to meet the teams’ different needs. Record types are a way to offer different business processes, picklist values, and page layouts to different users based on their profiles or permission sets. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Sales processes are a way to define the stages that an opportunity goes through from creation to close. By using separate record types, page layouts, and sales processes for each team, the administrator can customize the opportunity object according to their different requirements and preferences.

The change can be made through the desktop site by using the Edit All button on the related list of products on the opportunity page. This button allows you to edit multiple products at once and change their price book entries. You cannot use this button on the mobile app, as it is not supported. You also cannot change the price book on the opportunity once it has products added to it, unless you remove all the products first. References: https://help.salesforce.com/s/articleView?id=sf.opportunity_products_edit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.opportunity_products_change_pricebook.htm &type=5

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. References: 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

To access a junction object record, a user needs to have at least read permission on one of its master records and on the junction object itself. If the user does not have access to either master record, they cannot access the junction object record. If the user has access to both master records, they can access the junction object record with the most permissive access level of either master record. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

A before save flow trigger is a type of flow that runs before a record is saved and can update the record without any additional actions or database operations. This can expedite the time required to update the records and improve performance. A before save flow trigger can be used as an alternative to a process builder that updates the same record that triggered it. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_triggers.htm &type=5