CRT-211 Practice Exam Questions with Answers Prepare for your Advanced Administrator Certification Exam (SP25) Certification

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_a ctions_overview.htm&type=5

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

Three recommendations that the administrator can make to reduce the file size of full data exports are:

• Reduce the amount of objects per export. By selecting only the objects that are necessary for the backup and excluding the ones that are not, you can reduce the number of files and records that are exported and decrease the file size.
• Deselect ‘Include images, documents, and attachments’ in the export. By unchecking this option, you can exclude the files that are stored in Salesforce as images, documents, or attachments from the export. These files can take up a lot of space and increase the file size significantly.
• Keep deleted record counts to a minimum. By emptying the recycle bin regularly or using hard delete options, you can reduce the number of deleted records that are included in the export. Deleted records are still counted as part of the export limit and can increase the file size.

The other two options are incorrect because:

• Requesting a backup file every 5 days does not reduce the file size of each export. It only increases the frequency of exports and may cause more storage issues.
• Unselecting the recycle bin in the object export option does not reduce the file size of full data exports. It only applies to individual object exports and not to weekly or monthly exports.

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

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

Roll-up Summary calculations are performed after processes and workflows are executed, which means that any changes made by processes or workflows will not be reflected in the roll-up summary field until after the transaction is committed. This could cause inaccurate or outdated information to be delivered to the agent if the flow relies on the roll-up summary field value.

Setting a debug log on the Automated Process entity allows capturing information about platform events that are published or subscribed by flows or processes. This can help debug issues related to platform events and flows.

Workflow debug log category captures information about workflow rules, flows, processes, and actions that are executed as a result of a DML operation. References: 

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_t erritory_forecasts.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.forecasts3_enable.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/articleView?id=sf.bulk_api_intro.htm &type=5

A record type allows administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating a record type for the type of property (single-family home or condo), DreamHouse Realty can assign different page layouts to each record type that display only relevant fields for each property type. The record type can also determine which sales process and path are available for each opportunity. References: https://help.salesforce.co m/s/articleView?id=sf.customize_recordtype.htm&type=5

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

Identity Verification History is a tool that tracks the verification methods used by users when they log in to Salesforce via multi-factor authentication. It can help identify any issues or errors related to verification methods such as email, phone, or app. Login History is a tool that tracks the login attempts and status of users who access Salesforce. It can help identify any issues or errors related to login credentials, IP addresses, browser types, or locations.

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

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.repor ts_examples_joined.htm&type=5

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_fie lds.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.ht m&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm &type=5

A lookup relationship with Read/Write sharing setting is the recommended option to use when adding a field to Case Outcome custom object. A lookup relationship is a type of relationship that links two objects together and allows users to associate one record with another. A lookup relationship does not affect the security or deletion of either record and can be optional or required. In this case, you can create a lookup relationship field on Case Outcome object that references Case object and allows users to link multiple Case records to multiple Case Outcome records. You can also set the sharing setting for the lookup field to Read/Write, which means that users who have access to the parent record can also access and edit the child record. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5 https://he lp.salesforce.com/s/articleView?id=sf.relationships_considerations_lookup.htm&type=5

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

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

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

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

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

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

A delegated administrator is a user who has been granted limited administrative privileges by an administrator through delegated administration groups. Delegated administrators can perform some administrative tasks without having full access to Setup.

Some functions that delegated administrators can perform are:

• B) Build automation and validation rules using screen flows

Screen flows are types of flows that guide users through screens with elements such as text boxes, picklists, radio buttons, etc. Screen flows can also perform actions such as creating records, updating fields, sending emails, etc. Delegated administrators can build automation and validation rules using screen flows if they have been granted access to create and edit flows by an administrator. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_design_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_delegated_admins.htm &type=5

• D) Make updates to permission set configurations

Permission sets are collections of settings and permissions that can extend users’ functional access without changing their profiles. Delegated administrators can make updates to permission set configurations if they have been granted access to manage users by an administrator. References: https://help.salesforce.com/s/articleView?id=sf.users_permis sionsets.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_useradmin_delegated.htm &type=5

Data categories and visibility are features that allow you to organize and control access to your Salesforce Knowledge articles based on different topics or criteria. Data categories are logical groupings of articles that reflect your business needs and processes. You can create a data category group and assign it to one or more article types, and then create data categories and subcategories within that group. Data category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data categories and visibility to provide relevant and appropriate product documentation to your customers and support team. References: https://help.salesforce.com/s/articleView?id=s f.knowledge_categories.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_category_visibility.htm &type=5

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

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

To 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

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

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

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

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

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

A high assurance session is a type of session security level that requires users to verify their identity using a second factor of authentication, such as Salesforce Authenticator, a verification code, or a security key. Administrators can configure certain actions or permissions to require a high assurance session, such as exporting reports, viewing encrypted data, or accessing connected apps.

If users are able to run reports but are taken to a login screen and prompted for additional verification when they try to export a report, it could be because exporting is configured to require a high assurance session. This means that users need to use a second factor of authentication to export reports, even if they have already logged in with their username and password. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_sessions.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

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.

One possible reason why the before trigger fails is that the code could be trying to create duplicates in the archive when it is unable to. A before trigger is a type of trigger that executes before a record is saved and can be used to validate or modify record data. In this case, the before trigger is supposed to save the original version of a record to an external database before it is updated or deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try to create duplicate records in the external database when it is not allowed or possible. This could cause the trigger to fail and prevent the record from being saved in Salesforce. References: https://develop er.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_context_variables.htm

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

Another quote is already synced with the opportunity will prevent a user from syncing a quote with an opportunity. Only one quote can be synced with an opportunity at a time. If a user tries to sync another quote, they will get an error message saying that the opportunity already has a synced quote. References: https://help.salesforce.com/s/articleView?id=sf.quotes_syncing.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.sale sforce.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

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

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

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.co m/s/articleView?id=sf.products_pricebooks_def.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.

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_manytomany.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.

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

Export Data Settings is a feature that allows you to control which users can export data from Salesforce and how much data they can export at a time. You can enable or disable the Export Reports permission for different profiles or permission sets, and set a maximum number of records that can be exported per hour for your org. You can also restrict the export of sensitive data by using field-level security or encryption. References: https://help.salesforce.com/s/articleView?id=sf.admin_exportdata.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.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

The best way to keep secure fields protected in email templates is to remove them from the email altogether. Classic encrypted fields are not supported in email templates, and implementing GDPR or setting up an approval process for email alerts do not prevent unauthorized users from viewing sensitive data in emails. References: https://help.salesforce.com/ articleView?id=security_pe_classic_encryption_considerations.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

The Highlights Panel is a Lightning component that displays key information about a record at the top of the page. You can customize the Highlights Panel to show different actions based on the record type or other criteria. In this case, you can define dynamic action buttons for the Planet object that appear only if the gaseous field is true or false. This way, you can show different actions for different types of planets. References: https://help.salesforce.com/s/articleView?id=sf.lex_page_layouts_highlights_panel.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.dynamic_actions_considerations.htm &type=5

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/article View?id=sf.dashboard_filters.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.

Flows deployed with change sets are inactive by default and need to be manually activated in the destination org before they can run. Deploying or redeploying a flow with change sets creates a new version of the flow in the destination org, which preserves the previous versions and allows for rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are automatically added to the change set when a flow is added

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

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

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

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

The field is being updated by a workflow field update is why records are being updated with data that violates the validation rule. A workflow field update is a way to automatically change the value of a field when a workflow rule evaluates to true. A workflow field update can bypass validation rules and other security controls when updating a field value, which can result in invalid data being stored in the record.

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

 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.

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

A row-level formula is a formula that evaluates each row in a report and returns a value based on one or more fields in that row. A row-level formula can be used to create a new column in a report that indicates whether the case subject contains the words ‘Alpha Shoe’ or not. References: https://help.salesforce.com/s/articleView?id=sf.reports_row_level_formulas.htm &type=5