Free Practice Questions for Salesforce Salesforce-Maps-Professional Exam

These are two factors that an admin should keep in mind during the oAuth process when setting up Maps Advanced. According to the article "OAuth user requirements for Salesforce Maps"1, an oAuth user is required to establish a secure asynchronous connection with the Salesforce Maps Advanced, Live Tracking, and Territory Planning products. The oAuth user impacts the following product functions:

Performs optimizations for routes in Advanced Routing

Uploads results of Live Rules into customer Org in Live Tracking

Performs optimizations for territories in Territory Planning To perform these functions, the oAuth user should have full CRED (Create, Read, Edit, Delete) rights for records being routed1. The oAuth user should also beassigned a role that is above the Maps Advanced end-users in the Salesforce Role Hierarchy1. This ensures that the oAuth user can access and modify the records ofthe end-users. Having the SF Maps Admin permission set is not the only prerequisite for the oAuth user, as the oAuth user also needs to have the Salesforce MapsAdvanced Permission Set License assigned and the SF Maps Advanced Permission Set assigned1. The oAuth user does not need to fall within Sales organization, as this is not a relevant factor for setting up Maps Advanced.

 stop associations are a feature of Maps Live Tracking that allow an organization to see the accounts that are being visited during the day. Stop associations automatically link a user’s location history with nearby accounts, contacts, or leads in Salesforce. This way, an organization can track and analyze the visits made by their mobile users.

Defining customer user stories is the process of identifying which user stories the implementation team will build based on the customer’s needs and priorities. Designing customer user stories is the process of determining how the implementation team will build the user stories based on the best practices andtechnical specifications. This is explained in the Salesforce Maps Implementation Methodology document.

According to the Salesforce Help article on Optimization in Salesforce Maps Territory Planning2, pinned area centers are fixed locations that optimization uses as startingpoints for each territory. This feature can be used to ensure that sales reps’ homes are located within theboundaries of their respective territories whenever they run an optimization2. Pinned area centers can be set manually or automatically based on user location or other criteria2.

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 assignedaccounts 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 addressfields4.

geocoding is the process of transforming a description of a location—such as a pair of coordinates, an address, or a name of a place—to a location on the earth’s surface. You can geocode by entering one location description at a time or by providing many of them at once in a table. The resulting locations are output as geographic features with attributes, which can be used for mapping or spatial analysis123. Therefore, the correct answer is C.

According to theSalesforce Maps Configuration module on Trailhead1, to create multiple visit windows for different types of visits, you need to create two lookup fields on the Account object to the Visit Window object. This way, you can assign different visit windows to different routable records.

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 ofthe application after deployment2. The project manager, the Salesforce support team, and the customer are not directly involved in sanity testing post deployment.

According to the Salesforce Maps documentation1, when using the limit areas by attribute option during an optimization, some units may be trimmed from the areas and assigned to a specific area or the unassigned bucket, depending on the leftover unit assignment setting. To visualize these leftover units, the user must open the alignment using the “Include Unassigned Units” option, which will display all units in the data set, regardless of whether they are assigned to an area or not. This option can be found in the Alignment Settings window, under the Data tab2. By selecting this option, the user can see the leftover units on the map and in the legend, and decide how to handle them. References:

1: Optimization in Salesforce Maps Territory Planning | Salesforce Help1

2: Alignment Settings | Salesforce Help3

According to the Salesforce Help article on Filter by Owner in Maps Marker Layer Builder3, filtering by owner or ownership scope allows Maps users to filter Marker layersbased on the record ownership model in their Salesforce org. To create one marker layer for several users to display only the accounts they currently own, an admin can create an Account Marker Layer, select My Accounts under Filter By Owner3. This will show all accounts ownedby the logged-in user.