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

As explained in question 4, record types allow administrators to offer different business processes, picklist values, and page layouts to differen t 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

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 cust omers 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

Use separate record types, page layouts, and sales processes for the Rental and Real Estate Teams is how the administrator should extend the Opportunity object to meet the teams’ different needs. Record types are a way to offer different business processes, picklist values, and page layouts to different users based on their profiles or permission sets. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Sales processes are a way to define the stages that an opportunity goes through from creation to close. By using separate record types, page layouts, and sales processes for each team, the administrator can customize the opportunity object according to their different requirements and preferences.

A price book is a list of products and their prices that can be added to an opportunity. A product can have different prices for different markets or segments, and these prices are stored in different price books. In this case, the administrator should create a new price book for the new retail pricing and add the products that are sold to retail locations for resale. This way, the users can select the appropriate price book and products for their opportunities based on the type of customer they are selling to. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.products_ define.htm & type=5

The error condition formula of a validation rule should return TRUE when the validation rule should fire and display an error message. In this case, the validation rule should fire when the Title field has the value of ‘CEO’ and the Phone field is blank . The formula Title = ‘CEO’ & & ISBLANK(Phone) returns TRUE when both conditions are met, and FALSE otherwise. References: https://help.sales force.com/s/articleView?id=sf.fields_useful_field_validation_formulas.htm & type=5

Identity verification history and login history are two areas that the administrator can review to understand potential root causes of mul ti-factor authentication issues. Identity verification history shows the methods and results of identity verification attempts for a user, such as email verification, SMS verification, or app verification. Login history shows the status, source, and locati on of login attempts for a user, as well as any login errors or challenges that occurred. These two areas can help the administrator identify if the user entered the correct verification code, if the user’s device or app is compatible with multi-factor aut hentication, or if there are any network or security issues that prevent successful verification. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.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

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 Ou tcome 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 c an 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

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 prereq uisites 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

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

Use a custom permission set that is assigned to the user because custom permissions are a way to grant access to custom processes or functionality based on user profiles or permission sets. Custom permissions can be referenced by Apex code, validation rules, flows, or other logic to control whether a process should run for a user or not. Custom permissions can be used to declaratively control process execution by assigning them to users or profiles.

Planning deployments around maintenance schedules ensures that there are no interruptions or delays in the deploy ment 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

Two practices that the administrator should adhere to in order to ensure a successful deployment to production are:

Add permissions and access settings to outbound change sets in addition to the dependent component list. This can help avoid deployment errors or access issues caused by missing permissions or settings for the components in the change set. For example, if the change set includes a new custom object, the administrator should also include the object permissions, field-level security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This can help test the change set for any errors or conflicts before deploying it to production. Deployment validations simulate the deployment without actually making any changes and report any issues or warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the change set. It can be deployed along with other components as long as they are compatible and have the required dependencies.

The Fields component is a Lightning component that allows administrators to display fields from a record on a Lightning page based on certain condition s 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

Workflow is the debug log category that should be used to troubleshoot an issue with a flow. Workflow is a debug log category that captures information about workflow rules, flows, processes, approval processes, and entitlement processes. Workflow can help identify errors or issues related to these automation tools by showing details such as evaluation criteria, actions executed, variables assigned, and outcomes reached.

Make a validation rule on the Opportunity Product object to require custom date fields based on the product family is how the administrator should ensure the data is captured properly. A validation rule is a way to enforce data quality and integrity

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.

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

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.

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 segm ent 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 acce ss 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 masking tool is a tool that allows you to mask sensitive data in your full sandbox by replacing it with fictitious data. This can help you protect your data privacy and comply with regulations while testing in a realistic environment. You can use the data masking tool to mask data for standard and custom objects, includ ing person accounts, and choose from different masking formats and options. References: https://help.salesforce.com/s/articleView?id=sf.data_mask.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

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, d ebug, 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

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

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 w hat values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm & type=5

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

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 tr igger 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

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. References: https://help .salesforce.com/s/articleView?id=sf.app_manager_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex _pages_assign.htm & type=5

The order in which record-triggere d flows are executed is not guaranteed. If there are multiple record-triggered flows on the same object and trigger type, Salesforce does not guarantee which one runs first. Therefore, the administrator should consider this when designing record-triggered flows that depend on each other’s outcomes. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm & type=5

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 vie w records in a way that makes sense for each department depending on which app they are using.

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.

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flo ws can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also have decision elements that evaluate conditions and determine which path to follow in the flow. By combining the two flows into one with decision elements, the administrator can ensure that the flow runs in the correct order and updates the field on the child record after it is created by the first flow. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts .htm & type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.htm & type=5

The 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 immediat ely and executes the action of sending the email

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 cr eation, updates, or invocations from other processes or flows. Flows can also send email alerts as part of their actions. To send a notification when a record is deleted and by whom, and to maintain their own discovery information, an administrator can use a flow that runs when a record is deleted, queries the record owner’s email address and discovery information from another object or variable, and sends an email alert with those details. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts.htm & type=5

A lookup relationship creates a link between two objects. The child object can have its own security settings and does not inherit them from the parent object. This is suitable for audit records that need to be preserved and accessed by a specific team. References: https://trailhead.salesforce .com/en/content/learn/modules/data_modeling/relationships

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

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. Refe rences: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.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

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

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:

A) Set up users and password management.

Delegated administrators can set up and manage users who belong to specified roles or territories, including creating, editing, freezing, and unlocking users; resetting passwords; assigning permission sets; and managing public groups. References: https://help.salesforce.com/s/articleView?id=sf.admin_useradmin_delegated.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_permissionsets.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.admin_useradmin_delegated.htm & type=5

To embed a r eport chart on a record page, you need to use a lightning component that displays report charts. You can filter the component visibility by setting conditions based on record fields, user attributes, or device type. In this case, you can filter the compone nt visibility by matching the Account ID field on the report chart with the Account ID field on the record page. This will ensure that only the relevant data for that account is shown on the chart. References: https://help.salesforce.com/s/articleView?id=s f.reports_embed_chart_lightning.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_set_component_visibility.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 y our 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.s ecurity_pe_field_encryption_policies.htm & type=5

To resolve the issue with the Process Builder, the administrator should do the following steps:

Review the Error Email for the Process Builder and rectify the issues. The error email contains information about what caused the error and how to fix it.

Deactivate the Process Builder in production. This will prevent further errors from occurring while the administrator fixes the Process Builder.

Fix the Process Builder in a sandbox and migrate the change to production. This will ensure that the Process Builder is tested and validated before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.flow_troubleshoot_error_email.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.flow_deploy.htm & type=5

The setup audit trail tracks the recent setup changes t hat 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

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by replacing it with fictitious data. This can help you protect your data privacy and comply with regulations while testing in a realistic environment. You can use the data masking tool to mask data for standard and custom objects, including person accounts, and choose from different masking formats and options. References: https://help.salesforce.com/s/ar ticleView?id=sf.data_mask.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

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.

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

Salesforce Optimizer is a tool that analyzes your Salesforce implementation across multiple features such as security health check scores, API usage limits, field usage, and more, and provides recommendations for improvement. Salesforce Optimizer can also scan your Lightning web components and identify potential security risks such as cross-site scripting (XSS) vulnerabilities, insecure content deliver y network (CDN) references, or missing locker service compatibility. References: https://help.salesforce.com/s/articleView?id=sf.optimizer.htm & type=5 https://hel p.salesforce.com/s/articleView?id=sf.optimizer_security.htm & type=5

To show forecast numbers by territory regardless of who owns the record, CK should enable Territory Forecast. To forecast b ased 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

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.

Chat must be routed with Omni-Cha nnel in Lightning Experience because Omni-Channel is the only way to route chats to agents in Lightning Experience 1 .  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 style 2 . 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

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 Lightni ng 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 runni ng. 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.salesforc e.com/s/articleView?id=sf.flow_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_changesets.htm & type=5

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

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.

REGEX is a function that allows administrators to check whether a text value matches a regular expression pattern. Regular expressions are a way to define complex patterns of characters using symbols and operators. REGEX can be used to enforce consistent formatting for a field value by specifying the required length, characters, and separators.

Two options that the administrator should check to ensure the product is available are:

Confirm the correct price book is selected on the opportunity. A price book is a list of products and their prices that can be added to an opportunity. An opportunity can have only one price book at a time, and the products that are available for selection depend on the price book that is chosen. Therefore, the administrator should check if the opportunity has the right price book that contains the new keyboard product.

Ensure the product is associated with the correct price book. A product is a good or service that can be sold in Salesforce. A product can be associated with one or more price books, depending on how it is priced for different markets or segments. Therefore, the administrator should check if the new keyboard product is added to the appropriate price book that is used by the opportunity.

The other two options are incorrect because:

Making custom fields does not affect the availability of products on an opportunity. Custom fields are used to store additional information or calculations on an object, but they do not determine which products can be selected from a price book.

Turning on field tracking does not affect the availability of products on an opportunity. Field tracking is used to monitor changes to certain fields on an object and display them in a history related list, but it does not determine which products can be selected from a price book.

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

When Contacts to Multiple Accounts is enabled, a contact must always be associated with a primary account, even if the account field is not required on the page layout. The primary account determines how the contact is shared and how roll-up summary fields calculate values from the contact records. To remove the primary account from a contact, the contact must be deleted or merged with another contact. References: https://help.salesforce.com/s/articleView? id=sf.relating_contacts_to_multiple_accounts.htm & type=5

An administrator should consider using Person Accounts when they have a B2C business model and the consumer is the intended recipient of sales and marketing attention. Person Acco unts allow administrators to store information about individual consumers without requiring a separate account record for each contact. References: https:// help.salesforce.com/s/articleView?id=sf.account_person_behavior.htm & type=5

The user profile permissions on the Opportunity object is the item that t he 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 d elete the record for them. References: https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm & type=5 https://help.salesforce.com/s/a rticleView?id=sf.admin_object_permissions.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 re sults. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm & type=5 https://trailhead.salesforce.c om/en/content/learn/modules/business_process_automation/automation_considerations

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

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 suc cessfully 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

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

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 resource s 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

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