Salesforce Certified Administrator Practice Test - Questions Answers, Page 16

To create a many-to-many relationship between two existing custom objects, the administrator needs to create a junction object that has two master-detail relationships, one to each of the custom objects. This will allow each record of one object to be linked to multiple records from another object and vice versa.

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

To free up user licenses for new users, the administrator should deactivate the former employees user record. This will prevent them from logging in and using Salesforce resources, but preserve their historical activities and data. Deleting or freezing user records will not release user licenses.

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

To create a contact and an opportunity from a lead that is associated with a campaign, and keep the campaign member history, the administrator should convert the lead from the campaign member detail page. This will automatically create a contact, an account, and an opportunity that are linked to the campaign. Deleting, cloning, or adding a contact will not preserve the campaign member history.

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

To provide appropriate access to a report that contains shoe records for all of the sales reps on their team, the administrator should configure three items:

A custom report type that includes the shoe object and its fields

A folder access that grants access to the sales manager and their team members to view and run reports in that folder

A field level security that allows the sales manager and their team members to see all the fields on the shoe object Report subscription, while useful for scheduling and delivering reports, does not affect access to the report itself.

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

To automate an outbound message, the administrator should use a workflow rule that defines the criteria for sending the message and the actions to perform when those criteria are met. One of the actions available for workflow rules is sending an outbound message to a designated endpoint URL with specified fields as parameters. Process builder, task assignment, and flow builder are not able to send outbound messages directly.

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

To surface important values based on the stage of the opportunity, the administrator should use path key fields that display fields relevant to each stage along with guidance for success. Path key fields can be customized for each stage and can help users focus on key information and actions as they move opportunities through the sales process. Dynamic forms, opportunity processes, and workflow rules are not designed to show values based on stages.

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

To update the shipping address on selected orders associated with an account when the shipping address is changed on the account, the administrator should create a screen flow on the account page that lets the reps choose which orders they want to update with the new address. This will give them more control and flexibility over which orders are affected by the change. An autolaunched flow on either object will not allow reps to select specific orders, and may cause unwanted updates or errors. A screen flow on the order page will not be able to update multiple orders at once.

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

To require users to choose a specific search engine from a picklist when lead source is ''Search Engine'', and hide it otherwise, the administrator should create a picklist for specific search engine on the same screen as lead source, and set conditional visibility so that it is only shown when lead source is ''Search Engine''. This will make sure that users see only relevant fields based on their input. A decision element will create an extra screen that may disrupt user experience. An assignment element will not affect field visibility. A validation rule will not hide fields but only show errors when values are invalid.

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

To debug a screen flow that creates contacts, one of the possible causes for a variable missing on the debug screen is that the available for input checkbox was unchecked for that variable. This means that variable cannot be set by external sources such as debug inputs or URL parameters. To fix this issue, check this checkbox for any variable that needs to be set externally. The flow version or field type does not affect variable availability for input. The available for output checkbox only affects whether variables can be passed out of flows or subflows.

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