Salesforce AP-209 Exam Dumps

Resource Preferences are supported on Work Order Line Items, which makes the parent/child Work Order pattern fully usable for jobs that require specific resources with specialized skills.

Option C is correct. Resource Preferences can be added directly to the Work Order Line Item, with type 'Required' or 'Preferred', referencing the Service Resource(s) qualified for the specialized work. The scheduling engine respects those preferences when picking candidates for the WOLI's Service Appointment.

Option A is incorrect because Resource Preferences are supported in Complex Work scenarios, including WOLI-based hierarchies.

Option B is incorrect because Resource Priority ranks all resources globally; it doesn't target specific resources for a specific Work Order Line Item.

Option D is incorrect because Resource Preferences are supported on WOLI out of the box and do not require redesigning the data model.

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.

Service Crews are the Field Service feature designed for situations in which two or more resources must work together on the same Service Appointment, with one assignment representing the whole crew.

Option A is correct. Modeling the senior and junior as members of a Crew, and assigning the Service Appointment to the Service Crew Resource, ensures they show up together for the same job and the same time slot. The crew composition can be updated as the junior gains experience.

Option B is incorrect because two separate Service Appointments do not guarantee that both resources arrive at the same time on the same site, and they double-count the work for reporting.

Options C and D are incorrect because Multi Stage Work is intended for sequential or simultaneous jobs that produce different outputs --- not for two resources performing the same activity together. Crews are the supported pattern for joint-execution work.

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.

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.