Pass the Salesforce Administrator Salesforce-Certified-Administrator Questions and answers with ValidTests

A lookup relationship is a type ofrelationship 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 information 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 related 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 an 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

Maximum invalid login attempts, password complexity requirements, and number of days until expiration are three password policies that anadministrator can configure to encourage employees to choose secure and appropriate passwords for their Salesforce accounts. Maximum invalid login attempts determines how many times a user can enter an incorrect password before being locked out of Salesforce. Password complexity requirements determine how complex a user’s password must be based on criteria such as length, case sensitivity, alphanumeric characters, etc. Number of days until expiration determines how often users must change their passwords. References:https://help.salesforce.com/s/articleView?id=sf.security_password_policies.htm &type=5

Before save flows only support four elements: Assignment, Decision, Get Records, and Loop.

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

To display only the proper lead sources based on the product category chosen, an administrator should create a dependency between the Product Category field and Lead Source field on Lead object. Adependency is a relationship between two picklist fields that restricts the values available in one picklist based on the value selected in another picklist. For example, an administrator can create a dependency that shows only Online Store and Social Media as lead sources if Product Category is Shoes, but shows only Trade Show and Magazine as lead sources if Product Category is Apparel. Creating apage layout for each category, creating business processes and record types for each category, or creating a single business process with record types for each category will not display only the proper lead sources based on the product category chosen. References:https://help.salesforce.com/s/articleView?id=sf.customize_dependent.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_i mplementation_dashboards_and_reports/dashboards

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 andmetadata 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

To identify new leads entered by interns from existingleads, 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 App 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 &type=5

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

Web-to-Case and Email-to-Case are two solutions that allow customers to create cases from a webform or an email. Web-to-Case generates HTML code for a web form that you can place on your website. Email-to-Case converts incoming emails into cases.

References: https://help.salesforce.com/s/articleView?id=sf.customizesupport_web_to_case.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customizesupport_email_to_case.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 give 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 thestandard system administrator profile to analytical 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 andrestricting 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