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

Permission sets are a flexible way to grant additional access to users without changing their profiles. To provide access to the lead object for a team of support users, create a permission set that includes the appropriate object and field permissions for leads, and then assign it to the users. References:https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5

 Geolocation fields allow you to store the latitude and longitude coordinates of a location. They can be used tocalculate distances between records and display maps of accounts, contacts, leads, or other custom objects. References:https://help.salesforce.com/s/articleView?i d=sf.customize_geoloc.htm&type=5

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do notmeet certain criteria. In this case, a validation rule can be created on the Lead object to display an error message if the Lead Status field is marked as qualified and the Budget field is blank. References:https://help.salesforce.com/s/articleView?id= sf.fields_about_validation_rules.htm&type=5

Campaign hierarchy is afeature that allows administrators to organize campaigns into a parent-child relationship, where the parent campaign represents a larger initiative and the child campaigns represent smaller or more specific activities within that initiative. Using campaignhierarchy can help Ursa Major Solar report on campaign ROI by month and series by creating a parent campaign for the series of networking events and creating individual child campaigns for each monthly event. The parent campaign can show the aggregated metrics and ROI for the entire series, while the child campaigns can show the metrics and ROI for each month. Adding different record types for the monthly event types, creating individual campaigns that all have the same name, or configuring campaign memberstatuses to record which event members attended are not solutions for reporting on campaign ROI by month and series; they either do not group campaigns into a hierarchy or do not track campaign metrics or ROI. References:https://help.salesforce.com/s/articleView?id=sf.campaigns_ hierarchy.htm&type=5

A master-detail relationship is a parent-child relationship in which the master object controls certain behaviors of the detail object. The master object can be a standard or custom object, but not all standard objects support being a master. Roll-up summaries are fields that calculate the sum, count, min, or max of child records. The owner field on the detail records is not available and is automatically set to the owner of the master record.

References: https://www.forcetalks.com/blog/master-detail-relationship-in-salesforce/ https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

Contact, lead, and person accountare 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

To track shoe designs by products, prevent them from being deleted, and allow multiple designs for one product across various stages, the administrator should create a custom object for shoe designs and configure a custom lookup field for shoe designs on the Product object. This will create a one-to-many relationship between products and shoe designs, and allow users to link multiple shoe designs to one product record. To prevent shoe designs from being deleted, the administrator can use validation rules or permissions. Adding a custom master-detail field for shoe designs on the Product object will create a many-to-one relationship, which is not desired. Using the standard object for designs or configuring a validation rule will not meet the requirement. References:https://he lp.salesforce.com/s/articleView?id=sf.customize_object_relationships_overview.htm&type=5

App page and record page are two types of pages that an administrator can build and customize using Lightning App Builder for Salesforce mobile app. App pages are pages that display information or tools that don’t belong to a specific record; they can be accessed from navigation menus or tabs in Salesforce mobile app. Record pages are pages that display information or actions related to a specific record; they can be accessed by opening any record in Salesforce mobile app. User page and dashboard page are not types of pages that can be built using Lightning App Builder for Salesforce mobile app; they are types of pages that can be built using other tools such as Profile settings or Dashboard Builder. References:https://help.salesforce.com/s/articleView?id=sf.app_builder_mobile_pages.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

To show different picklist values for sales and marketing users, you can either use record types or profiles. Record types allow you to have different picklist values for different page layouts assigned to different profiles. Profiles allow you to restrict picklist values basedon user permissions.

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