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

The flow debug option is a tool that allows you to test and troubleshoot your flow by running it in debug mode and inspecting the values of variables and resources at each step. You can also set the debug mode to run as another user and see how the flow behaves for different users with different permissions and settings. In this case, using the flow debug option and setting the selection to run as another user can help identify why one user is experiencing a flow error while others are not. References: https://help.salesforce.com/s/articleView?id=sf.flow_ debug.htm&type=5

Public groups let you share records with a set of users defined by criteria such as role, profile, or individual users. You can use public groups as recipients for email alerts in workflow rules or process builder. References: https://trailhead.salesforce.com/en/content/learn/modules/administration_essentials_for_new_admins_in_lightning_experience/administration_essentials_for_new_admins_in_light ning_experience_security_sharing

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

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

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

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

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

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

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

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

A junction object is a custom object with two master-detail relationships that allows you to create many-to-many relationships between two objects. In this case, the Job Application object can be used as a junction object to link the Application object and the Job Posting object, so that each application can be related to one or more job postings, and each job posting can have one or more applications. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.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

To show forecast numbers by territory regardless of who owns the record, CK should enable Territory Forecast. To forecast based on role hierarchy, CK should enable Role Hierarchy Forecast. To match the Territory Forecast to the Hierarchy Forecast model, CK should modify the Territory Forecast accordingly. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_territory_forecasts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.forecasts3_enable.htm &type=5

The order of execution for flows that are configured to run before the record is saved on the same object is unpredictable and may vary depending on factors such as flow version, flow name, or flow creation date. Therefore, it is recommended to avoid creating multiple flows with the same trigger conditions and instead consolidate them into a single flow.

The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page. References: https://help.salesforce.com/s/articleView?id=sf.customize_layouts.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 Automated Case User is the default user for cases created via Email-to-Case. This user needs to have permissions to the new record type in order to assign it to the incoming cases. If the Automated Case User does not have the permissions, the cases will receive a different record type based on the organization-wide default settings. References: https://help.salesforce.com/s/articleView?id=sf.case_email_to_case.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_automated_user.htm &type=5

UESTION NO: 187

The administrator at Cloud Kicks recently replaced several case workflow rules with a single before save flow. Since this change, some cases are routing In unexpected ways.

What could be the cause or the charges to routing?

A. The old workflow rules are still active and impacting routing.

B. The flow precedes assignment rules; workflow rules are after assignment rules.

C. Assignment rules no longer reference the correct fields.

D. Multiple automation tools have been used and the automation is executed in a different order.

Answer: D

Multiple automation tools have been used and the automation is executed in a different order. This could cause some cases to route in unexpected ways, because the before save flow might override or conflict with the assignment rules or other automation tools that run after the record is saved. The administrator should review the order of execution and ensure that the flow logic is consistent with the other automation tools. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm

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 Classification is the feature that the administrator should use to flag where sensitive information is stored in Salesforce. 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 can help administrators comply with data privacy regulations and best practices by identifying and managing sensitive data in their orgs.

A forecast is a projection of how much revenue or quantity you can generate from your sales pipeline for a given period of time. A forecast can be either revenue-based or quantity-based, depending on what you want to measure and track. A revenue-based forecast shows the amount of money expected from closed sales, while a quantity-based forecast shows the number of units expected from closed sales. You can choose the forecast type that best suits your business needs and goals when you set up Collaborative Forecasts in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.forecasts3_forecast_ty pes.htm&type=5

Implement Service Console is what the administrator should recommend to support staff at Cloud Kicks for a better agent experience. Service Console is a Salesforce app that provides a unified interface for agents to manage multiple customer interactions and records at once. Service Console can help agents work more efficiently and productively by providing features such as tabs, subtabs, list views, related lists, highlights panel, interaction log, macros, keyboard shortcuts, and more

Product schedules are features that allow administrators to track revenue or quantity over time for products in opportunities or orders. Product schedules can be either revenue schedules or quantity schedules, depending on whether the product is sold by amount or by quantity. Product schedules can be either standard or customizable, depending on whether they use predefined settings or custom settings.

Line item schedules are records that represent each installment of revenue or quantity for a product over time. Line item schedules are created automatically when a product with a product schedule is added to an opportunity line item or an order product.

One limitation of product schedules is that line item schedules are unavailable in Process Builder and Workflow. This means that administrators cannot use these tools to automate actions based on line item schedules, such as sending email alerts, creating tasks, updating fields, or invoking flows. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_product_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.orders_line_item_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.product_schedule_considerations.htm &type=5

Password Policies on the System Administrator profile is a feature that allows administrators to set different password requirements for users with different profiles. Password Policies can specify the minimum length, complexity, expiration period, history enforcement, lockout interval, and warning message for passwords. Password Policies can be used to enforce stricter password requirements for system administrators than for other users

Building a process that updates the record type field to B2C Customer after conversion will correct this issue. The conversion layout for person accounts does not allow selecting different record types for accounts and contacts. The default record type for person accounts is determined by the organization-wide default settings. However, a process can be triggered after conversion to update the record type field based on the lead record type or other criteria. References: https://help.salesforce.com/s/articleView?id=sf.convert_leads_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.convert_leads_mapping.htm &type=5

Tableau CRM is a product that allows users to create complex dashboards with supporting charts based on data from a variety of sources, some of which live on internal company shared drives. Tableau CRM can connect to external data sources using connectors or dataflows and store the data in datasets within Salesforce. Tableau CRM can also use artificial intelligence and machine learning to provide insights and recommendations based on the data

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

An object-specific quick action is a type of action that allows users to do something in the context of a specific object, such as creating or updating a record, logging a call, sending an email, or launching a custom action. In this case, the administrator can create an object-specific quick action on the opportunity object that pre-populates certain fields with predefined values and allows users to quickly close an opportunity from the Salesforce mobile app. References: https://help.salesforce.com/s/articleView?id=sf.actions_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.actions_objectspecific_actions.htm &type=5

When the feature for Contacts to multiple Accounts is enabled, a Contact can have a direct relationship with multiple Accounts. However, one of these relationships must be designated as the primary Account relationship. This relationship is required on a Contact regardless of the page layout settings and cannot be removed unless the Contact is deleted or merged with another Contact. References: https://help.salesforce.com/s/articleView?id=sf.shared_contacts_set_up.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.shared_contacts_considerations.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

As explained in question 13, permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. Permission sets are useful when a user is part of a team with an assigned profile that covers the majority of their needs but requires more access than the rest of their team for some specific tasks or functions. For example, a user may need access to a custom object or field that is not available to their profile, but only for a limited time or project. In this case, assigning a permission set to the user can grant them the additional access they need without affecting their profile or other users with the same profile. References: https://help.salesforce.com/s/articl eView?id=sf.perm_sets_overview.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

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. References: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.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

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.

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

Delegated Administration allows administrators to delegate certain user management tasks to non-administrators. For example, a delegated administrator can assign permissions sets to users in specified roles or public groups without having full access to modify permission sets. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgt_delegated.htm &type=5

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

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.

References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_loader_describe_global.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_object_permissions

Two considerations that the administrator should remember about roll-up summary fields are:

Roll-up types include COUNT, SUM, and AVG. A roll-up type is a function that determines how the data from the child records is aggregated and displayed on the parent record. The available roll-up types are COUNT, which counts the number of child records; SUM, which adds up the values of a numeric field on the child records; AVG, which calculates the average value of a numeric field on the child records; MIN, which displays the lowest value of a field on the child records; and MAX, which displays the highest value of a field on the child records.

Roll-up summary fields are created on the master side of a master-detail relationship. A master-detail relationship is a type of relationship that links two objects together such that the master object controls certain behaviors of the detail object, such as security and deletion. A roll-up summary field is a type of field that displays a value that is calculated from child records related to a parent record. Roll-up summary fields can only be created on the master object of a master-detail relationship or on a lookup relationship if it is set as required.

The other two options are incorrect because:

Roll-up summary fields do not prevent the conversion of a master-detail relationship to a lookup. They only prevent it if they reference a formula field that includes another relationship.

Rollup fields are not calculated prior to save. They are calculated after save and may take some time to update.

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

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

Move some page components behind a tab, remove some of the fields displayed, and reduce the number of related lists displayed are three options available to the administrator to help with this issue. Moving some page components behind a tab can help reduce the loading time of a record page by hiding some components until they are needed by the user.

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.

A public group is a grouping of users, roles, roles and subordinates, or other groups that can be used to share access to records or folders. A sharing rule is a rule that grants additional access to records based on certain criteria or ownership. In this case, the administrator should create a public group for the renewals team and create a criteria based sharing rule on opportunities that grants read-only access to the group for all closed won opportunities. This way, the renewals team can see all the opportunities that are eligible for renewal while keeping the account private. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm &type=5

The issue is that the Company field is being populated on B2C Leads, which is causing the Lead Conversion Layout to only display Business Account record types. To correct this, the administrator should use a validation rule to ensure that the Company field is blank on B2C Leads. This will prevent the Lead Conversion Layout from displaying Business Account record types and will allow the administrator to select the B2C Customer record type.

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

Use an Insert operation to load data because the data is not already in Salesforce and does not need to be updated or deleted3. Map an External ID data value to the object because External IDs are used to create relationships between records that are being imported and records that already exist in Salesforce4. References: 3 https://help.salesforce.com/s/articleView?id=sf.data_loader_insert.htm &type=5 4 https://help.salesforce.com/s/articleView?id=sf.data_loader_relationships.htm &type=5

Tableau CRM is a product that allows you to create complex dashboards with supporting charts based on data from a variety of sources, including Salesforce data and external data sources. Tableau CRM uses an analytics platform that stores data in datasets and lets you explore and visualize data using lenses and dashboards. You can also use artificial intelligence and machine learning features to discover insights and make predictions from your data. Tableau CRM is integrated with Salesforce and can be accessed from various apps and objects. References: https://help.salesforce.com/s/articleView?id=sf.bi_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.bi_data_overview.htm &type=5

Salesforce’s Data Export Service is a tool that allows you to export your organization’s data to a set of comma-separated values (CSV) files and store them in a backup location of your choice. You can schedule this service to run weekly or monthly and receive an email notification when your files are ready to download. This is one way to back up your data daily without using any external tools or services. References: https://help.salesforce.co m/s/articleView?id=sf.data_export.htm&type=5

A price book is a list of products and their prices that can be added to an opportunity. A product can have different prices for different markets or segments, and these prices are stored in different price books. In this case, the administrator should create a new price book for the new retail pricing and add the products that are sold to retail locations for resale. This way, the users can select the appropriate price book and products for their opportunities based on the type of customer they are selling to. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm &type=5 https://help.salesforce.com/s/articleView?i d=sf.products_define.htm&type=5

Process Builder and Flow Builder are tools that allow administrators to automate business processes in Salesforce without writing code. Process Builder and Flow Builder can perform actions such as creating records, updating fields, sending emails, posting to Chatter, invoking Apex classes, calling flows, etc.

To automate several updates to lead records and update unrelated records at Cloud Kicks, an administrator can use two options:

B) Create a Process Builder that runs when a record is changed

Process Builder is a tool that allows administrators to create processes that consist of criteria nodes and action groups. Criteria nodes define the conditions that trigger the process and action groups define the actions that the process performs. Processes can run when a record is created or when a record is created or edited.

By creating a Process Builder that runs when a record is changed, an administrator can automate updates to lead records based on certain criteria and perform actions such as updating fields, sending emails, posting to Chatter, invoking Apex classes, calling flows, etc. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_considerations.htm &type=5

C) Create a flow that runs when a record is created or updated

Flow Builder is a tool that allows administrators to create flows that consist of elements such as screens, assignments, decisions, loops, etc. Elements define the logic and user interface of the flow. Flows can run in different ways such as when a user clicks a button, when a record is updated by Process Builder, when an event occurs in the system (such as record creation), etc.

Assignment rules and validation rules are two features that can satisfy these requirements:

Assignment rules are used to automatically assign leads or cases to users or queues based on certain criteria. In this case, an assignment rule can be used to assign leads to different planetary teams depending on which planet the lead is coming from.

Validation rules are used to validate the data entered by users and prevent records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to ensure that every team has all of the information they need by making certain fields required or dependent on other fields.

The other two options are incorrect because:

Matching rules are used to identify duplicate records based on certain fields or fuzzy logic. They do not assign records or validate data.

Workflow rules are used to automate tasks or actions based on certain criteria. They do not assign records or validate data.

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

Using a Get Record component allows the flow to dynamically retrieve records based on criteria or record IDs without hard coding them. This makes the flow more flexible and maintainable. Updating record elements outside the flow loop prevents unnecessary DML operations and reduces the risk of hitting governor limits.

The resume event is recalculated and the email goes out to the account owner immediately because the flow uses a scheduled path that evaluates the expiration date field every time it changes. When the expiration date is changed to yesterday, the flow resumes immediately and executes the action of sending the email

Entitlement management lets you create and maintain service contracts that specify the support terms for each account. You can use entitlement processes to automatically apply the correct service contract to a case based on criteria you define. References: https://trailhead.salesforce.com/en/content/learn/modules/entitlements/entitlements_overview

Displaying the related contacts related list and adding the direct field will allow users to distinguish between contacts and related contacts. The related contacts related list shows all contacts that are related to an account, either directly or indirectly. The direct field indicates whether a contact is directly associated with an account or not. By adding this field to the related list, users can easily see which contacts are direct and which are not. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts_direct_field.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

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

 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

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

Debug logs capture database operations, system processes, and errors that occur when executing a transaction or running unit tests. Debug logs can help identify the cause of Apex CPU time limit exceeded errors by showing the execution time of each Apex statement and trigger. References: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_debugging_debug_logs.htm

A primary account relationship is a feature that allows you to link a contact to a single account as its primary account. A primary account relationship is required on a contact regardless of the page layout settings or the contact to multiple accounts feature. This means that you cannot remove the primary account from a contact, but you can change it to another account. You can also add secondary accounts to a contact if you have enabled the contact to multiple accounts feature. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.contacts_fields.htm &type=5

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

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

A flow is an automation tool that allows you to create processes that perform actions based on user input or record changes. A flow can be triggered by a user who launches it from a button, link, or Lightning page, or by the system when a record is created or updated. A flow has different versions that can be active or inactive. An active version is the one that runs when the flow is triggered, while an inactive version is the one that is saved but not running. When you deploy a flow to production with a change set, the flow version is deployed as inactive by default. This means that you need to activate the flow manually after deployment if you want it to run in production. References: https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_changesets.htm &type=5

An after save flow is a type of flow that runs in the background after a record is saved and performs actions based on the record data or changes. An after save 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 flow that runs when a case record is updated and delivers status update email to customers based on certain criteria or conditions. References: https://help.salesforce.com/s/articleView?id=sf.flow_trigger_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigge r.htm&type=5

Dynamic actions are actions that appear on Lightning record pages based on criteria such as field values or user profiles. Dynamic actions allow administrators to customize which actions are available for users on different record types or page layouts without creating multiple page layouts for each scenario. By using dynamic actions and conditional visibility for accounts at AW Computing, administrators can show only relevant actions for customer service and sales users based on their situation. References: https://help.salesforce.com/s/articleView?id=sf.dynamic_actions_overview.htm &type=5

Two options that the administrator should use to meet these criteria are:

Share with roles and subordinates of the finance director role. This option allows you to grant access to records based on the role hierarchy of your org. You can share records with users who are in a specific role or in roles below that role in the hierarchy. In this case, you can share records with roles and subordinates of the finance director role, which includes all the members of the finance team.

Create a criteria-based sharing rule where the won field = true. This option allows you to grant access to records based on certain field values or formulas. You can create a criteria-based sharing rule on opportunities that grants access to records where the won field is true, which means that the opportunity stage is closed won.

The other two options are incorrect because:

Make an owner-based sharing rule where the won field = true is not an option because owner-based sharing rules do not allow you to specify field values or formulas as criteria. Owner-based sharing rules only allow you to share records based on who owns them or what role or group they belong to.

Select all opportunities owned by the sales manager role is not an option because it does not meet the criteria of sharing all closed won opportunities. It only shares opportunities that are owned by users who are in the sales manager role, regardless of their stage.

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

A Text Area (Rich) field allows users to format the text with fonts, colors, images, and hyperlinks. It also supports mapping to an opportunity when converting a lead. References: https://help.salesforce.com/s/articleView?id=sf.fields_using_rich_text_area.htm &type=5

Making the field Read Only on the page layout prevents users from manually entering or editing the field value on the record page. This ensures that users cannot bypass answering the questions in order to determine their Tier value. Using a screen flow to ask the questions allows administrators to create an interactive user interface that guides users through a series of screens based on their inputs and logic. A screen flow can be used to ask questions and set the field value based on the answers

Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than 100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records. Bulk API is an API that allows fast and parallel processing of large batches of records. 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