Salesforce Certified Administrator Practice Test - Questions Answers, Page 22

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 password, 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 unable to log in.

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

To help a user who has attempted to log in multiple times and has been locked out of Salesforce, the administrator should reset password on the user's record detail page and use the unlock button on the user's record detail page. Resetting password will generate a new temporary password and send it to the user's email address. Using unlock will restore access for a locked-out user without changing their password or waiting for lockout period to end. Logging in as the user or resetting the password policies will not help a locked-out user log in to Salesforce.

Reference: https://help.salesforce.com/s/articleView?id=sf.users_passwords.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_unlock.htm&type=5

To allow a user to add new Campaign Members or update Member statuses, the administrator should make sure that Marketing User Checkbox is checked on the user record page. This checkbox enables users to create, edit, and delete campaigns, configure advanced campaign setup, import leads, manage campaign members, and update campaign history via mass update. The checkbox also requires users to have Read and Edit permissions on campaigns and leads/contacts. Creating a permission set, providing access to both Leads and Contacts, or running a Campaign report will not enable users to manage Campaign Members.

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

To capture the expiration date of warranty based on installation date and warranty length (1 year by default), the administrator should use a formula as the default value of Warranty Expiration Date field on Installation object. The formula can calculate one year from installation date using DATE function or DATEVALUE function. For example, DATE(YEAR(Installation_Date__c) + 1 , MONTH(Installation_Date__c) , DAY(Installation_Date__c)) will return one year from installation date. Creating a formula field, adding a validation rule, or including Warranty Expiration Date field on mobile page layout will not capture expiration date based on installation date and warranty length.

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

To provide a summary of org's security health, an administrator should run a Health Check that compares org's settings against baseline settings defined by Salesforce Security Baseline Standard or industry standards such as CIS (Center for Internet Security) Benchmark Standard. Health Check generates an overall health score based on how org's settings match with baseline settings for various security categories such as Password Policies, Network Access, Session Settings etc. Health Check also provides recommendations for improving org's security health score by adjusting settings that do not match with baseline settings. Changing Org-Wide Default to private, turning on Event Monitoring, or downloading user login data will not provide a summary of org's security health.

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

Reference: https://help.salesforce.com/s/articleView?id=sf.campaigns_parent.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 . Reference : https :// help . salesforce . com / s / articleView ? id = sf . leads_custom_field_mapping . 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 . Reference : https :// help . salesforce . com / s / articleView ? id = sf . lex_path_setup_key_fields . 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.

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