Free Practice Questions for Salesforce Salesforce-Certified-Administrator Exam

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to apurchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References:https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

A PriceBook is a feature that allows administrators to define different prices for the same products based on different criteria such as customer segment, region, channel, etc. For example, a PriceBook can provide reseller partners with discounted prices on the products they purchase compared to regular customers. A PriceBook consists of one or more PriceBook entries that specify the product ID, pricebook ID, list price, currency, and active status for each product-pricebook combination. References:https://help.salesforce.com/s/articleView?id=sf.pricebook_overview.htm &type=5

Setup audit trail is a tool that allows administrators to review recent configuration changes made in their org. It shows a list of up to 180 days of setup changes made by anyone in the org, including the date, time, user, and type of change. It can help administrators track who made what changes and when, and troubleshoot any issues caused by configuration changes. Critical updates are notifications that inform administrators of new features or enhancements that may impact their org; they do not show configuration changesmade by users. Debug logs are records of database operations, system processes, and errors that occur when executing a transaction or running unit tests; they do not show configuration changes made by users either. Field history tracking is a feature thatallows administrators to track changes to the values of certain fields on records; it does not show configuration changes made in setup. References:https://help.sale sforce.com/s/articleView?id=sf.monitorsetup.htm&type=5

My Domain is a feature that allows administrators to create a custom domain name for their Salesforce org that replaces their instance URL (such as na35.salesforce.com). My Domain provides benefits such as improved security; enhanced branding; faster navigation; access to Lightning components; etc. However, one of the considerations when enabling My Domain is that it changes how users log in to Salesforce - instead of using their instance URL login (such as login.salesforce.com), they have to use their My Domain login (such as mydomain.my.salesforce.com). This applies to all internal and external users who access Salesforce via web browser or mobile app. References:https://help.salesforce.com/s/articleView?id=sf.domain_name_overview.htm &type=5

Contract is a standard object that represents a contractual agreement between your company and a customer. Case is a standard object that represents a customer’s questionor problem that needs to be resolved by your support team. Account is a standard object that represents an individual or an organization involved in your business, such as customers, competitors, partners, etc. These three objects are commonly used for service use cases in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.contract_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_fields.htm &type=5https://help.salesforce.com/s/articleView?id=sf.account_fields.htm &type=5

Splits is a feature that should be used to meet this requirement. Splits allows users to assign credit to opportunity team membersbased on the level of effort contributed by each person toward each deal. Users can create different types of splits, such as revenue or overlay splits, and specify the percentage or amount of credit for each team member. References:https://he lp.salesforce.com/s/articleView?id=sf.forecasts3_splits_overview.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, thesource 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. References:https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.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 securitystandards. 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

Lightning record page is a type of page that should be created to meet this requirement. Lightning record page allows an administrator to customize the layout and components for a specific object record page in Lightning Experience or the Salesforce mobile app. To create tabs for account details, related lists, and chatter feeds, use the Tabs component in the Lightning App Builder and drag the desired components to each tab. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_record_page.htm &type=5 https://help.salesforce.com/s/articleView?id=sf .app_builder_tabs.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 creates 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 seeonly 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