ADM-201 Sample Questions Answers

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

A user with manager role above the agent can change ownership on multiple cases that are owned by the agent or by users below the agent in the role hierarchy. A user with the System Administrator profile can change ownership on any case, regardless of the owner or role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.case_change_owner.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_userperms.htm &type=5

Get Records is a flow element that allows you to retrieve one or more records from an object that meet certain conditions and store them in a collection variable or a record variable for use later in the flow. You can also choose which fields from those records you want to store in variables. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_data_getrecords.htm &type=5

To advertise on TV, radio, print, and social under one banner called New Runners and aggregate total statistics for this marketing effort, an administrator should use Parent campaign field on Campaign object. This field allows creating hierarchical relationships between campaigns by specifying one campaign as parent of another campaign. Parent campaigns roll up statistics from child campaigns such as number of leads generated, amount of revenue won etc. For example, an administrator can create four child campaigns for TV, radio, print and social ads respectively and link them to one parent campaign called New Runners using Parent campaign field. Junction object, lookup relationship, and master-detail relationship are not features related to Campaign object or hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_parent.htm &type=5

A validation rule is a tool that allows administrators to enforce data quality and integrity by preventing users from saving records that do not meet certain criteria or conditions. For example, a validation rule can display an error message if a user enters an invalid value in a field. In this case, the administrator can create a validation rule on the account object that displays an error if the account annual revenue field is below 0 or greater than 100 billion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

Process Builder is an automation tool that allows you to create processes that perform actions based on criteria that you specify. You can use Process Builder to update fields on related records when a record is created or updated. To meet the requirement of updating the parent object Referral when the Referral Date field is updated on the custom object Referral Source, you need to create a process that triggers when a Referral Source record is updated, checks if the Referral Date field has changed, and updates the Referral Date field on the related Referral record. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

The $Record global variable allows you to reference the values of the active record the flow is running on.

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

To surface important values based on the stage of the opportunity, the administrator should use path key fields that display fields relevant to each stage along with guidance for success. Path key fields can be customized for each stage and can help users focus on key information and actions as they move opportunities through the sales process. Dynamic forms, opportunity processes, and workflow rules are not designed to show values based on stages. References: https://help.salesforce.com/s/articleView?id=sf.path_key_fields.htm &type=5

Component visibility allows you to restrict the visibility of a related list based on a permission set.

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

The AppExchange is an online marketplace where customers can find apps, components, consultants, developers, and more to extend Salesforce functionality or solve specific business challenges. Some of the actions that can be accomplished via AppExchange are finding certified developers and consultants who can help with custom development or implementation projects; installing industry-specific solution templates that provide preconfigured apps, dashboards, reports etc., for various industries such as manufacturing or healthcare; downloading free tools or components that enhance productivity or user experience; browsing reviews or ratings from other customers who have used certain products or services; etc. References: https://appexchange.salesforce.com/

Case escalation rules are a way to automatically escalate cases that meet certain criteria, such as being open for more than a specified time or having a certain priority. Escalation rules can assign cases to a different owner or queue and send email notifications to the support manager or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5

Lightning pages are custom layouts that let you design pages for your Salesforce org using Lightning App Builder. You can assign different Lightning pages for different apps, record types, and profiles using Lightning page assignments. To meet the requirement of displaying different Lightning pages for Accounts in Sales Console and Service Console, you need to assign Lightning pages as app default for each app. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_assignments.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

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

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.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

Data Export Wizard allows administrators to export data from Salesforce in CSV files. It can be used to export data for backup purposes or to analyze data in external tools. Data Import Wizard is used to import data into Salesforce, not export. Data Loader is a desktop tool that can also export data, but it is more complex and requires installation. Report Builder is used to create reports in Salesforce, not export data. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm &type=5

A Chatter private group is a type of Chatter group that allows members to share feedback and ideas with each other in a secure and exclusive space; only members can see and post in a private group. It can be used by Ursa Major Solar to create a space for product owners to collaborate with just the product team by creating a Chatter private group and adding product owners as members. Using quick actions to log communication, configuring a Chatter public group, or adding activity history to document tasks are not solutions for creating a space for product owners to collaborate with just the product team; they either do not provide privacy or do not support collaboration. References: https://help.salesforce.com/s/articleView?id=sf.collab_groups_overview.htm &type=5

A support process is a feature that allows administrators to define and enforce the stages that a case or work order must go through based on its record type. A support process determines which values are available for the status field for each record type. If a support process omits a certain value for the status field, such as Closed, then users will not be able to see or select that value when working with cases or work orders of that record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthome.htm &type=5

Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

Dashboards show data from source reports as visual components that provide a snapshot of key metrics and performance indicators. Dashboards need to be refreshed manually or scheduled to run on a regular basis to reflect the most recent data from the reports. The running user of a dashboard determines whose security settings are applied when the dashboard is run. If the running user is different from the viewer of the dashboard, they may see different data based on their permissions and sharing settings. References: https://trailhead.salesforce.com/en/content/learn/modules/lex_implementation_dashboards_and_reports/dashboards

Flow Builder and Process Builder are two automation tools that should be used to accomplish this request. Flow Builder can be used to create a flow that defines the logic and actions for creating a renewal opportunity, such as setting the stage, close date, and amount. Process Builder can be used to create a process that triggers the flow when an opportunity is closed won. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

Dynamic dashboards allow you to display data according to the security settings of the running user. If users have different access levels to data on dashboards, you can use dynamic dashboards to show them only what they are allowed to see.

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

Role hierarchy and sharing rules are two features that should be used to open up access to Opportunity records for sales users working on collaborative deals. Role hierarchy can be used to grant access to records owned by or shared with users who are below them in the hierarchy. Sharing rules can be used to extend sharing access to users in public groups, roles, or territories based on certain criteria, such as record owner or field value. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm &type=5

A criteria-based sharing rule is a tool that allows administrators to share records with certain users based on field values rather than ownership. For example, a criteria-based sharing rule can share all opportunities with a cross-sell opportunity type with a specific group of users. A public group is a collection of individual users, roles, roles and subordinates, or other groups that can be used to simplify sharing settings and other processes. In this case, the administrator can add the subject matter experts to a public group and give them access to records with a criteria-based sharing rule that matches the cross-sell opportunity type. References: https://help.salesforce.com/s/articleView?id=sf.sharing_criteria_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.public_groups.htm &type=5

To access the account object in Salesforce, users need to have permission to the account object on their profile or permission set. Permission to an object determines what users can do with records of that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission to an object, they will not be able to see or access that object in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm &type=5

A junction object is a type of custom object that allows administrators to create many-to-many relationships between two other objects. A many-to-many relationship means that each record of one object can be related to multiple records of another object, and vice versa. For example, a junction object can represent that a contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

Campaign influence is a feature that allows users to track how campaigns have influenced opportunities and measure the return on investment (ROI) of marketing efforts. Users can see which campaigns have influenced an opportunity on the related list and assign different attribution models to calculate the campaign influence. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_influence.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

Master-detail lookup is a type of relationship field that can be used to create a relationship between Account and Shoe and prevent orphaned Shoe records. Master-detail lookup establishes a parent-child relationship between two objects, where the parent record controls certain behaviors of the child record, such as security, ownership, and deletion. If the parent record is deleted, all the child records are deleted as well. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Two options that should be added to Lightning record pages to make sales reps aware when they are speaking with high-profile customers are:

• Custom Component, which can display a custom message or icon on the record page based on certain criteria such as account rating or industry. For example, an administrator can create a custom Lightning Web Component that shows a star icon on account record pages if account rating is Hot or Warm.
• Component Visibility Filter, which can control when a component is visible on a record page based on field values of that record. For example, an administrator can add a component visibility filter to an existing component such as Path or Highlights Panel that makes it visible only if account rating is Hot or Warm. Highlight Panel, Action and Recommendations, and Rich Text Area are not options that can be used to make sales reps aware when they are speaking with high-profile customers. References: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.htm&type=5

To track all cases that reference the new product and give read/write access to the product’s two lead engineers, the administrator should create a queue and a criteria-based sharing rule. The queue will allow assigning cases that meet certain criteria, such as having a specific value in the Product field, to a group of users. The criteria-based sharing rule will grant read/write access to the queue members for cases that match the same criteria. References: https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_criteria.htm &type=5

Component visibility filters are a way to make the record pages more dynamic and easier to use by showing or hiding components based on certain criteria. For example, users can see different components based on their profile, role, record type, or field values. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_component_visibility.htm &type=5

A sales process is a set of stages that an opportunity goes through as it moves from creation to close. It can be customized by administrators to match different business models or product lines within an org. Creating a new sales process can help Dreamhouse Realty define a different set of stages for its new home concierge offering that is unlike anything the company has offered in the past and follows a different business model. Creating a quick action, a new approval process, or a new opportunity product are not solutions for creating a customized sales process; they are used for different purposes such as creating records, approving records, or adding products to opportunities. References: https://help.salesforce.com/s/articleView?id=sf.customize_salesprocess.htm &type=5