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

Planning deployments around maintenance schedules ensures that there are no interruptions or delays in the deployment process. Deploying all dependent components ensures that there are no missing metadata or references that could cause errors or failures in the deployment. Limiting change sets to 10,000 files ensures that the deployment does not exceed the maximum size limit for change sets

Change sets are tools that allow administrators to move customizations such as fields, page layouts, profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators need to establish a deployment connection between a source org (such as a sandbox) and a target org (such as production). Then, administrators can create an outbound change set in the source org that contains the components they want to deploy, and upload it to the target org. In the target org, administrators can view and validate the inbound change set before deploying it to their org. References: https://help.salesforce.com/s/articleView?id=sf.changesets.htm &type=5

A record-triggered flow lets you automate actions when a record is created or updated. You can use scheduled paths to schedule actions relative to a date field on the record, such as close date. You should configure the trigger to flow after the record is saved so that you can access the updated field values. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_types_record.htm &type=5

Read permission is required on at least one master record to be able to see the solar panel records. Since Item is a junction object between Doc and Solar Panel, users need to have access to either Doc or Solar Panel to see Item records. If users have access to both Doc and Solar Panel, they can see all Item records related to either object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manyto many.htm&type=5

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

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

Product schedules allow users to track revenue or quantity over time for products in opportunities or orders by creating schedules manually or automatically based on predefined criteria such as start date, end date, frequency etc. However, product schedules have some limitations that administrators should consider before enabling this feature. One of these limitations is that line item schedules are unavailable in Process Builder and Workflow rules; only revenue schedules are available. References: https://help.salesforce.com/s/articleView?id=sf.products_schedules_def.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.products_schedules_considerations.htm &type=5

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

A 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

A lookup relationship is a type of field that links one object to another object. It allows you to access related data from another object and display it on a record page. A lookup relationship can be used to link the custom object that stores financial information to the Account object, so that only finance team members can see the related financial information about the account. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

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

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

 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.

A price book is a list of products and their prices for a specific segment of customers or market. By creating a separate price book for the special bundle deal on monitors and keyboards, AW Computing can offer different prices for these products without affecting their standard prices or requiring VP approval. The price book can also specify which products are included in the bundle and which are not. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks_def.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.

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

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

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. By assigning a permission set that has View All on Leads to the contractor, Cloud Kicks can grant them view access to all lead records without modifying their profile or creating a new one. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.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.

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

Configure one app per department and activate record pages for each app is how the administrator should ensure this is configured correctly. An app is a collection of items that work together to serve a particular function for a group of users. An app can include items such as tabs, objects, reports, dashboards, and record pages. A record page is a type of Lightning page that displays details about a specific record. A record page can be customized using Lightning App Builder and activated for different apps, profiles, or record types. By configuring one app per department and activating record pages for each app, the administrator can ensure that the backup team users can view records in a way that makes sense for each department depending on which app they are using.

 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

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.

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

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

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 cross-filter lets you filter records based on related objects and their fields. For example, you can filter accounts that have at least one opportunity from this year and at least one completed activity in the last 30 days. References: https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm &type=5

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

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.

Paused flows can cause data to be saved in an unencrypted state because when a flow pauses, Salesforce saves its state and any data it has collected in a flow interview object, which is not encrypted by Shield Platform Encryption. References: https://help.salesforce.com/s/articleView? id=sf.security_pe_considerations_flows.htm&type=5

Validation rules and page layouts are two tools that can be used to require data to be entered in a field and improve data quality on a record in Salesforce. Validation rules are a way to enforce data quality and integrity by checking the values of fields before a record is saved and displaying an error message if the values do not meet the specified criteria. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Page layouts can also make fields required so that users must enter a value before saving a record.

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

A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce. A permission set can be used to extend users’ functional access without changing their profiles. You can assign permission sets to individual users or groups of users based on their business needs. In this case, you can create a permission set with Read access to the Government ID field on the custom object and assign it to the Institutional Team users who need access to this field via reports. References: https://help.salesforce.com/s/articleView? id=sf.perm_sets_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.perm_sets_create.htm &type=5

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

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

Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users’ access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.

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

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

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

Permission set groups are a combination of permission sets that grant users access to various tools and functions. Muting permission sets are used to remove access that is granted by other permission sets in the group. However, muting permission sets cannot remove object-level access that is granted by Modify All or View All permissions. Therefore, if a user is assigned to a permission set group that gives them Modify All access to Accounts, a muting permission set that mutes Delete access on Account will not have any effect. The user will still have Modify All access on the Account object, which includes Delete access. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_groups_muting.htm &type=5

Before installing a managed package from the AppExchange, the administrator should take into consideration several factors, such as:

Custom objects and custom fields used by the app count against the org’s limits. The administrator should check how many custom objects and fields are available in their org and how many are used by the app.

Apps may require certain Salesforce editions or features to be enabled. The administrator should check the app’s requirements and compatibility with their org’s edition and features.

Apps may require external, third-party web services to function properly. The administrator should check if the app integrates with any external services and if they need to set up any authentication or configuration for them.

The other two options are incorrect because:

Managed apps do undergo a formal security review by Salesforce before they are listed on the AppExchange.

Apps can be installed in a sandbox before they are installed in production.

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

Debug Log is a tool that captures information about database operations, system processes, and errors that occur when executing a transaction or running a unit test. Debug Log can help troubleshoot issues related to triggers, workflows, validation rules, or other custom logic by showing the order of execution and the values of variables and expressions

Bulk API and Dataloader.io are both tools that can be used to update large numbers of records in Salesforce. Bulk API is a RESTful API that allows you to create, update, delete, or query millions of records asynchronously by submitting batches of data. Dataloader.io is a web-based data loader tool that allows you to import, export, or delete data using a simple user interface. References: https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm https://dataloader.io/

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.v alidation_rules.htm&type=5

Email logs are files that provide information about email delivery and activity in your Salesforce org. Email logs contain details such as sender, recipient, subject, date, status, error code, and more for each email sent or received within a specified time range. You can use email logs to investigate issues with email delivery or performance in your org. In this case, you can use email logs to check if the status update emails were sent successfully or if there were any errors or failures. References: https://help.salesforce.com/s/articleView?id=sf.email_logs.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.email_logs_format.htm &type=5

Contacts to Multiple Accounts is a feature that allows administrators to relate a contact to multiple accounts without creating duplicate contacts for each account. This feature is useful for scenarios where a contact has business relationships with more than one account, such as consultants, brokers, or loan advisors. By setting up Contacts to Multiple Accounts for loan advisors at DreamHouse Realty, administrators can track which loan advisors work with which customers and which accounts without creating duplicate contacts for each account. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts_overview.htm &type=5

Cloning a sandbox creates a duplicate copy of an existing sandbox with the same type, name, description, configuration, and license type as the original sandbox. Cloning a sandbox is useful when you need to create multiple sandboxes with the same metadata and data for testing or development purposes. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_clone.htm &type=5

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

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

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

As explained in question 4, record types allow administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By using separate record types for rental and real estate opportunities, DreamHouse Realty can capture different client information on their opportunities using custom page layouts for each record type. The record types can also determine which sales processes and paths are available for each opportunity type. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

When a currency is added to an organization’s list of supported currencies, it cannot be deleted and once enabled, advanced currency management cannot be disabled are two considerations that AW Computing should be aware of prior to implementing this change to the existing system. Adding a currency to an organization’s list of supported currencies is an irreversible action that allows users to enter and view amounts in that currency for standard and custom objects that have currency fields. Enabling advanced currency management is also an irreversible action that allows administrators to define dated exchange rates for opportunities and opportunity products based on close dates or product dates instead of using static conversion rates

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

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

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

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

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

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

Lightning Usage App:

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

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

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

Analyze Button:

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

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

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

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

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

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

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

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

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

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

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.

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

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

Time-based workflows are a type of workflow that execute actions based on a specific time trigger, such as a certain number of days before or after a date field on a record. Time-based workflows can cause delays in processing because they are added to a queue and processed in one-hour batches. If the queue is large or the system is busy, the actions may not execute at the exact time they are scheduled. Therefore, time-based workflows can contribute to reaching the hourly limit for processing workflow time triggers. References: https://help.salesforce.com/s/articleView?id=sf.workflow_time_action_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_limits.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

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