Free Salesforce Administrator Questions for Salesforce Administrator Exam as PDF & Practice Test Software

Answer : D

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

Answer : D

The likely cause for why a rehired user is no longer able to access records they worked on before leaving the company is that the records were manually shared with the user. Manual sharing allows granting access to individual records to specific users or groups. However, manual sharing is removed when a record owner changes or when a user's role changes. When a user is deactivated, their role is removed and any manual sharing involving that user is deleted. When a user is reactivated, their role is restored but manual sharing is not. Therefore, the rehired user will not have access to records that were manually shared with them before deactivation. The stage of Opportunity records, permission sets, or record type of Opportunity records are not likely causes for why a rehired user is no longer able to access records they worked on before leaving the company. Reference: https://help.salesforce.com/s/articleView?id=sf.sharing_manual.htm&type=5

Answer : A, D

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. Reference: 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

Answer : D

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 system. 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. Reference: 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

Answer : C

Split views are a feature that allows users to view records as a split list on object home pages in Lightning Experience 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 views are only available on standard objects such as accounts, contacts, leads, opportunities, cases, etc., and not on custom objects such as shipments. Reference: https://help.salesforce.com/s/articleView?id=sf.lex_split_view.htm&type=5