Salesforce AP-209 Dumps Questions Answers

To model international workforces in Salesforce Field Service, specific objects handle geography, time, and exceptions.

Option B is correct.

Service Territories: Used to define the geographical areas (Countries/Regions). Crucially, the Time Zone is defined on the Service Territory record.

Operating Hours: Used to define the "Permitted Working Hours" (e.g., Mon-Fri, 9-5). These are assigned to the Service Territory or Service Territory Member.

Resource Absences: Used to model time off, such as public holidays or sick days, where the resource is unavailable. (Note: Holidays can also be linked directly to Operating Hours, but Resource Absences are the distinct records created on the Gantt).

Option A is incorrect because "Business Hours" is a Service Cloud (Support) object used for Case Entitlements, not Field Service scheduling. "Resource Capacity" is used for contractors (Capacity-Based Scheduling), not for defining standard working hours.

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.

This scenario distinguishes between "External" contractors (buckets of work) and "Internal/Named" contractors (managed schedule).

Option C (Contractor A): Since they manage work outside Salesforce and work specific hours (9-10 am), they should be modeled as Capacity-Based Resources . This feature allows you to define a "bucket" of capacity (4 hours/day) without optimizing individual travel or start times. You simply dump work into their bucket until it is full.

Option A (Contractor B): Since they manage the schedule inside Salesforce (likely named users), they act like standard employees. To limit them to 4 hours of work within a 9-5 shift, you use a Work Rule (Count Rule) . You configure the rule to limit "Duration" to 240 minutes (4 hours) per day and use a Relevance Group to ensure this rule only applies to Contractor B (not internal employees or Contractor A).