Salesforce Certified Administrator Practice Test - Questions Answers, Page 23

To access the account object in Salesforce, users need to have permission to the account object on their profile or permission set. Permission to an object determines what users can do with records of that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission to an object, they will not be able to see or access that object in Salesforce.

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

A junction object is a type of custom object that allows administrators to create many-to-many relationships between two other objects. A many-to-many relationship means that each record of one object can be related to multiple records of another object, and vice versa. For example, a junction object can represent that a contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects.

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

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 a purchase 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.

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

To customize the campaign member status picklist values themselves, marketing users need two things: a marketing user feature license and edit permission for campaigns. A marketing user feature license enables users to create, edit, and delete campaigns; manage campaign members; and update campaign history via the import wizards or API. Edit permission for campaigns allows users to modify existing campaigns and their related records such as campaign members and campaign member statuses.

Reference: https://help.salesforce.com/s/articleView?id=sf.campaigns_enable.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.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.

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

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario.

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

A restricted picklist is a type of picklist that enforces the integrity of the picklist values by allowing only values defined in the picklist during data entry or import operations. If the restricted picklist checkbox is checked for a picklist field, then any records with values not defined in the picklist will cause errors during import operations. However, if the restricted picklist checkbox is unchecked for a picklist field, then any records with values not defined in the picklist will be imported without errors.

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

Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results.

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

Two data loss considerations when changing a custom field type from Text to Picklist are:

Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.

Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist.

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