Advanced-Administrator Sample Questions Answers

To automate the renewal process for service plans, AW Computing should configure a flow that will create the renewal based on the closed-won date and opportunity line items. A flow is a tool that can automate complex business processes by executing logic, interacting with Salesforce database, calling Apex classes, and guiding users through screens. A flow can be triggered by various events, such as when an opportunity is closed won. References: https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm &type=

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

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.

A validation rule and a stage guidance in Path are two features that can help ensure that users input a use case before moving the opportunity stage to qualified.

A validation rule is a formula that validates the data entered by users and prevents records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to check if the Use Case field is blank when the Stage field is changed to Qualified, and display an error message if so.

A stage guidance in Path is a feature that displays helpful information or tips for each stage of a sales process on an opportunity record page. In this case, adding the Use Case field to the stage guidance in Path can remind users to fill out this field before moving to the next stage.

The Security Health Check tool in Salesforce provides a detailed overview of an organization’s security posture, which includes information on how objects are shared externally. This tool is particularly useful for administrators who need to review and assess various security configurations, including the visibility of objects to external users.

Security Health Check:

This tool helps administrators quickly identify and manage risks related to security settings, including those pertaining to data sharing externally.

By using Health Check, administrators can access a report that shows the sharing settings of objects, allowing them to confirm if any objects have been shared as "Public" externally, which is crucial during an audit.

It provides insights into high-risk settings and areas where the configuration does not align with Salesforce security best practices, such as public access levels.

Use Case:

For an audit focused on understanding external access to objects, Security Health Check is the most appropriate choice because it gives a quick snapshot of how data sharing settings compare against Salesforce's recommended security baseline.

This can help AW Computing immediately identify which objects have broader public access than desired, addressing potential security vulnerabilities.

Incorrect options:

Setup Audit Trail: This tool tracks configuration changes within Salesforce over time, but it does not provide specific details about data sharing settings or external visibility of objects.

Session Security Settings: These settings control session policies and timeouts but are not related to object sharing or external visibility.

Object Manager: While Object Manager allows administrators to configure object-specific settings, it does not provide an overall view or quick audit of external sharing configurations.

The Dev Console Log Inspector is a tool that allows you to view and analyze debug logs in a graphical interface. Debug logs contain information about database operations, system processes, and errors that occur when executing a transaction or running unit tests. To troubleshoot a process builder, the administrator should look for event types beginning with FLOW in the event column. These event types indicate the start and end of a flow interview, as well as any flow elements, faults, or decisions that occur during the execution. References: https://help.salesforce.com/s/articleView?id=sf.code_dev_console_log_inspector.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.code_debug_log_event_types.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

 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

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.

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

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.

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.

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

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

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

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

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

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

The View Setup Audit Trail page lets you view the 20 most recent setup changes made to your org. You can also download a file of the last six months of setup changes. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_setup_audit_trail.htm &type=5

Formula field and Dynamic Forms should be created to meet the requirements because a formula field can be used to count the number of open opportunities over US$10,000 related to an account using a roll-up summary filter condition, and Dynamic Forms can be used to display or hide a component on an account page based on a visibility filter using the formula field value. References: https://help.salesforce.com/s/articleView?id=sf.customize_functions_i_z.htm

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.

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

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

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

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

Changing the record type of a record does not affect the record access of a user. Record access is determined by the organization-wide default, role hierarchy, sharing rules, manual sharing, teams, and ownership. Record type only affects the page layout and picklist values that are available for the record. Therefore, if a user has access to a record before changing its record type, they will still have the same access after changing its record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm &type=5

To limit data exports, especially for sensitive information, Export Data Settings in Salesforce are specifically designed to control user access to export data. These settings allow administrators to restrict who can export data from Salesforce, helping to protect sensitive information like bank accounts and Personal Identifiable Information (PII).

Export Data Settings:

Salesforce provides administrators with the ability to manage permissions related to data export functions. This includes restricting access to tools like Data Export, Data Loader, and Report Exports.

By limiting these permissions, administrators can control which users are allowed to export data, thereby reducing the risk of sensitive data, such as PII, being exported by unauthorized individuals.

This is particularly useful for ensuring that only designated roles or users can export data, as per the organization’s data security policies.

Specific Use Case for Sensitive Information:

In a scenario where the focus is on preventing unnecessary access to sensitive information, Export Data Settings directly target the ability to export data and can be customized based on the security needs of the organization.

By disabling or limiting export permissions for specific profiles or roles, AW Computing can better manage the risk associated with handling sensitive data.

Incorrect options:

Salesforce Platform Encryption: While it protects sensitive data at rest by encrypting fields and files, it does not control export capabilities or prevent users from exporting data.

Salesforce Shield: This suite includes event monitoring, encryption, and audit trail features, which enhance security but do not specifically limit export permissions.

Muted Permission Sets: These are used to restrict permissions in permission set groups but are not designed to manage or limit data export capabilities directly.

In conclusion, Export Data Settings offer the most precise control over data export capabilities in Salesforce, making it the best solution to meet the security department's requirement.

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

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

When deploying profiles using change sets, the field-level security settings are not included unless the fields themselves are also part of the change set. Therefore, the administrator should consider adding the new custom fields to change set 2 along with the profiles, or manually adjust the field-level security after deployment. References: https://help.salesforce.com/articleView?id=changesets_about_components.htm &type=5

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

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

A rich text component allows administrators to add custom text or images to a Lightning page. Conditional visibility allows administrators to control when a component is visible based on criteria such as field values or device type. By using these features, administrators can highlight Canadian customers as a potential challenge for fulfillment without modifying the page layout or creating a new record type. References: https://help.salesforce.com/articleView?id=sf.app_builder_components_rich_text.htm &type=5 https://help.salesforce.com/articleView?id=sf.app_builder_component_visibility.htm &type=5

One of the IDs in the batch referenced a record that was in the recycle bin because deleting records with Bulk API does not delete records permanently but moves them to the recycle bin. Therefore, if a record ID in the batch matches an existing record ID in the recycle bin, an ‘entity is deleted’ error will occur.

The most suitable tool to identify potential security risks associated with Lightning Web Components is the Health Check. Health Check allows Salesforce administrators to evaluate and monitor the security posture of their Salesforce org by comparing its settings against Salesforce's recommended security baseline. This feature provides visibility into settings like session security, password policies, and more, which can directly impact the security of custom apps using Lightning Web Components.

Health Check:

Salesforce Health Check examines various security settings in your Salesforce org and provides a score based on how closely your settings align with Salesforce's recommended security baseline.

By using this tool, administrators can identify vulnerabilities and see specific actions to remediate any security gaps found within the org.

Health Check is especially relevant when evaluating new custom applications and components since it can highlight areas that require tightening security to meet organizational standards.

Other options listed:

Master Encryption Keys is relevant for managing encryption but not directly for identifying security risks.

Salesforce Optimizer is used for overall performance and usage insights and doesn’t specifically focus on security assessments.

Self-signed Certificates are primarily used for secure communications and do not serve as a tool for security risk assessment.

Therefore, Health Check is the best tool to help the administrator expose potential security risks within the custom Lightning Web Components.

A managed package is a type of app that can be installed from the AppExchange. Managed packages are typically created by ISV partners or developers who want to distribute and sell applications that are upgradeable and have intellectual property protection. Before installing a managed package, an administrator should consider the following:

A) Custom objects and custom fields used by the app count against the org’s limits.

Managed packages may include custom objects and custom fields that are used by the app. These custom objects and custom fields count against the org’s limits and may affect the performance or functionality of the org. Administrators should review the components and requirements of the app before installing it and make sure they have enough space and resources for the app. References: https://help.salesforce.com/s/articleView?id=sf.packaging_limits.htm &type=5

C) Apps may require certain Salesforce editions or features to be enabled.

Managed packages may require certain Salesforce editions or features to be enabled in order to work properly. For example, some apps may require Lightning Experience, API access, custom permissions, or specific user licenses. Administrators should check the app’s description and documentation before installing it and make sure they meet the prerequisites for the app. References: https://help.salesforce.com/s/articleView?id=sf.packaging_install.htm &type=5

D) Apps may require external, third-party web services to function properly.

Managed packages may require external, third-party web services to function properly. For example, some apps may integrate with other platforms or systems such as Google Maps, PayPal, or Twilio. Administrators should check the app’s description and documentation before installing it and make sure they understand the implications and costs of using external web services. References: https://help.salesforce.com/s/articleView?id=sf.packaging_install.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://help.salesforce.com/s/articleView?id=sf.relationships_considerations_lookup.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

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

Confirm the object is marked as deployed and not in development is what the administrator should do to resolve the issue. A custom object can be marked as deployed or in development depending on its readiness for use. A custom object that is marked as in development is not visible to users or available for data import or export. A custom object that is marked as deployed is visible to users and available for data import or export. Therefore, the administrator should make sure that the new custom object is marked as deployed before using Data Loader to upload records to it

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.

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

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

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

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.

Upsert is an operation that can either update existing records or insert new records based on the External Id field. This way, the administrator can match existing leads and add new ones with Data Loader. References: https://help.salesforce.com/s/articleView?id=sf.data_loader_upsert.htm &type=5

To manage both B2C and B2B customers, CK should use Person Accounts and Contacts to Multiple Accounts features. Person Accounts allow CK to store information about individual consumers without requiring a separate account record. Contacts to Multiple Accounts allow CK to associate a contact with multiple accounts, such as their employer and their personal account. References: https://help.salesforce.com/s/articleView?id=sf.account_person_behavior.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account_contact_rel_overview.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

To access a junction object record, a user needs to have at least read permission on one of its master records and on the junction object itself. If the user does not have access to either master record, they cannot access the junction object record. If the user has access to both master records, they can access the junction object record with the most permissive access level of either master record. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.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

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

One possible cause of unexpected changes to record values is having multiple automation tools that update the same field on the same object. This can create conflicts and overwrite each other’s values. To resolve this issue, the administrator should consolidate automation tools and use only one tool per object and field combination. This can help avoid confusion and ensure consistent results. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/automation_considerations

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

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

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

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

The Campaign Member option is only available for Update when using Data Import Wizard. This means that you can use Data Import Wizard to update existing campaign members with new or modified information, but you cannot use it to create new campaign members from a spreadsheet. To create new campaign members from a spreadsheet, you need to use other tools such as Data Loader, Import Wizard for Leads and Contacts, or Manage Members button on the campaign page. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_members_adding_parent.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_importer.htm &type=5

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.

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

To create a training sandbox with 160MB of test data that needs to be refreshed every other day, NTO should use either Partial or Developer Pro sandboxes. Partial sandboxes have a storage limit of 10GB and can be refreshed every 5 days. Developer Pro sandboxes have a storage limit of 1GB and can be refreshed every day. Both sandboxes can include test data from production. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm &type=5

Escalation rules are rules that automatically escalate cases if they have not been resolved within a certain time frame or meet certain criteria such as priority or status. Escalation rules can perform actions such as changing ownership of cases, sending email notifications, or creating tasks for users or queues. By using escalation rules, AW Computing can ensure that cases are properly prioritized and handled within their SLA time limit.

Assignment rules are rules that automatically assign cases to users or queues based on criteria such as case origin, type, or product. Assignment rules can also send email notifications to users or customers when a case is assigned. By using assignment rules, AW Computing can ensure that cases are routed to the right agents or teams based on their skills and availability. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation_rules_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_caseassign.htm &type=5

A lightning action is a type of quick action that can invoke a Lightning component, a Visualforce page, or a URL. The administrator can use a lightning action to redirect the user to a different page after they finish the screen flow. This way, the user will not see the initial screen again and will not misuse the flow tool.

 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

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