Routes is the feature that supports the use of Custom Drive Profiles. Custom Drive Profiles are used to create routes that are optimized for trucks and other vehicles that might not be able to travel the same roads as passenger cars3. A route can be optimized based on the specificcharacteristics of a truck and its cargo, such as height, weight, length, and hazardous materials3. To use this feature, the user needs to create a Salesforce Maps Drive Profiles tab and a custom object for Maps Drive Profile3. Then, the user can create a new Drive Profile with the details of the vehicle and select it when creating a route in Salesforce Maps3. The characteristics of the vehicle’s Drive Profile will be used to create a route that is compliant with published permanent road restrictions3. Favorite Location, Schedule, and Marker Layer are not features that support the use of Custom Drive Profiles.

Balance prioritizes equal distribution of the selected attribute across territories in your focus. This is the best option for ensuring revenue is distributed as evenly as possible across the entire sales team1. References: Optimization in Salesforce Maps Territory Planning

According to the Trailhead module 3, this is the correct type of report and field for creating a data set that integrates with Enterprise Territory Management. An Accounts and Territories report can show the accounts that are assigned to territories, and the Territory Id field can be used to assign units to areas based on their territory membership.

Permission Groups are the permission level that an admin should review if a user is able to view but not able to export a list of markers from Salesforce Maps. Permission Groups are used to grant access to features in Salesforce Maps, such as allowing marker exports, editing details tab fields, enabling weather tab, and so on1. The admin can edit existing permission groups or create new ones to assign different features to different users or profiles1. If a user is not able to export a list of markers from Salesforce Maps, it means that the user does not have the ‘Allow Marker Exports’ permission checked in the Permission Groups on Maps configuration page2. The admin can enable this permission for the user or profile by editing the corresponding permission group2.

One way to automate the process of clearing coordinates for records that have address changes is to use a Salesforce automation tool, such as Process Builder or Flow Builder. These tools can help create workflows that trigger actions based on certain criteria or events. For example, the account executive from Alpine Energy can use Process Builder to create a process that runs whenever an account is created or edited,and checks if any of the address fields have changed. If so, the process can execute an action that clears the latitude and longitude values of the account record. This way, the next time the account is plotted on Salesforce Maps, it will geocode with the updated address and plot in the correct location. Alternatively, the account executive can use Flow Builder to create a flow that performs similar logic and actions as the process, but with more flexibility and customization options. For more information on how to use Process Builder or Flow Builder, see the references below. References:

• 2: Automate Your Business Processes with Process Builder | Salesforce Trailhead Module2
• 3: Automate Your Business Processes with Flow Builder | Salesforce Trailhead Module3

According to the Salesforce Help article on Publish to Enterprise Territory Management in Salesforce Maps Territory Planning2, three things that can be published from Territory Planning to Enterprise Territory Management are: manually assigned accounts, territories, and geographic territory rules. Manually assigned accounts are accounts that are locked to a specific territory in Territory Planning and will not be affected by optimization or rule changes2. Territories are the hierarchical units that define sales and service coverage areas3. Geographic territory rules are rules that assign accounts to territories based on their address fields4.

The implementation team is responsible for business and IT sanity testing post deployment to production. Sanity testing is a type of software testing executed on the stable build of an application with minor code changes. It is also known as surface-level testing. A sanity test is performed to ensure the application works as expected after the bug fixes or changes in the code1. The implementation team, which consists of developers, testers, and business analysts, conducts sanity testing to verify the functionality and performance of the application after deployment2. The project manager, the Salesforce support team, and the customer are not directly involved in sanity testing post deployment.