Which parts of the 'Dispatcher Console' support adding Custom Actions? (Choose 3 options)
Answer : B, D, E
Custom Actions (configured in Field Service Settings) allow dispatchers to trigger Apex classes or Visualforce pages/components from the console.
Option B is correct: You can add custom actions to the Resource List on the Gantt (e.g., right-click a technician's name to 'Send SMS' or 'Show on Map').
Option E is correct: You can add custom actions to individual Service Appointments (e.g., right-click an appointment bar or list item to 'Reschedule' or 'Print Label').
Option D is correct: You can add Mass Actions to the Appointment List (select multiple checkboxes -> Actions -> 'Bulk Dispatch').
Note: You generally cannot perform custom actions on the 'Service Territory' grouping headers (Option A) or multiple resources simultaneously (Option C) in the standard UI.
Green Energy Solution is getting more work for the next 3 weeks. They are engaging a new third-party contractor to help with some work for that time.
What should the admin recommend?
Answer : C
The key here is that it is a Third-Party Contractor and a Temporary engagement.
Option C is correct.
Capacity Based: Contractors are typically modeled as 'Capacity Based Resources' (buckets of work) rather than named individuals, as you usually don't track their specific travel or breaks---you just know they can take 'X hours of work per day.'
Giving Capacity: You would define the capacity only for the specific 3-week period. Once the capacity records end, the scheduling engine will naturally stop assigning work to them.
Options B and D (Deleting): It is never a best practice to delete a Service Resource record after use. You need the record to remain in the system to preserve the Audit Trail and historical data of the Work Orders they completed. You simply deactivate them or stop giving them capacity.
Which of the following objects have fieldsets that allow controlling how the data is displayed in the 'Dispatcher Console'? (Choose 3 options)
Answer : A, B, C
The Dispatcher Console (Gantt) allows admins to customize which fields are visible in various panels and tooltips using standard Salesforce Field Sets.
A is correct (Resource Absence): You can control what information appears when a dispatcher hovers over a non-availability block (e.g., 'Sick Day,' 'Doctor's Appointment') by editing the field set on the Resource Absence object.
B is correct (Service Appointment): This is the most heavily customized object. You can configure field sets to control the columns in the Appointment List, the text shown on the Gantt bar, and the fields in the tooltip (hover).
C is correct (Service Resource): You can customize the resource list (left-hand side of the Gantt) to show fields like 'Vehicle Type,' 'Skill Level,' or 'Phone Number' by editing the field set on the Service Resource object.
Options D and E: Service Territory and Assigned Resource do not have direct field sets that control the Dispatcher Console layout in the same way the primary transactional objects do.
Green Energy Solutions are trying to forecast the number and type of licenses needed to be purchased to support the following resource structure:
Service Territory A has 2 internal resources and 2 contractors set as capacity-based resources: ABC and XYZ, both represent a contractor company. ABC contracting company has 3 individual resources and XYZ contracting company has 4 individual resources.
What type of Field Service licenses and how many of each should Green Energy Solutions purchase?
Answer : D
This question tests your understanding of Salesforce Field Service License types (Dispatcher, Technician, Contractor).
1 Dispatcher: Although not explicitly stated as a user in the text, you always need at least one dispatcher license to manage the schedule. (Typically implied in licensing questions unless '0' is an option).
2 Technicians: Territory A has '2 internal resources'1. Internal mobile workers require the standard Field Service Mobile (Technician) license.
2 Contractors (Capacity-Based): The question states '2 contractors set as capacity-based resources: ABC and XYZ.' 2 These are the 'Bucket' accounts. In Salesforce, even capacity-based container users often consume a license (typically a Contractor or Community Plus login) to access the portal/community where they might view their aggregate schedule.
7 Contractors (Individuals): The question specifies 'ABC... has 3 individual resources and XYZ... has 4 individual resources'3. Even if the scheduling is done at the capacity (bucket) level, if these 7 people need to log in to the app or community to close jobs, they each need a license.
Result: 1 Dispatcher + 2 Technicians (Internal) + 2 Contractors (The Managers/Buckets) + 7 Contractors (The Workers) = Option D.
(Note: Licensing models can be complex. In some strictly capacity-based models, you might not license the 7 individuals if they never log in, but Option D is the most complete answer reflecting a standard model where all participants need system access).
Green Energy Solutions would like to track their vehicles' availability, so that once a Work Order is created, both a Service Resource and a vehicle need to be assigned to the work, to ensure that the resource will use an available vehicle for the job.
How would a consultant recommend implementing this requirement?
Answer : C
The requirement is to schedule two distinct resources (a Human and a Vehicle) for the same job at the same time.
Option C is correct.
Vehicle as Service Resource: You must model the vehicle as a Service Resource (Type: Asset) to track its availability on the Gantt and prevent double-booking.
Complex Work (Same Start): To ensure the vehicle and the technician are booked together, you use Complex Work dependencies. 'Same Start' ensures that the vehicle appointment and the technician appointment are scheduled to begin simultaneously.
Options A and D are incorrect because Products are not scheduled. Consuming a product does not check if the vehicle is available at that specific time, potentially leading to double-booking the van.
Option B is incorrect because 'Immediately Follow' implies a sequence (Technician finishes -> Vehicle starts), which is not how a shared ride/equipment scenario works.
A customer wants to collect a mobile worker's geolocation history in the Field Service Mobile App only for some of the resources, while for others, they want this option to be disabled.
How can a consultant implement this requirement?
Answer : D
The Field Service Mobile Settings configuration controls the behavior of the mobile app (branding, location tracking, flows, etc.).
Option D is correct. To apply different settings to different groups of users, you must create multiple Field Service Mobile Settings records. You assign these settings records to specific User Profiles.
You would create one settings record with 'Collect Service Resource Geolocation History' enabled (for the tracked users).
You would create a second settings record with it disabled (for the untracked users).
You then map the relevant Profiles to the appropriate Settings record.
Options A, B, and C imply global settings or non-existent tabs ('Mobile App Configuration' tab where you select users/profiles directly doesn't exist in the global settings in this manner; it is done via the specific Mobile Settings object assignments).
A customer wants to assign work to Resources by postal code coverages, each Resource covering one or more postal codes. The solution must also support Scheduling and Optimization.
What should a consultant recommend to meet the customer's requirements?
Answer : A
Mapping resources to specific Zip Codes (which are not necessarily Service Territories) is a common high-volume requirement.
Option A is correct. Creating a standard Service Territory for every postal code (Option D) creates a hierarchy that is too deep and hurts performance.
Instead, modeling 'Zip Code Coverage' as a Custom Object (or data table) allows for a cleaner data model. You then use the Extended Match Work Rule. This rule is highly flexible; it can verify that the Zip Code on the Service Appointment matches a record in the Zip Codes Covered related list on the Service Resource. This supports optimization without bloating the Territory or Skill tables.
Option B (Match Fields) only works for 1-to-1 matching (e.g., The Resource has one zip field). It cannot easily handle a resource covering 50 different zip codes unless you use the custom object approach described in A.