Salesforce AP-209 Exam Questions

Work Rules are hard constraints that filter candidates in or out, while Service Objectives are soft constraints that rank the remaining candidates. The 40-mile radius is a strict eligibility rule, while preferring contractors over internal employees is a preference.

Option D is correct. A Work Rule (such as Maximum Travel From Home with a Relevance Group for contractors) enforces the 40-mile radius as a hard filter --- contractors beyond that distance are excluded from the candidate list. A Service Objective (such as a Resource Preference or Resource Priority objective) is the correct mechanism to rank contractors above internal employees while still allowing internal employees to be considered when no contractor is available.

Option A is incorrect because a Service Objective cannot enforce the maximum travel as a hard rule; it would only score it.

Option B is incorrect because using a Work Rule for the contractor preference would exclude internal employees, violating requirement #1.

Option C is incorrect because the roles of the rule types are reversed --- travel limit needs to be a Work Rule and preference needs to be a Service Objective.

Salesforce Field Service uses two distinct KPIs for service contracts: Availability and Reliability. The two differ in whether planned downtime (scheduled maintenance) is counted against the asset.

Option C is correct. Availability measures the proportion of expected uptime that the Asset was usable, excluding only unplanned downtime. Planned maintenance is expected and excluded from the calculation, so Availability = (expected uptime - unplanned downtime) / expected uptime.

Option D is partially right in form but mislabeled --- Reliability is the metric that subtracts both planned and unplanned downtime: Reliability = (expected uptime - planned - unplanned downtime) / expected uptime. Mislabeling it as the Availability formula (Option A) is incorrect.

Option A is incorrect because that is the Reliability formula, not Availability.

Option B is incorrect because Asset Uptime is the numerator of these formulas, not a ratio of Availability divided by Reliability.

Capacity-Based Scheduling is a simplified scheduling model (buckets of work) compared to the standard, granular optimization. Because it ignores specific travel times and start times, it has significant limitations.

Option B is correct: Capacity-Based Resources (contractors) cannot be assigned Multi-Day Service Appointments. They work on a 'Hours per Day' or 'Jobs per Day' limit, and the system cannot span a single appointment record across multiple days for them.

Option C is correct: They cannot handle Complex Work (dependencies like 'Start Same Time' or 'Follow Immediately'). Since the engine doesn't calculate their precise start time (it just ensures they have enough hours in the day), it cannot synchronize their work with other resources.

Option D is incorrect: You cannot create a Service Crew composed of Capacity-Based resources.

To exclude a specific subset of resources from being scheduled by the optimization engine, you use a Hard Constraint Work Rule.

Option D is correct. The Match Boolean Work Rule is designed to filter resources based on a checkbox (Boolean) field.

You would create a custom checkbox on the Service Resource object (e.g., Is_Contractor__c).

You configure the Match Boolean rule in the Scheduling Policy to enforce that Is_Contractor__c must be False.

When optimization runs, any resource where Is_Contractor__c = True fails the rule and is completely ignored/excluded from the schedule calculation.

Option A (Count Rule) limits volume, it doesn't exclude.

Options B and C (Match Field/Extended Match) match properties between the Job and the Resource (e.g., Skill or Location matching), which is not the same as a blanket exclusion of a resource type.

Capacity-Based Scheduling is a simplified scheduling model (buckets of work) compared to the standard, granular optimization. Because it ignores specific travel times and start times, it has significant limitations.

Option B is correct: Capacity-Based Resources (contractors) cannot be assigned Multi-Day Service Appointments. They work on a 'Hours per Day' or 'Jobs per Day' limit, and the system cannot span a single appointment record across multiple days for them.

Option C is correct: They cannot handle Complex Work (dependencies like 'Start Same Time' or 'Follow Immediately'). Since the engine doesn't calculate their precise start time (it just ensures they have enough hours in the day), it cannot synchronize their work with other resources.

Option D is incorrect: You cannot create a Service Crew composed of Capacity-Based resources.