What AP-209 Questions and Answers feature?

This scenario requires managing availability for resources who work across multiple territories (Primary and Secondary memberships) specifically for "off-hours" emergencies.

Option D is correct because Shifts in Salesforce Field Service allow you to define ad-hoc availability outside of standard Operating Hours. Crucially, if you create a Shift without specifying a Service Territory , that availability applies to the resource's Primary Territory by default. However, because the resource also holds Secondary Territory Memberships for the other business units, the scheduling engine (specifically the "Match Territory" Work Rule) recognizes this availability as valid for those territories as well, provided the shift falls within the membership dates.

Setting the Time Slot Type to 'Designated' (or 'Extended') is the standard way to mark time for specific work types (like Emergencies) using Work Rules that filter on those time slot types.

Option B is incorrect because creating a separate shift for every territory is administrative overhead and unnecessary when a single non-territory-specific shift can cover the resource's availability across their memberships.

Option A is factually incorrect; resources can have multiple territory memberships.

This is a classic "Double-Booking" vs. "Complex Work" scenario.

Option B is correct. To book two distinct people for the same work at the same time, you create two Service Appointments . You link them using a Complex Work dependency of type Same Start 4 . This tells the optimization engine: "Find a time where Resource A (Appointment 1) and Resource B (Appointment 2) are BOTH free, and book them simultaneously."

Option A is incorrect because a single Service Appointment can typically only have one active Assigned Resource for scheduling purposes in the standard optimization model (unless using Crew Management, but Crews are for static teams, not ad-hoc pairs).

Option D is incorrect because the requirement states they need to be assigned to "individual jobs later that day" 5 . Service Crews are designed for resources who stay together all day. Breaking a crew apart for half a day is administratively difficult.

Option C is a hack (Resource Absence) that blocks the second tech's time but doesn't link them to the actual job details properly.

Global Optimization will not move appointments that are pinned by status, pinned by checkbox, or otherwise constrained by their own scheduling parameters such as an Arrival Window the customer already agreed to.

Option A is correct. Once an Arrival Window is defined on a Service Appointment, the optimizer treats the start time as fixed within that window. If most appointments already have tight Arrival Windows, the optimizer has very little room to move them.

Option B is correct. Appointments in a 'Pinned' status (configured under Field Service Settings → Optimization → Pinned Statuses) are excluded from optimization moves entirely.

Option D is correct. The 'Pinned' checkbox on the Service Appointment locks the appointment to its scheduled time, regardless of status. Optimization will not move pinned appointments.

Option C is incorrect because if appointments are scheduled in violation of Work Rules, optimization would typically reschedule them to a compliant slot, not leave them in place.

Option E is incorrect because high priority makes appointments more important to schedule, not less likely to move; the optimizer is free to relocate high-priority work.