The optimizer is already producing the mathematically lowest-travel result; the business wants to override that to consolidate Narnia visits to a single day. Several configuration levers can force the engine to favor same-day grouping.

Option A is correct. An Extended Match Rule with a custom 'Coverage' object can express the requirement that Narnia services are only valid on one specified day of the week. This hard rule forces all Narnia work into the same day.

Option B is correct. Assigning Visiting Hours on the Work Order that restricts Narnia customer visits to a single day per week constrains the engine to schedule all those appointments within that window, achieving the same-day grouping.

Option E is correct. Raising priority on Narnia customers makes the optimizer schedule them earlier in the planning sequence. Combined with a tight time horizon, this often clusters them together because the optimizer satisfies high-priority work before filling gaps with lower-priority visits.

Option C is incorrect because 'PolygonUtils' is not a Salesforce Field Service class used to constrain scheduling.

Option D is incorrect because the customer already understands they will pay higher travel; adding another Minimize Travel objective would only reinforce the current undesired spread.

Customer self-scheduling requires an externally exposed booking action, while call-center bookings happen inside Salesforce. The Book Appointment action serves both surfaces.

Option C is correct. The Book Appointment global action returns available appointment slots based on the Scheduling Policy, Work Rules and Operating Hours, and lets a call-center agent confirm one. It is the standard internal-user booking surface.

Option D is correct. The Communities Book Appointment action exposes the same booking capability through an Experience Cloud (Communities) site, enabling customer self-service scheduling without contacting the call center.

Option A is incorrect because Get Candidates returns eligible resources for an existing appointment, not bookable time slots, and is a dispatcher tool.

Option B is incorrect because a nightly optimization job rearranges existing appointments and does not allow customers or agents to choose a slot.

To tier resources generally (not per customer), you use the Resource Priority Service Objective.

Option C is correct. The Resource Priority objective works on a scoring scale where a Higher Value indicates a Higher Priority . The optimization engine attempts to assign the appointment to the resource that yields the highest overall schedule score.

By assigning Full-Time = 10, Contractors = 9, and Part-Time = 8, the engine will "score" the Full-Time option highest, followed by the Contractor.

Option D uses the inverse logic (1, 2, 3). If deployed, the engine would favor the Part-Time employees (Score 3) over the Full-Time employees (Score 1), which is the opposite of the requirement.

Options A and B refer to Preferred Resource , which is typically defined on the Account or Work Order level (e.g., "Bob is preferred for Customer X"). It is not efficient for ranking entire groups of employees globally.

To send push notifications to the Field Service mobile app based on specific criteria, you need both the configuration and the automation.

Option B is correct: You must first enable and configure Custom Notifications for the Field Service Connected App. This ensures the mobile device is capable of receiving and displaying the specific notification type.

Option D is correct: You need an automation trigger (Record-Triggered Flow) to detect the specific business condition: The Service Appointment Status changes to 'Dispatched' AND the Priority (or Work Type) is 'Emergency'. The flow then executes the "Send Custom Notification" action targeting the Assigned Resource user.

Option A and C refer to "Jeopardy," which is a different feature used to warn dispatchers about impending SLA violations, not to notify technicians of new work.

When Global Optimization leaves appointments unscheduled despite available capacity, the root cause is usually in the optimization configuration (which appointments are eligible) rather than in the Gantt UI state.

Option A is correct. 'Pinned Statuses' under Field Service Settings define which Service Appointment statuses are treated as locked by Global Optimization. If an appointment is in a pinned status, the optimizer will not move or schedule it, which produces exactly the symptom described.

Option C is correct. The lightbox shown when invoking optimization from the Gantt lets the dispatcher choose the Scheduling Policy, time horizon, filters and resources. A misconfigured run from this dialog directly causes appointments to be skipped.

Option D is correct. 'Optimization Insights' on the Optimization Request object surfaces detailed information about which appointments were considered and why some were not scheduled (work rule violations, no eligible resource, etc.). This is the most direct investigative tool available.

Option B is incorrect because list view visibility is a UI concern; Global Optimization picks up appointments based on the scope you select, not based on what is visible to the dispatcher.

Option E is incorrect because the Gantt's active Scheduling Policy is not what controls Global Optimization — the policy is chosen in the run dialog.

To filter resources based on strict criteria (like security clearance), you use Work Rules (Hard Constraints).

Option B is correct (Match Boolean): This is a simple, effective method for binary requirements. You place a checkbox on the Service Appointment (e.g., "Requires Security Badge") and a corresponding checkbox on the Service Resource (e.g., "Has Security Badge"). The Match Boolean Work Rule enforces that if the Appointment is checked, the Resource must also be checked.

Option E is correct (Extended Match): If the requirement is more complex (e.g., matching a specific type or level of badge), the Extended Match Work Rule is best. It allows you to match a field on the Service Appointment (or Work Order) to a related list or field on the Service Resource. For example, matching the "Badge Type" required by the Government Account to the "Badge Type" held by the Resource.

Note: While Skills (Option C) are also commonly used for this, the question specifically points toward Work Rule configurations (Boolean/Extended) often used for strict compliance attributes.

This requires a balance of data accuracy (tracking the asset) and schedule accuracy (updating the duration).

Option D is correct because it uses Field Service Mobile Flows , which is the best practice for guiding technicians through complex processes.

Data: Creating a Work Order Line Item (WOLI) is the correct data model to track work done on a specific (secondary) Asset under the main Work Order.

Schedule: The flow can update the current Service Appointment's Duration and Scheduled End to reflect the reality that the tech will be there longer.

Automation: Triggering a "Scheduling Recipe" (now typically handled via Flows/Optimization services) ensures that if the appointment runs long, subsequent appointments for the day are automatically shifted (Reshuffled) to prevent overlapping/late arrivals.

Options A and C fail to update the schedule duration, meaning the tech will likely be late to their next job without the dispatcher knowing. Option B creates a second appointment, which is administratively heavy for "just looking at" another asset during the same visit.

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.

When dealing with a Bring Your Own Device (BYOD) strategy (common with contractors), device compatibility is the biggest technical hurdle.

Option B is correct. Salesforce explicitly publishes a list of supported devices and operating systems (iOS and Android versions) 6 . Since the company does not own the phones, they cannot guarantee every contractor has a compatible device. The consultant must warn the client to check these specs against their contractors' hardware.

Option A is a policy decision, not a technical constraint. You can track contractor location if they agree to it.

Option C is false; Contractor licenses (Community Plus) do include access to the Field Service Mobile App.

Salesforce Field Service provides specific tools for capturing rich media in a structured way.

Option B is correct (Mobile Flow): This is the modern best practice. By using a Flow with the File Upload (or Image) screen component, you can guide the technician to take a photo at a specific step in the process (e.g., "Take a photo of the completed installation"). This ensures consistency.

Option A is correct (Quick Action): You can configure Quick Actions (specifically Global or Object-Specific actions for File Uploads) in the Field Service Mobile app extension settings. This provides a one-tap button for technicians to launch the camera and attach a file directly to the record.

Note: While Option D (Chatter Feed) is possible, it is unstructured data. Options A and B are the "Best Practice" recommendations for process adherence.