Advanced-Administrator Salesforce Certified Advanced Administrator (SU24) Questions and Answers

Data Import Wizard is a tool that allows administrators to import data for standard and custom objects in Salesforce using CSV files. Data Import Wizard can handle up to 50,000 records at a time and supports simple data transformations and validations. Data Import Wizard can be used to upload records for a custom object when the number of records is small and the import frequency is low.

Opening the flow in Debug mode and running it as another user allows simulating how the flow behaves for different users with different permissions and settings. This can help identify any issues related to user

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: 

The Dev Console Log Inspector is a tool that allows you to view and analyze debug logs in a graphical interface. Debug logs contain information about database operations, system processes, and errors that occur when executing a transaction or running unit tests. To troubleshoot a process builder, the administrator should look for event types beginning with FLOW in the event column. These event types indicate the start and end of a flow interview, as well as any flow elements, faults, or decisions that occur during the execution. References: https://help.salesforce.com/s/articleView?id=sf.code_dev_console_log_inspector.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.code_debug_log_event_types.htm &type=5

Workflow is the debug log category that should be used to troubleshoot an issue with a flow. Workflow is a debug log category that captures information about workflow rules, flows, processes, approval processes, and entitlement processes. Workflow can help identify errors or issues related to these automation tools by showing details such as evaluation criteria, actions executed, variables assigned, and outcomes reached.

A roll-up summary field is used to display a value in a master record based on the values of a set of related detail records. In this case, the administrator can create a roll-up summary field on the Properties object that counts the number of Open House records in a Pending status. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

UESTION NO: 92

Sales management wants a small subset of users with different profiles and roles to be able to

view all data for compliance purposes. How can an administrator meet this requirement?

A. Assign delegated administrator to the subset of users to View All Data.

B. Create a new profile and role for the subset of users with the View All Data permission.

C. Enable the View All Data permission for the roles of the subset of users.

D. Create a permission set with the View All Data permission for the subset of users.

Answer: D

A permission set is a collection of settings and permissions that give users access to various tools and functions. The View All Data permission allows users to view all data, regardless of sharing settings. By creating a permission set with this permission and assigning it to the subset of users, the administrator can meet the requirement without changing their profiles or roles. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm&type=5

Formula field and Dynamic Forms should be created to meet the requirements because a formula field can be used to count the number of open opportunities over US$10,000 related to an account using a roll-up summary filter condition, and Dynamic Forms can be used to display or hide a component on an account page based on a visibility filter using the formula field value. References: https://help.salesforce.com/s/articleView?id=sf.customize_functions_i_z.htm

Identity verification history and login history are two areas that the administrator can review to understand potential root causes of multi-factor authentication issues. Identity verification history shows the methods and results of identity verification attempts for a user, such as email verification, SMS verification, or app verification. Login history shows the status, source, and location of login attempts for a user, as well as any login errors or challenges that occurred. These two areas can help the administrator identify if the user entered the correct verification code, if the user’s device or app is compatible with multi-factor authentication, or if there are any network or security issues that prevent successful verification. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.monitor ing_login_history.htm&type=5

Run the standard Data Classification report is what the administrator should recommend to the compliance team. Data Classification is a feature that allows administrators to flag where sensitive information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data Classification also provides a standard report that shows field level sensitivity and classification for all fields in an org. The administrator can run this report and share it with the compliance team to meet their requirement. 

The Analyze feature in the Lightning App Builder toolbar is a tool that helps you optimize the performance of your record pages by providing recommendations and insights on how to improve page load time and user experience. It can help you identify which fields and components are taking the most time to load and suggest ways to reduce their impact. You can also compare your page performance with other pages in your org or with Salesforce best practices. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_optimize.htm &type=5

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

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

Setup Audit Trail is a tool that tracks the recent setup changes made by anyone in an org. It can help identify who made what changes and when, as well as any errors or failures that occurred during the changes. Setup Audit Trail can help troubleshoot deployment issues by comparing the changes made in production with those made in sandbox

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.

A summary report with a cross-filter is a type of report that allows you to summarize data by grouping rows and columns and applying filters based on related objects and fields. A cross-filter is a filter that lets you include or exclude records in your report based on related objects and their fields. In this case, you can create a summary report that includes a cross-filter to the Account object with a sub-filter for credit card number equal to null. This will show you all B2C accounts that are missing the credit card number, regardless of whether it is encrypted or not. References: https://help.salesforce.com/s/articleView?id=sf.reports_summary_charts.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.reports_cross_filters.htm&type=5

To make inventory data from a legacy application available in Salesforce, the administrator can create an external object that maps to the inventory application. An external object is similar to a custom object, except that it maps to data that’s stored outside your Salesforce organization. External objects enable users to view and report on external data in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.external _object_overview.htm&type=5

When deploying profiles using change sets, the field-level security settings are not included unless the fields themselves are also part of the change set. Therefore, the administrator should consider adding the new custom fields to change set 2 along with the profiles, or manually adjust the field-level security after deployment. References: https://help. salesforce.com/articleView?id=changesets_about_components.htm&type=5

Delegated Administration is a feature that allows administrators to delegate some administrative tasks to other users without giving them full access to Setup. Delegated administrators can manage users and assign permissions for specific custom objects, tabs, apps, and fields. This can help reduce the workload of the system administrator and empower power users to make configuration changes to a specific custom object

To add a user to an opportunity team, you need Edit access on the account associated with the opportunity and either own the opportunity or be above the owner in the role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.teams_adding.htm &type=5

Data Loader is a tool that allows administrators to import or export large amounts of data (more than 50,000 records) from or to Salesforce using CSV files. Data Loader can be used for inserting, updating, deleting, upserting, exporting, or extracting data. Bulk API is an API that allows administrators to process large batches of records asynchronously in the background. Bulk API can handle millions of records with high performance and minimal system resources. By using Data Loader with Bulk API enabled, an administrator can import a large amount of historical data (more than 100,000 records) from another system efficiently and securely. References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.loader_api.htm&type=5 https://help.salesforce.com/s/articleVi ew?id=sf.bulk_api_intro.htm&type=5

 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.

Delegated administration allows administrators to delegate certain user management tasks to other users without granting them full administrative privileges. Delegated administrators can create and manage users only within specified roles or public groups. This option will meet the requirement of allowing each division to create and manage users only within their division. References: https://help.salesforce.com/articleView?id=delegated_administration_overview.htm &type=5

To ensure that sales reps’ managers can view records containing customer’s credit information but their colleagues cannot, NTO should grant access using hierarchies via the sharing settings. This option allows users above another user in the role hierarchy to have access to records owned by or shared with users below them in the hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5

To restore the deleted Review records, you need to restore both the Account and Product master records from the Recycle Bin. A master-detail relationship is a type of relationship that links two objects together and enforces a parent-child relationship between them. A master-detail relationship affects the security and deletion of the child records. If you delete a master record, all of its detail and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or subdetail record, you must first restore its parent record. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.recyclebin_overview.htm &type=5

Two options that the administrator should check to ensure the product is available are:

Confirm the correct price book is selected on the opportunity. A price book is a list of products and their prices that can be added to an opportunity. An opportunity can have only one price book at a time, and the products that are available for selection depend on the price book that is chosen. Therefore, the administrator should check if the opportunity has the right price book that contains the new keyboard product.

Ensure the product is associated with the correct price book. A product is a good or service that can be sold in Salesforce. A product can be associated with one or more price books, depending on how it is priced for different markets or segments. Therefore, the administrator should check if the new keyboard product is added to the appropriate price book that is used by the opportunity.

The other two options are incorrect because:

Making custom fields does not affect the availability of products on an opportunity. Custom fields are used to store additional information or calculations on an object, but they do not determine which products can be selected from a price book.

Turning on field tracking does not affect the availability of products on an opportunity. Field tracking is used to monitor changes to certain fields on an object and display them in a history related list, but it does not determine which products can be selected from a price book.

References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.products_define.htm &type=5

Allow Forecasting is what the administrator should review to solve this issue. Allow Forecasting is a user permission that enables users to access and edit forecasts. If a user does not have this permission, they will not be able to see their own forecast or any forecasts below them in the role hierarchy. Therefore, the administrator should make sure that the sales rep has this permission enabled on their profile or permission set.

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

To limit data exports, especially for sensitive information, Export Data Settings in Salesforce are specifically designed to control user access to export data. These settings allow administrators to restrict who can export data from Salesforce, helping to protect sensitive information like bank accounts and Personal Identifiable Information (PII).

Export Data Settings:

Salesforce provides administrators with the ability to manage permissions related to data export functions. This includes restricting access to tools like Data Export, Data Loader, and Report Exports.

By limiting these permissions, administrators can control which users are allowed to export data, thereby reducing the risk of sensitive data, such as PII, being exported by unauthorized individuals.

This is particularly useful for ensuring that only designated roles or users can export data, as per the organization’s data security policies.

Specific Use Case for Sensitive Information:

In a scenario where the focus is on preventing unnecessary access to sensitive information, Export Data Settings directly target the ability to export data and can be customized based on the security needs of the organization.

By disabling or limiting export permissions for specific profiles or roles, AW Computing can better manage the risk associated with handling sensitive data.

Incorrect options:

Salesforce Platform Encryption: While it protects sensitive data at rest by encrypting fields and files, it does not control export capabilities or prevent users from exporting data.

Salesforce Shield: This suite includes event monitoring, encryption, and audit trail features, which enhance security but do not specifically limit export permissions.

Muted Permission Sets: These are used to restrict permissions in permission set groups but are not designed to manage or limit data export capabilities directly.

In conclusion, Export Data Settings offer the most precise control over data export capabilities in Salesforce, making it the best solution to meet the security department's requirement.

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

The user profile permissions on the Opportunity object is the item that the administrator should review to find out why the user is unable to delete the duplicate record. The user profile permissions determine what users can do with records and objects in Salesforce, such as creating, editing, deleting, viewing, or sharing. In this case, the administrator should check if the user has the Delete permission on the Opportunity object, which allows them to delete opportunity records that they own or have access to. If not, the administrator can either grant them this permission or delete the record for them. References: https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_object_permissions.htm &type=5

To use outbound change sets, a user needs to have the Create and Upload Change Sets permission on their profile or permission set. This permission allows users to create change sets in a sandbox or Developer Edition organization and upload them to another organization. References: https://help.salesforce.com/s/articleView?id=sf.changesets_create_upload_perm.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_v alidation_formulas.htm&type=5

The Delete permission is missing on the user for Accounts is what is preventing the user from completing the merge. Merging accounts is a way to combine up to three duplicate accounts into one master record and update the related records accordingly. Merging accounts requires the Delete permission on accounts because merging accounts involves deleting the duplicate records and keeping only the master record.

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

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

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

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

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

The setup audit trail tracks the recent setup changes that you and other administrators have made to your org. It can help you troubleshoot issues by showing you what changes were made, who made them, and when. In this case, the setup audit trail can help the administrator identify if someone changed the field-level security, page layout, or profile settings for the industry picklist field. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.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 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_elemen ts_triggers.htm&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: https://help.salesforce.com/articleView?id=sf.identity_verification_history.htm &type=5

A custom summary formula is a formula that calculates values from summary fields in reports such as sums, averages, counts, etc. Custom summary formulas can use functions such as PREVGROUPVAL which returns the value of a field from the previous row at the same grouping level. By using a custom summary formula with the PREVGROUPVAL function, an administrator can create a report to calculate the year-over-year change in the dollar amount of a company’s opportunities by subtracting the amount from the previous year from the amount from the current year and dividing by the amount from the previous year. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_summary_formulas.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_functions.htm &type=5

Territory management is a feature that allows you to grant access to accounts and opportunities based on criteria such as geography, industry, product line, or customer size. A territory is a grouping of accounts and users that represents a market segment or business unit. In this case, the administrator should utilize territory management to add the operations team to the East territory, which contains all the accounts and opportunities in the East region. This way, the operations team members can access all the records in their territory regardless of who owns them or what the organization-wide default is. References: https://help.salesforce.com/s/articleView?id=sf.territories_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.territories_define.htm &type=5

A validation rule and a stage guidance in Path are two features that can help ensure that users input a use case before moving the opportunity stage to qualified.

A validation rule is a formula that validates the data entered by users and prevents records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to check if the Use Case field is blank when the Stage field is changed to Qualified, and display an error message if so.

A stage guidance in Path is a feature that displays helpful information or tips for each stage of a sales process on an opportunity record page. In this case, adding the Use Case field to the stage guidance in Path can remind users to fill out this field before moving to the next stage.

The order in which record-triggered flows are executed is not guaranteed. If there are multiple record-triggered flows on the same object and trigger type, Salesforce does not guarantee which one runs first. Therefore, the administrator should consider this when designing record-triggered flows that depend on each other’s outcomes. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm &type=5

Two combined automation tools that the administrator can use to create the task record and assign based on date criteria are:

Create a formula field to capture the MAX date. A formula field is a custom field that calculates a value based on other fields or expressions. In this case, a formula field can be used to capture the maximum value between Estimated Shipping Date and Client Need By Date fields and store it as a date value.

Make a Process Builder to create the task. A Process Builder is an automation tool that allows you to create processes that perform actions based on certain criteria. In this case, a Process Builder can be used to create a task record when a certain condition is met and assign its due date based on the formula field value.

The other two options are incorrect because:

An approval process is an automation tool that allows you to route records for approval based on certain criteria and approval steps. It does not create or assign tasks based on date criteria.

A workflow rule is an automation tool that allows you to perform actions based on certain criteria and evaluation time. It does not create or assign tasks based on date criteria.

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

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

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 grants login access to another user. This means that you can use the Setup Audit Trail to see if any other administrators or delegated administrators are using the Log In As a User feature. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.remoteaccess_granting_login_access.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.

References: https://help.salesforce.com/s/articleView?id=sf.change_sets_components.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.change_sets_deploy.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.change_sets_validate.htm &type=5

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

A phone field that provides the full phone number of the seller, a number field that designates the square footage of the listing, and a picklist field that designates the county of the listing should be used as filter criteria because they are fields that can be used to narrow down the report results based on specific values or ranges. A multi-select picklist field that designates features of the listing and a formula field that calculates a price for the listing should not be used as filter criteria because they are fields that cannot be filtered on in reports. References: https://help.salesforce.com/s/articleView?id=sf.reports_filtering.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_fields_unavailable.htm &type=5

To help with this issue, the administrator can do the following options:

Move some page components behind a tab. This will reduce the number of components that load initially and improve performance.

Remove some of the fields displayed. This will reduce the amount of data that needs to be retrieved and rendered on the page.

Reduce the number of related lists displayed. This will also reduce the amount of data that needs to be retrieved and rendered on the page. References: https://help.salesforce.com/s/articleView?id=sf.lex_performance_considerations.htm &type=5

change sets are tools that allow administrators to move customizations from one Salesforce org to another. However, change sets do not track dependencies or conflicts between components in different orgs, so administrators need to manually verify that all required components are included in the change set and that they do not overwrite existing customizations in the target org. To avoid losing changes in production due to deploying an incomplete or incorrect change set, administrators should push the change set to another sandbox first and test it there before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.changesets_considerations.htm &type=5 https://help.salesforce.com /s/articleView?id=sf.changesets_best_practices.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 cross-object formula is a formula that references fields from related objects. The administrator can create a cross-object formula field on the Case object that displays the current status from the Account. This field can be used in validation rules and other processes. References: https://help.salesforce.com/s/articleView?id=sf.tips_on_building_formulas_cross_object_formulas.htm &type=5

To ensure that multiple field updates occur in a specific order on a custom object, the administrator should create a process with one criteria node and three field updates arranged in the correct order. This approach allows the updates to execute sequentially within a single automation framework, ensuring that they happen in the intended order.

Using Process Builder with a Single Criteria Node:

In Process Builder, the administrator can define a single criteria node that triggers the field updates. By adding multiple field updates within this single node and arranging them in the desired sequence, Salesforce will execute them in that specific order.

This setup provides better control over the sequence of updates compared to multiple workflow rules, as Process Builder will execute each field update step by step as configured within the node.

Advantages Over Workflow Rules:

Unlike workflow rules, where the order of execution can be less predictable due to separate triggers, Process Builder enables precise control over the execution sequence within the same process.

Using multiple workflow rules or multiple criteria nodes with stop actions would complicate the setup without guaranteeing the specific order. Process Builder’s structure ensures that updates proceed in the exact order defined.

Incorrect options:

Option A (Three workflow rules): Creating separate workflow rules for each update does not ensure a specific order of execution, as workflow rules are not guaranteed to run sequentially.

Option C (Three criteria nodes with stop actions): This approach would execute each node separately, and the stop action after each node adds unnecessary complexity, without ensuring the sequential order required.

Option D (One workflow rule with three field updates): Workflow rules do not guarantee the order of field updates within a single rule. Using Process Builder with a single node is more reliable for sequential execution.

In conclusion, Process Builder with one criteria node and ordered field updates is the most effective approach to ensure a specific execution sequence for multiple field updates on the Shipment object.

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. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automatio n/automation_considerations

A cross filter with WITHOUT logic is a method for creating a report that shows accounts that are missing certain related records. A cross filter is a filter that lets you include or exclude records in your report based on related objects and their fields. You can use cross filters to create reports on accounts with or without opportunities, contacts, cases, or other related objects. In this case, you can use a cross filter with WITHOUT logic to show accounts without assets that have a certain product name or code. This way, you can identify customers that need to install a new solar panel monitor system. References: https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_examples_cross_filters.htm &type=5

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

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

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

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also have decision elements that evaluate conditions and determine which path to follow in the flow. By combining the two flows into one with decision elements, the administrator can ensure that the flow runs in the correct order and updates the field on the child record after it is created by the first flow. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.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

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

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/art icleView?id=sf.users_permissionsets.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