A customer needs to cancel all appointments within a specific area due to climate changes that boosted a bushfire.
How should a consultant recommend implementing this requirement?
Answer : A
The Dispatcher Console Map is the most efficient tool for geographic mass actions.
Option A is correct. Salesforce Field Service allows dispatchers to draw custom Map Polygons directly on the Gantt map. Once a polygon is drawn around the affected bushfire area, the dispatcher can right-click the polygon (or use the actions menu) to perform Mass Actions on all Service Appointments contained within that shape. 'Unschedule,' 'Cancel,' or 'Flag' are standard bulk actions available in this context.
Option B (Reports/Data Loader) is too slow for an emergency response.
Option C (Optimization) would just move the appointments to later times, not cancel/unschedule them.
Option D (List View) is difficult because defining a 'bushfire area' using text filters (City, Zip) is often inaccurate compared to drawing the precise boundary on a map.
Universal Containers (UC) sell Service Contracts to their customers. One of the terms of the Service Contract determines that a UC technician will perform annual maintenance on all the customer's Assets until the contract expires.
UC would like to ensure that when a technician is sent to the customer, the maintenance work is completed in a single visit, and all covered Assets are listed on the Work Order's Service Report.
What Maintenance Plan configuration should a consultant recommend UC?
Answer : D
This question tests the Maintenance Plan generation logic.
Option D is correct. The requirement is Single Visit (One Appointment) for Multiple Assets.
One Work Order Line Item per Asset: This groups all the assets under a single parent Work Order. Each asset gets its own line item (WOLI) for tracking purposes.
One Service Appointment per Work Order: This creates a single appointment for the parent Work Order. The technician arrives once and works through the list of line items (Assets).
Option B ('One Work Order per Asset') would create separate Work Orders (and likely separate Appointments) for every single asset, resulting in multiple visits or a cluttered schedule.
Option C ('One SA per WOLI') would explicitly create a separate appointment for every single asset line item, causing massive double-booking/overlap.
Universal Containers uses In-Day Optimization to optimize a Service Territory schedule during working hours. The dispatchers have recently noticed that In-Day Optimization reschedules Service Appointments in status 'In Progress' to other Service Resources, which requires them to correct the schedule manually.
What should a consultant recommend to troubleshoot this behavior?
Answer : C
When running optimization (Global or In-Day), the engine is allowed to move any appointment that is not 'Pinned.'
Option C is correct. In Salesforce Field Service, you must explicitly define which statuses are considered Pinned (immovable) during optimization. This is configured in Field Service Settings > Optimization > Logic. If the 'In Progress' status is not selected in the 'Pinned Statuses' list, the optimization engine sees that appointment as movable. To improve the schedule, it might unassign the current tech and assign a different one, even though the tech is already on-site.
Ensuring 'In Progress' is 'excluded from optimization logic' (Pinned) forces the engine to schedule around that appointment rather than moving it.
Option B refers to 'Status Transitions,' which controls the lifecycle flow (e.g., New -> Scheduled -> In Progress) but does not control the scheduling engine's permission to move the job.
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).
An admin notices that an org currently has a large number of qualified candidates per Service Appointment.
How can the admin reduce the number of candidates per appointment in order to improve optimization quality?
Answer : D
In Salesforce Field Service, the scheduling engine creates a list of 'Qualified Candidates' based on Work Rules (Hard Constraints). If a search returns too many candidates, it places a heavy load on the CPU and can degrade optimization performance.
Option D is correct because Work Rules are the mechanism used to filter candidates. Adding rules like Match Territory (ensuring the resource belongs to the territory), Maximum Travel from Home (filtering out distant resources), or Extended Match (matching custom criteria) effectively reduces the pool of eligible technicians before the system attempts to score them. This improves the speed and quality of the schedule.
Option A is incorrect because Service Objectives are 'Soft Constraints.' They rank candidates (giving them a score of 0-100) but do not remove them from the list.
Option B is a manual structural change that doesn't address the configuration issue.
Option C is incorrect because optimization performance is directly controlled by the efficiency of the configuration (Scheduling Policy).
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).
Universal Containers would like the Service Appointment times that are displayed on the 'Dispatcher Console' to reflect the actual times a field worker starts and completes the work. That way, if they finish early, they might be able to add additional work to the new white space.
What implementation approach should the Field Service consultant recommend?
Answer : D
The requirement is specifically to free up white space on the Gantt when a tech finishes early.
Option D is correct. The Gantt chart visual blocks are drawn based on Scheduled Start and Scheduled End. If a tech finishes a 2-hour job in 30 minutes, the Gantt bar will remain 2 hours long unless the Scheduled End is updated. By using a Mobile Flow to update both the Actuals (for reporting) and the Scheduled (for the Gantt), the bar shrinks, revealing 1.5 hours of open availability for the dispatcher to utilize.
Option C is the 'Purist' data view (don't change scheduled), but it fails the specific business requirement of allowing new work to be added immediately.
Option A suggests creating custom fields for the original times, which is a valid part of the solution (to keep a history), but Option D describes the core functional mechanism (Flow updating the standard fields) required to achieve the Gantt behavior. The 'Offline' warning in A is true but D is the more direct configuration answer.