Salesforce AP-209 Exam Questions

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.

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.

This addresses the 'Shift vs. Operating Hours' architecture.

Option B is correct. When a schedule has no consistent weekly pattern, using standard Operating Hours (which repeat Mon-Sun indefinitely) is inefficient. The best practice is to assign the Service Territory Member (the resource) a 'Shell' Operating Hours record that has zero time slots (No Availability).

You then use Shifts to define the specific working times for specific dates (e.g., 'Nov 1st: 9am-2pm').

Because the base Operating Hours are empty, the Scheduling Engine looks only at the Shifts to determine availability. This avoids the conflict of having to 'subtract' time from a standard day or constantly update the base record.