Salesforce-Certified-Administrator Salesforce Certified Administrator (SU24) Questions and Answers

Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.

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

Two-factor authentication requires users to verify their identity with two pieces of information when they log in to Salesforce. One piece is their username and password, and the other is a verification code from an authenticator app or email or SMS.

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

Dependent picklist and global picklist are two options that can be used to meet this requirement. Dependent picklist allows users to cre ate a conditional relationship between two picklist fields, where the available values in one field depend on the value selected in another field. Global picklist allows users to create a set of picklist values that can be shared across multiple fields and objects, ensuring consistent values and reducing maintenance. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_dependent_picklists.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.picklist_global_picklists.htm & ty pe=5

Flow Builder supports creating a screen that can launch a simple discount calculator when a button is clicked on an opportunity.

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

Default language and currency locale are two options that an administrator should configure in the company settings to support a global team of Salesforce users. Default language determines the language that is used for labels, buttons, tabs, help text, and messag es in Salesforce for all users unless they override it in their personal settings. Currency locale determines the format of currency fields and numbers in Salesforce for all users unless they override it in their personal settings or enable multiple curren cies. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.ad min_supported_currencies.htm & type=5

A junction object is a type of custom object that allows administ rators 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

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 escala tion. References: https://help.salesforce.com/s/articleView?id=sf.customize_caseesc.htm & type=5

Security Health Check is a tool that can be used to identify and fix potential session vulnerabilities. Security Health Check scans the security settings in an org and compares them to a baseline set of standards, such as the Salesforce Baseline Standard or the Salesforce Optimized Standard. Security Health Check provides a health check score and a list of issues and recommendations for improving the security settings. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm & type=5

A restricted picklist is a type of picklist that enforces the integrity of the picklist values by allowing only values defined in the pick list during data entry or import operations. If the restricted picklist checkbox is checked for a picklist field, then any records with values not defined in the picklist will cause errors during import operations. However, if the restricted picklist check box is unchecked for a picklist field, then any records with values not defined in the picklist will be imported without errors. References: https://he lp.salesforce.com/s/articleView?id=sf.picklist_limitations.htm & type=5

To identify new leads entered by interns from existing leads, the administrator should define a record type and assign it to the interns. This will allow them to select a different record type when creating leads, and distinguish them from other leads based on record type. Creating a separate Lead Lightning Ap p or updating the active Lead Assignment Rules will not affect lead identification. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm & t ype=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 regul ar 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 d ata based on their permissions and sharing settings. References: https://trailhead.salesforce.com/en/content/learn/modules/lex_i mplementation_dashboards_and_reports/dashboards

The mass transfer tool allows you to transfer up to 250 records at a time from one user to another user while keeping the existing team member s intact. You can access this tool from Setup by entering Mass Transfer Records in the Quick Find box. References: https://help.salesforce.com/s/articleView? id=sf.mass_transfer_overview.htm & type=5

When an administrator deletes a custom field, Salesforce moves it to the deleted fields list for 15 days, during which time it can be undeleted or erased permanently. If the administrator undeletes the field within 15 days, most of its properties and data are restored, except for its field history data, which remains deleted and cannot be recovered. References: https://help.salesforce.com/s/ar ticleView?id=sf.custom_field_delete.htm & type=5

A lookup relationship is a type of relationship that links two objects together, but does not affect security or deletion. It can be used to create a relationship between shipments and accounts where shipments should have a lookup to accounts; this way, shipments can show related account in formation on their records, but when an account is deleted, the shipments remain. Accounts should have a lookup to shipments is not a valid option because it does not match the requirement of seeing all shipment items from an account page; it would show re lated account information on shipment records instead. Shipments should have a master-detail to accounts or accounts should have a master-detail to shipments are not valid options either because they do not match the requirement of keeping shipments when a n account is deleted; they would delete shipments along with their master account records. References: https://help.salesf orce.com/s/articleView?id=sf.relationships_lookup.htm & type=5

Picklist values, help text, and decimal places are three aspects of standard fields that an administrator can customize to suit their business needs. Picklist values are th e options that users can choose from a picklist field; they can be added, edited, or deleted by administrators. Help text is the text that appears when users hover over a field; it can be customized by administrators to provide additional information or gu idance for users. Decimal places are the number of digits that appear after the decimal point in a number or currency field; they can be changed by administrators to adjust the precision of the field values. Field history tracking and field name are not as pects of standard fields that can be customized; they are only available for custom fields. References: https://help.salesforce.com/s/articleView?id=sf.customize_picklists.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_edit.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_ number.htm & type=5

To share report fo lders with different groups of users with different levels of access, an administrator can use folder sharing settings under setup. Folder sharing settings allow administrators to share report folders with public groups, roles, roles and subordinates, terr itories, or portal roles with view or edit access. In this case, the administrator can share the Helpdesk folder with Support Agents with view access so they can run Helpdesk reports but not edit them; and share the R & D folder with Support Managers with ed it access so they can view and edit R & D reports. References: https://help.salesforce.com/s/articleView?id=sf. reports_builder_folders_sharing.htm & type=5

To route new leads to the correct sales person based on the lead address, the administrator should use lead assignment rules that specify criteria based on lead fields such as City, State/Province, or Country, and assign leads that match those criteria to queues or users. Lead assignment rules can be triggered aut omatically when leads are created or manually by users. Creating a formula field, assigning with an escalation rule, or configuring a validation rule will not route leads to sales people. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm & type=5

To see certain information about one or more cases when referencing the contact r ecord, an administrator can use two methods: edit the Related List component in the Lightning App Builder and choose Related List as the related list type; and use the page layout editor to include the appropriate column in the Cases related list. The Rela ted List component is a component that allows users to view and edit records related to a parent record on a record page. The Related List component has two types: Related List and Enhanced List. The Related List type shows records in a table format with c olumns that match the page layout of the parent record. The Enhanced List type shows records in a compact format with fewer columns and actions. To change the type of the Related List component, an administrator can use the Lightning App Builder and select either Related List or Enhanced List from the properties panel. The page layout editor is a tool that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. To include appro priate columns in a related list, such as case name, case ID, customer name, case reason, case status, and case creation date for cases related to contacts, an administrator can use the page layout editor and drag and drop the desired fields from the palet te to the Cases related list on the contact page layout. References: https://help.salesforce.com/s/articleView?id=sf.lex_related_lists_component.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm & type=5

Roll-up summary fields allow you to calculate the sum of a field from child records related to a parent record.

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

Running the flow using it to create contacts and using debug to test the flow in Flow Builder are two key components of testin g 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 dif ferent 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

Profile assignment and page layout assignment are two assignments that should be used to display a new record type to users. Profile assignment determines which profiles can access a record type and which record type is the default for each profile. Page layout assignment determines which p age layout is assigned to each record type and profile combination. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_assign.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_pagelayoutassign.htm & type=5

A dashboard filter is a feature that allows users to filter dashboard components by one or more field values without changing the underlying repo rt data. For example, a dashboard filter can allow users to view cases by origin, status, or owner. A dashboard filter consists of a filter name, one or more source fields, and one or more filter values. Users can apply one or more filters to see different views of the dashboard data. References: https://help.sales force. com/s/articleView?id=sf.dashboards_filters.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 a rticles 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, an d 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/articleV iew?id=sf.knowledge_lightning_component.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.htm & type=5

Flow Builder supports creating a wizard that can collect user input and perform actions.

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

Email-to-Case allows you to create cases from incoming emails. You need to enable this feature and set up routing addresses and case creation settings.

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

Report folders are used to organize and secure reports in Salesforce. You can set different levels of access for different users or groups on each report folder. To preserve the integrity of the source reports for dashboards, you can create a new report folder with viewer access only and move the dashboard reports to that folder. This w ay, users can view the reports but not edit them. References: https://help.salesforce.com/s/articleView?id=sf.reports_folders.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.reports_dashboard_folder_access.htm & type=5

To update the shipping address on selec ted orders associated with an account when the shipping address is changed on the account, the administrator should create a screen flow on the account page that lets the reps choose which orders they want to update with the new address. This will give the m more control and flexibility over which orders are affected by the change. An autolaunched flow on either object will not allow reps to select specific orders, and may cause unwanted updates or errors. A screen flow on the order page will not be able to update multiple orders at once. References: https://help.salesforce.com/s/articleView?id=sf.flow_build_screen.htm & type=5

Lightning app pages, Chatter, and dashboards are three items that are available in the mobile navigation menu. The mobile navigation menu allows users to access d ifferent items in the Salesforce mobile app, such as objects, apps, or utilities. Users can customize their mobile navigation menu by adding or removing items and changing their order. References: https://help.salesforce.com/s/articleView?id=sf.app_nav_setup.htm & type=5

A lookup field is a type of field that creates a relationship between two objects and allows users to select a record from one object as a value for another object. A lookup relationship cr eates a one-to-many relationship between two objects, where each parent record can have many child records but each child record can have only one parent record. A lookup relationship also allows limited access to child records, meaning that users can see only those child records that they have access to based on their profile permissions and sharing settings. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.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 va lues 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 typ e. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthome.htm & type=5

Multi factor authentication (MFA) is a security feature that requires users to verify their identity using two or more factors when they log in to Salesforce. It can help prevent unauthorized access to Salesforce by adding an extra layer of protection beyond username and password. Enabling MFA can be done by administrators in the security setting s or by users in their personal settings. Disabling TLS requirements for sessions, customizing organization wide defaults, or enabling caching and autocomplete on login page are not actions that would prevent unauthorized access to Salesforce; in fact, the y may reduce security or have no effect on security at all. References: https://help.salesforce.com/s/articleView?id=sf.security_mfa.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

App page and record page are two types of pa ges 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 Sal esforce 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 Li ghtning 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

A list view is a feature that allows users to filter and display records based on certain criteria and fields. A Kanban view is a feature that allows users to view records as cards o rganized by columns that represent stages in a process such as opportunity stages or case statuses. Users can switch between list view and Kanban view by clicking on a toggle button on any object tab that supports Kanban view such as opportunities or cases . Users can also edit records by dragging and dropping cards from one column to another or by clicking on an inline edit icon on each card. In this case, the administrator can create a list view on the opportunity object that filters opportunities by expec ted close date in the next 90 days; and recommend users switch the view to Kanban to edit opportunities by drag and drop. References: https://help.salesforce.com/s/articleView?id=sf.lex_list_views.htm & type=5 https://help.salesforce.com/s /articleView?id=sf.kanban_view.htm & type=5

Support processes allow you to define different status values for different record types on cases.

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

To ensure Market Segment field from Lead is copied to converted Account record in routine manner without manual intervention , an administrator should ensure Market Segment field on Lead is mapped to right field on Account using Lead Field Mapping tool under Lead Settings. This tool allows mapping custom fields from Lead object to custom fields on Account , Contact , or Opportunity objects so that data is transferred when leads are converted . For example , an administrator can map Market Segment field on Lead to Market Segment field on Account using this tool . Ensuring Account has a field that has same name as new Lead field , writing validation rule , or writing record-triggered flow are not necessary for copying custom fields from Lead to Account . References : https :// help . salesforce . com / s / articleView ? id = sf . leads_custom_field _mapping . htm & type = 5

Native debug feature is a tool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings tha t indicate where the flow failed or might fail. References: https://help.salesforce.com/s/articleView?id=sf .flow_debug.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 Lead object to display an error message if the Lead Status field is marked as qualified and the Budget field is blank. References: https://help.salesforce.com/s/articleView?id= sf.fields_about_validation_rules.htm & type=5

Account and contact are two records that can be created when using the lead conversion process. The lead conversion process converts a lead into an account, a contact, and optionally, an opportunity. References: https://help.salesforce.com/s/articleView?id=sf.convert_lead.h tm & 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 use as an identifier when importing and updating records from a separate system, an administrator should use External ID field type on an object. External ID fields allow storing unique identifiers from external systems and using them for matching records during import or update operations. External ID fields can also be used for upsert operations that insert new records or update existing ones based on external ID values. For example, an administrator can create an External ID field on Account object that stores account numbers from an external ERP system and use it for importing or updating accounts from that sy stem. Rich Text field, Record ID, and Auto-Number field are not suitable for using as identifiers when importing and updating records from a separate system. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_field_types.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.data_loader_upsert.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

A flow can be active or inactive depending on whether you want it to run or not. An inactive flow cannot be run by users or processes until you activate it. If a flow in production is supposed to create new records but it is not doing so, it could be because the flow is inactive and needs to be activated. References: https://help.salesforce.com/s/articleView?id=sf.flow_distribute_activate.htm & type=5

To identify why a user is unable to log in to Salesforce, the administrator should review the login history for the user. The login history shows the date and time of each login attempt, the source IP address, the browser and platform used, the login type (such as username and password or single sign-on), and the status (such as success or failure). The login history can help troubleshoot common login issues such as incorrect username or passw ord, invalid security token, IP restrictions, or login hours violations. Checking the attempted logins by running the setup audit trail, pulling the password history, or resetting the security token for the profile will not help identify why a user is unab le to log in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm & t ype=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

To enable users to add repeating tasks in Salesforce, the administrator needs to do two things: first, enable the creation of recurring tasks in activity settings under setup; second, add the create recurring series o f tasks field on the page layouts for tasks. This will allow users to create a series of tasks that repeat based on a specified frequency and end date. References: https://help.salesforce.com/s/articleView?id=sf.tasks_repeating.htm & type=5

Permission sets are used to grant additional permissions and access settings to individual users without changing their profiles or requiring a new profile to be created. You can use permission sets to extend users’ functional access without changing their existing profiles. To meet the request of giving comprehensive edit access on Campaigns to a few marketing users who have read-only access by default, you need to create a permission set with edit access on Campaigns and assign it to those users. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm & type=5

Split views are a feature that allows users to view records as a split list on object home pages in Lightning Experie nce apps that use console navigation. Split views show records in two panes: a list view pane on the left and a record detail pane on the right. Users can switch between different list views and records without losing context or scrolling. However, split v iews are only available on standard objects such as accounts, contacts, leads, opportunities, cases, etc., and not on custom objects such as shipments. References: https://help.salesforce.com/s/articleView?id=sf.lex_split_view.htm & type=5

An escalation rule is a tool that allows administrato rs to automatically escalate cases based on certain criteria and time triggers. For example, an escalation rule can change the owner of a case, send an email notification, or update a field value when a case has been open for more than 7 days. An escalatio n rule consists of multiple rule entries that define the criteria and actions for each escalation scenario. References: https://help.salesforce.com/s/articleView?id =sf.case_escalation.htm & type=5

Ther e 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 user s 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://hel p.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

Contact, lead, and person account are three objects that will have the individual field available for tracking data privacy information when data protection and privacy is enabled for an org. The individual object is an object that stores data privacy preferences and requests for customer s who are subject to privacy regulations such as GDPR; it can be linked to contact, lead, or person account records using the individual field. Case and opportunity, account and user, or individual, user, and account are not combinations of objects that wi ll have the individual field available for tracking data privacy information; they either do not store customer data or do not support individual object relationships. References: https://help.salesforce.com/s/articleView?id=sf.individual_object.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

Currency locale and default language are two of the company settings that an administrator can configure in Salesforce. Currency locale determines how currency amounts are formatted and displayed in reports and other places. Default language determines the language used for labels, buttons, t abs, and other elements in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.htm & type=5 https://help.sale sforce.com/s/articleView?id=sf.admin_supported_languages.htm & type=5

A custom profile is a profile that can be created and customized by administrators to define what users can see and do in Salesforce based on their job function or role. It can be used by Cloud Kicks to giv e read, create, and edit access for objects and restrict users from deleting any records by creating and assigning a custom profile with delete access removed for each object in the object settings. Assigning the standard system administrator profile to an alytical user, giving user view all access and assigning them to highest role in role hierarchy, or creating and assigning permission set that includes read, create, and edit access are not solutions for giving read, create, and edit access for objects and restricting users from deleting any records; they either give too much access or do not remove delete access. References: https://help.salesforce.com/s/articleView?i d=sf.users_profiles.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 ca se, 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

An external ID is a custom field that has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using S alesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating recor ds from an external system because it is generated by Salesforce and may not match with the external system’s IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier when importing and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records f rom an external system because it may not be available or consistent across systems. References: https://help.salesforce.com/s/articleView?id=sf.custom_fiel d_attributes.htm & type=5

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields s uch as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm & type=5

Log in as the user is a feature that can be used to validate the error the user is receiving. Log in as the user allows an administrator to access Salesforce as another user and perform actions on their behalf, such as editing an opportunity. This can help troubleshoot issues that are specific to a user’s profile, role, or permissions. References: https://help.salesforce.com/s/articleView?id=sf.admin_login.htm & type=5

Paths allow you to display key fields and guidance for each stage of an opportunity. Kanban list views allow you to update records by dragging them between columns.

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

To require users to choose a specific search engine from a picklist when lead source is “Search Engine”, and hide it otherwise, the administrator should create a picklist for specific search engine on the same screen as lead source, and set conditional visibility so that it is only shown when lead source is “Search Engine”. This will make sure that users see only relevant fields based on their input. A dec ision element will create an extra screen that may disrupt user experience. An assignment element will not affect field visibility. A validation rule will not hide fields but only show errors when values are invalid. References: https://help.salesforce.com /s/articleView?id=sf.flow_ref_elements_screen_components_picklist.htm & type=5 https://help.salesforce.com/s/articleView?id =sf.flow_ref_elements_screen_components_conditional_visibility.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

QUESTION NO: 170

The administrator for AW Computing is working with a user who is having trouble logging

in to salesforce.

What should the administrator do to identify why the user is unable to login?

A. Review the Security token.

B. Review the password history.

C. Review the Password policies.

D. Review the Login history

Answer: D

The login history is a tool that allows administrators and users to view information about recent login attempts, such as date, time, status, source IP address, browser type, platform, application, and login type. Administrators can use this tool to identify why a user is unable to login to Salesforce by checking for any failed login attempts and their corresponding error messages or reasons. References: https://help.salesforce.com/s/articl eView?id=sf.monitoring_login_history.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

Lightning page allows you to customize a record page and add a screen flow as a component. You can use the Lightning App Builder to drag and drop the Flow component onto the page and select the screen flow you want to display.

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

Bucket column allows you to categorize report data into groups without creating a formula or custom field. You can create buckets for different ranges of values and assign labels to them.

References: https://help.salesforce.com/s/articleView?id=sf.reports_bucketing_overview.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 t o 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 relation ship. 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 relat ed objects. References: https://help.salesforce.c om/s/articl eView?id=sf.cross_object_formulas.htm & type=5

A related record component is a type of component that allows users to view and edit fields from a parent rec ord on a child record page without leaving the page. For example, a related record component can allow users to update the account status from the case layout by selecting an account record from a drop-down list. A rich text component is a type of componen t that allows users to display formatted text on a record page using rich text editor tools such as bold font, bullet points, images, and links. For example, a rich text component can display a message in bold font when a case is saved as acriticalrecord t ype by using conditional visibility rules. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_related_record.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_rich_text.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

Knowledge is a feature that can be used to meet this requirement. Knowledge allows users to create, manage, and share articles that provide information and solut ions for common issues or questions. Data categories can be used to organize articles into different topics and make them easier to find and access. Users can view related articles from the Case page layout based on the data category of the case. Reference s: https://help.salesforce.com/s/articleView?id=sf.knowledge_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm & type =5

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

Permissions and tab visibility are two options that administrators can adjust to fully restrict access to records for certain users or profiles. Permissions determine what users can do with records, such as create, read, edit, delete, view all, or modify all. Tab visibility determines whether users can see a specific object tab in their app launcher or navigation bar. By setting permissions and tab visibility to none or hidden for deal records for service users or profiles, administrators can prevent them from accessing deal records via search or other methods. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm & type=5 https://help.salesforce. com/s/articleView?id=sf.customize_tabs.htm & type=5