Salesforce AP-209 Exam Dumps

The goal is to fit high-priority work into a schedule already filled with low-priority work.

Option B is correct. The system must know that the Repair jobs are more important than the Maintenance jobs. This is handled by the Scheduling Priority field (used in the optimization logic to decide which job to drop if there is a conflict) or the Priority field mapped to Service Objectives.

Option C is correct. Global Optimization is the best tool here. It will look at the entire week, see the high-priority unscheduled jobs, and the low-priority scheduled jobs. It will then un-schedule or move the maintenance jobs to make room for the urgent repairs.

Option D is correct. For Optimization to work, the existing maintenance appointments must not be Pinned. If they are pinned, the optimizer treats them as immovable rock, and it won't be able to free up the time needed for the repairs.

Option A (Manual assignment) is inefficient and risky (could double-book). Option E (Resource Schedule Optimization) optimizes one person at a time; Global Optimization is better suited for balancing the load across the whole territory.

To stop a resource from receiving work, you must mark them as inactive and ensure the scheduling engine respects that status.

Option C is correct: Deactivating the Service Resource (unchecking the 'Active' checkbox on the record) is the standard way to 'fire' or terminate a resource. It preserves history but flags them as no longer working7.

Option A is correct: You must ensure your Scheduling Policy includes the Active Resources Work Rule8. This rule explicitly tells the optimization engine: 'Do not assign appointments to any resource where Active = False.' Without this rule, the engine might still technically assign work to an inactive record if no other constraints block it.

Option B (Delete) is bad practice (data loss).

Option D (Excluded Resources) is for specific job-by-job exclusions (e.g., 'Don't send Bob to this specific customer'), not for global termination.

Global Optimization is the heavy-lifting batch process in Salesforce Field Service designed to create the most efficient schedule possible.

Option B is correct. Global Optimization uses a powerful algorithm to evaluate millions of potential combinations of resources, times, and routes to find the best overall score based on the Service Objectives.

Option C is correct. Unlike 'Appointment Booking' (which finds a slot for a single job without disturbing others), Global Optimization has the authority to reshuffle (move) existing appointments. It can slide jobs earlier or later, or reassess assignments to minimize travel time and white space (gaps) in the schedule.

Option A is incorrect; Optimization is a batch process that takes significantly longer than the near real-time 'Auto Scheduling.'

Option D describes 'In-Day Optimization.' Global Optimization is typically run overnight because it changes the whole schedule, which is disruptive during the work day.

Option E is incorrect; all scheduling methods (Global, In-Day, Resource Schedule Optimization, and Appointment Booking) utilize the Scheduling Policy (Work Rules and Objectives).

When a contractor company provides aggregate hours rather than a list of named technicians, the correct model is a Capacity-Based Resource so the engine schedules against capacity in hours, not against a specific individual.

Option A is correct. A Capacity-Based Resource lets you express '20 hours per day' as capacity, assign Operating Hours of 9:00 AM--5:00 PM that match the contractor's agreed window, and add the 'maintenance' skill to restrict the type of work routed to them.

Option B is incorrect because preferring contractors is a soft preference; it does not enforce the contractor's distinct hours or capacity.

Option C is incorrect because creating a separate Service Territory does not, by itself, model contractor capacity or restrict the work type assigned.

Option D is incorrect because a Named Resource represents a single person, not a company providing aggregate hours, and the Designated Work approach does not capture the daily capacity cap.

To prioritize junior resources without creating rigid 'hard constraints' (which might prevent scheduling altogether if no junior is available), you should use Service Objectives (Soft Constraints).

Option C is correct (Resource Priority): By assigning a higher priority value to Junior Service Resource records and adding the 'Resource Priority' objective to the scheduling policy, the optimization engine calculates a higher score for these resources. This acts as a general 'preference' to use them whenever possible.

Option E is correct (Least Qualified): The 'Skill Level' Service Objective has a setting called 'Prefer Least Qualified.' When enabled, the engine prefers the resource who has the lowest skill level that still meets the job requirement. For example, if a job requires Skill Level 50, and you have a Senior (Level 90) and a Junior (Level 55), the engine will pick the Junior. This is a best practice to prevent 'over-qualified' resources (Seniors) from being booked on routine jobs, keeping them free for complex tasks.