ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

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

One of the possible causes for being unable to add a new user in Salesforce is that the username is already in use by another organization. Usernames must be globally unique across all Salesforce orgs, so if another user has claimed that username before, it cannot be used again. To fix this issue, choose a different username that is not taken by anyone else. The username is not restricted to a domain specific to my domain unless specified by an administrator. The email address used for the username does not have to match a contact record. The email used for the username can be any valid email address. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_add.htm &type=5

One scenario that could prevent an administrator from changing the relationship between work item and project custom objects from master-detail to lookup is that roll-up summary fields exist on the master object (project). Roll-up summary fields are fields that calculate values from related records in a master-detail relationship; they cannot be used in a lookup relationship. If roll-up summary fields exist on the project object, they would prevent the administrator from changing the relationship type unless they are deleted first. A junction object is not required to support a lookup relationship; it is only used when creating many-to-many relationships between two objects using two master-detail relationships. The lookup field in all the records containing a value or the lookup field being required for saving records are not scenarios that would prevent changing the relationship type; they are scenarios that would allow changing the relationship type without losing data or functionality. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

 Discount is not a standard field on the Opportunity object, so you need to create a custom field to capture the discount amount or percentage for each opportunity. To set up an approval process where opportunity discounts over 30% need to be approved by the VP of sales, and any discounts above 10% need to be approved by the user’s manager, you need to configure two separate approval processes with different entry criteria based on the discount field value and different approvers based on their roles. References: https://help.salesforce.com/s/articleView?id=sf.approvals_getting_started.htm &type=5

To protect data with backups by using Data Export Service, two considerations that the administrator should remember when scheduling export are:

• Data Backups are limited to weekly or monthly intervals depending on edition and license type
• Metadata backups must be run via a separate process such as Metadata API or change sets because Data Export Service only exports data (records) Metadata backups are not limited by sandbox refresh intervals. Data Export Service should be run from production orgs unless testing purposes require otherwise. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm&type=5

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadrules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.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 customers 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 will 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

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 use page layout editor to make fields editable or read-only on page layouts for different profiles or record types. After resetting a password, the user may be required to activate their device by entering a verification code sent to their email address or phone number before they can log in to Salesforce. This is a security feature that helps prevent unauthorized access to Salesforce from unknown devices or browsers. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.identity_verification.htm &type=5

Validation rules allow you to enforce data quality by preventing users from saving records that do not meet certain criteria.

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