Salesforce ADM-201 Salesforce Certified Administrator (SP23) Exam Practice Test

Running the flow using it to create contacts and using debug to test the flow in Flow Builder are two key components of testing a new screen flow that creates contacts. Running the flow allows the administrator to see how the flow behaves in real time and check for any errors or unexpected results. Debugging the flow allows the administrator to simulate how the flow runs with different inputs and outputs and check for any logic or syntax errors. Setting up a flow interview or testing the flow in a sandbox are not necessary for testing a screen flow that creates contacts. References: https://help.salesforce.com/s/articleView?id=sf.flow_test.htm &type=5

To track shoe designs by products, prevent them from being deleted, and allow multiple designs for one product across various stages, the administrator should create a custom object for shoe designs and configure a custom lookup field for shoe designs on the Product object. This will create a one-to-many relationship between products and shoe designs, and allow users to link multiple shoe designs to one product record. To prevent shoe designs from being deleted, the administrator can use validation rules or permissions. Adding a custom master-detail field for shoe designs on the Product object will create a many-to-one relationship, which is not desired. Using the standard object for designs or configuring a validation rule will not meet the requirement. References: https://help.salesforce.com/s/articleView?id=sf.customize_object_relationships_overview.htm &type=5

Einstein Opportunity Scoring is a feature that helps sales reps prioritize and close more deals by assigning each opportunity a score from 1 to 99 based on how likely it is to be won. The score is calculated using artificial intelligence and machine learning based on historical data and patterns from similar opportunities. Sales reps can use the score to focus on high-value opportunities and take actions to improve low-scoring ones. References: https://help.salesforce.com/s/articleView?id=sf.einstein_sales_oppty_scoring.htm &type=5

Two considerations when installing a managed package in a sandbox are:

• The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
• The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5

Flow Builder supports creating a scheduled flow that can run at specified intervals and perform actions on a set of records that meet certain criteria.

References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_scheduled_start.htm &type=5

Field update and email alert are two types of automated actions that can be added as part of the approval process. Field update allows you to change the value of a field on a record when it is submitted, approved, rejected, or recalled. Email alert allows you to send an email to one or more recipients when a record is submitted, approved, rejected, or recalled.

References: https://help.salesforce.com/s/articleView?id=sf.approvals_automated_actions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_creating_approval_actions.htm &type=5

Forecasting is a feature that allows you to predict and plan the sales cycle from pipeline to closed sales, and manage sales expectations throughout your organization. Opportunity stages are the steps that an opportunity goes through as it moves from creation to close, and they determine the probability and forecast category of the opportunity. References: https://help.salesforce.com/s/articleView?id=sf.forecasting3_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_opptystages.htm &type=5

There are two possible reasons why users are unable to access a report based on a custom report type created by an administrator. One is that the custom report type is in development mode, which means that it is not deployed and available for use by other users except for administrators and users with manage custom report types permission. The other is that the report is saved in a private folder, which means that it is visible only to its owner and not shared with other users or groups. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_custom_report_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_folders.htm &type=5

Custom object and master detail field are two steps that should be configured to meet this requirement. Custom object can be used to create a new object for shoe design that can store information about different designs and stages. Master detail field can be used to create a relationship between Product and Shoe Design that prevents deletion of Shoe Design records and allows multiple designs for one product. References: https://help.salesforce.com/s/articleView?id=sf.customize_customobjects.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Probability is a standard percentage field on the Opportunity object that indicates how likely an opportunity will close successfully. It is automatically calculated based on the opportunity stage unless you make it editable on page layouts. To allow sales reps to change the probability field value of their opportunities, you need to make the field editable on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.opportunity_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5

Grant access using Hierarchies is a setting that can be used to configure the custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_custom_objects.htm &type=5

Process Builder is a tool that can be used to automate business processes by creating record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can be used to create a flow that executes when an opportunity is closed won and creates a client welcome task and a welcome email for the primary contact. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5

App page and record page are two types of pages that an administrator can build and customize using Lightning App Builder for Salesforce mobile app. App pages are pages that display information or tools that don’t belong to a specific record; they can be accessed from navigation menus or tabs in Salesforce mobile app. Record pages are pages that display information or actions related to a specific record; they can be accessed by opening any record in Salesforce mobile app. User page and dashboard page are not types of pages that can be built using Lightning App Builder for Salesforce mobile app; they are types of pages that can be built using other tools such as Profile settings or Dashboard Builder. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_mobile_pages.htm &type=5

To make sure that all of the Salesforce users log in using the branded login URL after deploying my domain, and give them a grace period for updating their bookmarks, the administrator should set the Redirect policy to Redirect with a warning to the same page within the domain. This will redirect users who try to log in from https://login.salesforce.com or another domain to https://nto.my.salesforce.com, and show them a warning message that they need to update their bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not redirect users or give them a warning. Filtering with Form Factor will not affect login URL. References: https://help.salesforce.com/s/articleView?id=sf.domain_mgmt_redirect.htm &type=5

Minimum password length and password complexity requirement are two settings that administrators can configure to increase the security of user passwords in Salesforce. They determine how long and how complex the passwords must be to meet the security standards. Password different than username and prevent common words are not valid settings in Salesforce, although they are good practices for creating strong passwords. References: https://help.salesforce.com/s/articleView?id=sf.admin_password_policies.htm &type=5

A cross object formula field is a type of formula field that references fields from related objects using relationships such as lookup or master-detail. It can be used to display data from one object on another object without creating another relationship or copying data. A cross object formula field can be created on opportunity object to display data from industry field on account object using account ID lookup relationship. A custom account field, a standard account field, or a master-detail relationship field are not types of fields that can display data from industry field on account object on opportunity page layout; they either do not exist or do not reference related objects. References: https://help.salesforce.com/s/articleView?id=sf.cross_object_formulas.htm &type=5

Page layout editor is a tool that allows you to customize the layout and organization of detail and edit pages for a specific object and record type combination. You can also use page layout editor to customize related lists on detail pages by adding or removing fields, changing column order, sorting records, etc. To meet the requirement of showing different fields on the Case related list from the Account record for Sales and Customer Care users, you need to use page layout editor to modify the related list properties for each page layout assigned to those users. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutrelatedlists.htm &type=5

To test the impact of a critical update before it is auto-activated, you should activate it in a sandbox first. This way, you can verify that your customizations and integrations work as expected without affecting your production org.

References: https://help.salesforce.com/s/articleView?id=sf.admin_critical_updates.htm &type=5

To save time and budget, you can check the AppExchange for prebuilt solutions that can be easily customized for your needs. AppExchange is a marketplace for apps, components, and consulting services that extend Salesforce functionality.

References: https://appexchange.salesforce.com/

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can require users to select a product type or check a needs review box when saving an opportunity by using an OR function that evaluates both fields. If neither field is populated, then the validation rule will prevent users from saving records with an error message. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

Path is a feature that can be used to visually see the sales stages on an opportunity page. Path can include guidance and key fields for each stage to help users move opportunities along the sales process. Guidance can provide tips, policy information, or best practices for each stage. Key fields can display important fields that users need to fill in or update for each stage. References: https://help.salesforce.com/s/articleView?id=sf.path_overview.htm &type=5

Record types are a way to assign different page layouts and picklist values to different users based on their business needs. To use two different page layouts for customer and partner accounts, create one record type for each account type and assign them to the appropriate page layouts and profiles. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

The Knowledge Lightning component is a component that allows users to access articles from the Service Cloud Console app. However, if users want to access articles from a different app that does not use the console, they can use the Knowledge related list instead. The Knowledge related list shows articles related to a record based on data categories and shows article details such as title, summary, rating, and view count. To add the Knowledge related list to a record page, an administrator can use the page layout editor and drag and drop the Knowledge related list to the appropriate section on the page layout. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_lightning_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.htm &type=5

Fault connector and screen component are two features that can be used to address the issue of users seeing error messages when they use one of their screen flows. Fault connector can be used to handle errors that occur when a flow element fails, such as a record create or update element. Screen component can be used to display a message to the user with text explaining what went wrong and how to correct it. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_display_text.htm &type=5

Case escalation rules are used to escalate cases that have not been resolved within a certain time frame by changing the case owner, sending email notifications, or triggering workflow actions. You can use these actions to alert the appropriate users or groups when a case needs urgent attention or escalation. References: https://help.salesforce.com/s/articleView?id=sf.customize_caseesc.htm &type=5

Flow Builder is a tool that can be used to create an automated way to delete records based on field values. Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm &type=5

To surface important values based on stage of opportunity , an administrator should use Path Key fields feature on Opportunity object . This feature allows adding up to five fields that display key information about each stage along path . Users can edit these fields inline without leaving path . For example , an administrator can add Amount , Close Date , Next Step , Probability , and Stage fields as key fields for Opportunity path . Opportunity Processes , Dynamic Forms , and Workflow Rules are not tools for surfacing important values based on stage of opportunity . References : https :// help . salesforce . com / s / articleView ? id = sf . lex_path_setup_key_fields . htm & type = 5

To enable record sharing and collaboration with groups, you need to add the groups related list to the object layouts and configure the Add Record action in the group publisher.

References: https://help.salesforce.com/s/articleView?id=sf.collab_groups_records.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.collab_groups_record_actions.htm &type=5

Delegated approver is a feature that should be used to fulfill this requirement. Delegated approver allows users to delegate their approval authority to another user for a specified period of time, such as when they are out on vacation. Users can specify which approval requests they want to delegate and who they want to delegate them to. References: https://help.salesforce.com/s/articleView?id=sf.approvals_delegate.htm &type=5

Screen flow allows you to create a form that collects user input and performs actions based on that input. You can use screen components to display questions and instructions, and use flow logic to update records or send notifications.

References: https://trailhead.salesforce.com/content/learn/modules/screen-flows/get-started-with-screen-flows https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5

Themes are a way to customize the look and feel of Salesforce by changing the colors, images, and logos that appear on Lightning Experience pages. However, there are some limitations and considerations when using themes, such as: only one theme can be active at a time, and a theme applies to the entire org; themes apply only to Lightning Experience and do not affect Salesforce Classic or the Salesforce mobile app; up to 300 custom themes can be created, modified, or cloned from the built-in themes; Chatter external users see the built-in Lightning theme only and cannot see custom themes. References: https://help.salesforce.com/s/articleView?id=sf.themes_overview.htm &type=5

Creating a dashboard with the running user set as someone who can see all opportunities is a way to create an enterprise-wide dashboard of all open opportunities in the pipeline without changing any sharing settings. The running user determines what data is displayed on the dashboard based on their access level and permissions; if the running user can see all opportunities, then the dashboard will show all opportunities regardless of who views it. Updating the dashboard folder settings to manager for the sales reps role does not create an enterprise-wide dashboard; it only controls who can access the dashboard folder, not what data is displayed on the dashboard. Adding a filter to the dashboard to filter the opportunities by owner role does not create an enterprise-wide dashboard either; it only shows opportunities owned by users in certain roles, not all opportunities. Building individual dashboards for profiles that need to see the enterprise results is not a feasible solution; it would require creating multiple dashboards for different profiles and maintaining them separately, which is inefficient and redundant. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_running_user.htm &type=5

To make it easy for approvers to respond to approval requests, the administrator should configure three settings:

• Update the organization’s chatter setting to allow approvals, which enables approvers to approve or reject requests from chatter feeds or email notifications
• Enable the organization’s Email approval response setting, which allows approvers to reply to approval request emails with keywords such as APPROVE or REJECT
• Add the Items to approve component to the approvers home page, which shows a list of pending approval requests that can be acted upon with one click Specifying initial submission actions within the approval process will not affect how approvers respond to requests. Creating a flow to automatically approve all records will bypass the approval process altogether. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_email.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_one_click.htm&type=5

Record types allow you to update the options in a picklist based on the kind of opportunity.

References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

To debug a screen flow that creates contacts, one of the possible causes for a variable missing on the debug screen is that the available for input checkbox was unchecked for that variable. This means that variable cannot be set by external sources such as debug inputs or URL parameters. To fix this issue, check this checkbox for any variable that needs to be set externally. The flow version or field type does not affect variable availability for input. The available for output checkbox only affects whether variables can be passed out of flows or subflows. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_variables.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_debugging.htm &type=5

To customize the campaign member status picklist values themselves, marketing users need two things: a marketing user feature license and edit permission for campaigns. A marketing user feature license enables users to create, edit, and delete campaigns; manage campaign members; and update campaign history via the import wizards or API. Edit permission for campaigns allows users to modify existing campaigns and their related records such as campaign members and campaign member statuses. References: https://help.salesforce.com/s/articleView? id=sf.campaigns_enable.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.htm &type=5

Two functions that an administrator should use when creating a validation rule are:

• Error condition formula, which defines when an error should occur based on record fields and values
• Error message location, which specifies where on the page layout an error message should appear when triggered by an error condition formula Formula return type and rule active date are not functions used for validation rules. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm&type=5