Plat-Admn-301 Salesforce Certified Platform Administrator II Question and Answers

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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

The sales manager and system administrator will be able to edit this new contact record because they are either the owner or have Modify All Data permission respectively. Users above or below the sales manager in the role hierarchy will not be able to edit this contact record because contacts are controlled by parent and accounts are set to Public Read Only. All users in the organization will be able to view but not edit this contact record because accounts are set to Public Read Only. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5

To ensure that secure fields remain protected in email templates, administrators should remove the fields from the email. Email templates can expose sensitive information if they contain fields with secure data. By excluding these fields, administrators can prevent unauthorized access to sensitive information through email communication.

Removing Secure Fields from Email Templates:

When creating or updating email templates, administrators should carefully assess the fields included and remove any that contain sensitive information, such as encrypted fields or fields that contain Personal Identifiable Information (PII).

This approach ensures that secure information is not unintentionally shared via email, aligning with best practices for data security and minimizing exposure risks.

Implications of Including Secure Data in Emails:

Secure fields, particularly those that contain sensitive or confidential information, should be restricted from emails to avoid potential data breaches.

Email communication often lacks the same security controls as the Salesforce platform, making it essential to limit the sharing of sensitive data.

Incorrect options:

Implement GDPR: While GDPR compliance ensures proper data handling practices, it does not directly prevent secure fields from being included in emails.

Set up an approval process for email alerts: An approval process can control the sending of email alerts but does not inherently protect secure fields within the email content.

Use classic encrypted fields: Encrypted fields add a layer of security for data at rest within Salesforce but do not provide specific protections for data included in email templates. Moreover, encrypted fields cannot be referenced in email templates.

In conclusion, the most effective way to ensure that secure fields are not exposed through email templates is to remove these fields from the template altogether, avoiding the inclusion of sensitive data in email communications.

A joined report is a type of report that allows you to create multiple report blocks that provide different views of your data. Each report block can have its own fields, columns, sorting, and filtering. A joined report can only be created from summary or matrix reports. You can use a joined report to show data from different report types or data sources on a single report. In this case, you can use a joined report to show Accounts with Open Cases by creating two report blocks: one for accounts and one for cases with a filter for open status. You can then join the two blocks by a common field such as Account ID or Account Name. References: https://help.salesforce.com/s/articleView?id=sf.reports_joined_format.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_examples_joined.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.

One possible reason for the changes to case routing is the difference in the order of execution between before save flow triggers and workflow rules. Before save flow triggers run before assignment rules, which means that any field updates made by the flow can affect how the assignment rules assign the case. Workflow rules run after assignment rules, which means that any field updates made by the workflow do not affect how the assignment rules assign the case. Therefore, replacing workflow rules with before save flow triggers can change the case routing logic. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_of_execution.htm &type=5

When 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 matching rule is a rule that defines how records are compared for duplication based on certain fields or fuzzy logic. By including more fields or changing the matching method, you can make the matching rule more or less strict and reduce false positives or negatives. In this case, including the email field to the existing matching rule for contacts can help avoid duplicate messages for common names by checking if the email addresses are also identical. References: https://help.salesforce.com/s/articleView?id=sf.matching_rules_create.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.matching_rules_considerations.htm &type=5

IP ranges are settings that restrict login access to Salesforce from specific IP addresses. Administrators can set IP ranges at the org level or at the profile level. If a user tries to log in from an IP address that is outside the allowed range for their profile or their org, they will not be able to access Salesforce. Therefore, if a user started to work remotely and is having an issue logging in, it could be because they are not in the IP range for their profile or their org. References: https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm &type=5

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

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.

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

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

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

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

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.com/s/articleView?id=sf.data_export.htm &type=5

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

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

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

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

An administrator should consider using Person Accounts when they have a B2C business model and the consumer is the intended recipient of sales and marketing attention. Person Accounts allow administrators to store information about individual consumers without requiring a separate account record for each contact. References: https://help.salesforce.com/s/articleView?id=sf.account_person_behavior.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

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.

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

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

 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

As explained in question 3, a price book is a list of products and their prices for a specific segment of customers or market. By creating a new price book for the U.K product pricing, Northern Trail Outfitters (NTO) can offer different prices for their products in the U.K market due to shipping and raw material cost differences. The price book can also specify which currency is used for the prices, such as pounds or euros. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks_def.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

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

Modify All is the level of access that the sales user will have on the Account object after being assigned to a muting permission set that mutes Delete access on Account. Muting permissions are a way to reduce or remove access to objects or fields for users who are assigned to permission set groups. Muting permissions can only mute object-level permissions, such as Create, Read, Edit, Delete, View All, or Modify All, but not field-level permissions or other permissions. Muting permissions can only reduce or remove access that is granted by other permission sets or permission set groups within the same permission set group, but not by profiles or other sources of access. Therefore, in this case, the muting permission set will only mute the Delete access on Account that is granted by the permission set group, but not the Modify All access that is also granted by the permission set group.

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_lightning_experience_security_sharing

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

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. Removing some of the fields displayed can help reduce the loading time of a record page by minimizing the number of queries and calculations that need to be performed when rendering the page. Reducing the number of related lists displayed can help reduce the loading time of a record page by limiting the amount of data that needs to be retrieved and displayed on the page

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

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

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?id=sf.products_define.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

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.

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’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

A validation rule is a formula that validates the data entered by a user and prevents the record from being saved if the data does not meet certain criteria. In this case, the administrator can create a validation rule to ensure that the custom encrypted field for credit card numbers has exactly 16 digits. The other options are not applicable for encrypted fields. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_encrypted_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

An entitlement is a record that represents a customer’s right to receive support or service based on the terms of a contract or agreement. An asset is a record that represents a product that a customer has purchased. To automatically provide phone support to customers who purchase photo editing software, the administrator can create a flow that attaches an entitlement to the asset upon purchase. The entitlement can have a term of 365 days and a service contract that specifies the phone support details. References: https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.assets_overview.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

To grant access for the sales rep who broke their phone and needs multi-factor authentication using Salesforce Authenticator app, the administrator can generate a temporary identity verification code for them. This code allows users who don’t have their verification method available to log in securely without compromising their account security. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_codes.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. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

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