Advanced-Administrator Questions and Answers

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

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.

Role hierarchy is a sharing mechanism that should be used to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers. Role hierarchy is a way to grant access to records based on the user’s position in an organization’s hierarchy of roles. Role hierarchy can grant users access to records owned by or shared with users below them in the hierarchy for objects that have organization-wide defaults set to Private or Public Read Only. By using role hierarchy, the administrator can ensure that directors can access opportunities owned by or shared with regional managers who report to them

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.

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

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

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

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

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

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

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.

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

To debug platform events in Apex code, you need to set a debug log on the Automated Process entity. This entity represents an automated process user that runs flows and processes in your org. By setting a debug log on this entity, you can capture the events that are published and consumed by your flow and Apex code, as well as any errors or exceptions that occur during the execution. References: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_debug.htm https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm &type=5

The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page. References: https://help.salesforce.com/s/articleView?id=sf.customize_layouts.htm &type=5

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

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.

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

Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than 100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records. Bulk API is an API that allows fast and parallel processing of large batches of records. References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm &type=5

Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.

B) Configure custom duplicate rules.

Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for contacts or other objects. References: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm &type=5

C) Create custom matching rules.

Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads. Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are detected for contacts or other objects. References: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm &type=5

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

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

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.

A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. A roll-up summary field can be used to count, sum, min, or max values from child records. You can create a roll-up summary field on an object that has a master-detail relationship with another object. In this case, you can create a roll-up summary field on Room that counts the number of Equipment records related to it. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_types.htm &type=5

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=sf.knowledge_categories.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_catego ry_visibility.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/artic leView?id=sf.data_importer.htm&type=5

Shield Platform Encryption is a Salesforce feature that allows you to encrypt sensitive data at rest while preserving critical platform functionality. It uses a combination of tenant secrets, encryption keys, and masking policies to protect your data. A field encryption policy is a set of rules that defines which fields are encrypted and how they are masked when displayed. A field encryption policy can be used to encrypt and mask the identification number field, except for the last two digits. References: https://help.salesforce.com/s/articleView?id=sf.security_pe_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_pe_field_encryption_policies.htm &type=5

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.

A custom summary formula is a formula that calculates values from summary fields in reports such as sum, average, min, max, etc. Custom summary formulas can use functions such as PREVGROUPVAL to compare values from different groups in reports. For example, to calculate the year-over-year change in dollar amount of opportunities, an administrator can create a custom summary formula that uses PREVGROUPVAL to compare the sum of amount from this year’s group with the sum of amount from last year’s group, and divide it by last year’s sum of amount. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_fields_summary_formulas.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_formulas_prevgroupval.htm &type=5

An after save flow is a type of flow that runs in the background after a record is saved and performs actions based on the record data or changes. An after save flow does not require user input or interaction and can be triggered by a record-triggered flow element or by an Apex trigger. In this case, you can create an after save flow that runs when a case record is updated and delivers status update email to customers based on certain criteria or conditions. References: https://help.salesforce.com/s/articleView?id=sf.flow_trigger_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigge r.htm&type=5

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

Person Account cannot be disabled is something that the administrator should consider before enabling Person Accounts. Person Accounts are a special type of accounts that allow storing information about individual people who are not associated with an organization or business account. Once Person Accounts are enabled, they cannot be disabled or removed from the org without contacting Salesforce support

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

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

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

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

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_obje ct.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

 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

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

Knowledge is a feature that allows administrators to create, manage, and share articles that provide information and solutions for common issues or questions. Knowledge articles can be searched by users using keywords or phrases.

To improve its customers’ ability to search for knowledge articles, UMS can use two options:

B) Create synonyms for specific search terms.

Synonyms are words or phrases that have the same or similar meanings, such as “TV” and “television” or “fix” and “repair”. By creating synonyms for specific search terms, administrators can ensure that customers can find relevant articles even if they use different words or spellings than the ones used in the articles. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_search_synonyms.htm &type=5

D) Promote specific search terms for specific articles.

Promoted search terms are keywords or phrases that administrators can associate with specific articles to boost their relevance and ranking in search results. By promoting specific search terms for specific articles, administrators can ensure that customers can find the most helpful or popular articles for their queries. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_search_promotion.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.reports_examples_joined.htm &type=5

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

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

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

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 can deploy a change set from the sandbox to production that includes the Amount field and all the custom profiles that need access to it. This way, you can update the field-level security settings for the field on each profile in one deployment. 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 options that the administrator should use to meet these criteria are:

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

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

The other two options are incorrect because:

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

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

Query and export the Account History object using Data Loader is how the administrator can acquire the field history data for analysis. Data Loader is a tool that allows administrators to import, export, insert, update, delete, or upsert records in Salesforce using CSV files. Data Loader can handle large data sets and complex data transformations. Data Loader can be used to query and export the Account History object, which stores the field history data for accounts, using SOQL statements. 

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

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/

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

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

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.

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

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

To 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

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

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. 

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.

Three reasons CK should utilize Data Categories when creating articles in Knowledge are:

Data Categories help organize the Knowledge base content displayed. 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 categories help you organize your articles by topic or criteria and make them easier to find and browse by your users or customers.

Data Categories provide a way to secure access to the Knowledge base content. 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 category visibility to control access to your articles based on their data categories and ensure that only relevant and appropriate content is displayed to different users or customers.

A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a document that provides information or answers to common questions or issues. A Knowledge article can be tagged to one or more data categories within each data category group that is assigned to its article type. This allows you to classify your articles by multiple criteria and make them searchable and accessible by different users or customers.

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

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

Delegated administrators in Salesforce are designated users who are given limited administrative privileges to assist system administrators without having full access to all administrative functions. The two functions they can typically perform, which align with the permissions available to delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users, resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have the ability to manage custom objects or perform extensive customization. These functions are reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify permission sets. This is also restricted to full administrators, as it involves controlling access at a granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can maintain security and control while also sharing some administrative workload.

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

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

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

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