Practice Free AP-209 Exam Online Questions
Question #11
After running a Global Optimization on an empty Gantt, the dispatcher at Green Energy Solutions noticed that one of the Service Appointments wasn’t scheduled, although there seems to be enough white space on the Gantt for it to fit in.
What should the dispatcher do to identify the root cause?
- A . Manually drag the Service Appointment to a place on the white space and observe what rule violations are displayed.
- B . Click on the ‘Appointment Booking’ action on the appointment from the appointments list to identify which candidates are displayed.
- C . Remove the Service Objective with the highest weight from the Scheduling Policy.
- D . Check the ‘In-Day Optimization’ checkbox on the Scheduling Policy used in the previous run, and re-run the optimization request.
Correct Answer: A
A
Explanation:
This is the standard troubleshooting procedure for "Why wasn’t this scheduled?".
Option A is correct. If there is white space, but the optimizer didn’t use it, there is likely a Rule Violation (Hard Constraint) preventing it (e.g., The resource is missing a Skill, the Territory doesn’t match, or the Travel Time is too long). Manually dragging the appointment to that specific spot on the Gantt triggers the rule validation logic, and the console will pop up a "Rule Violation" message telling you exactly which rule failed (e.g., "Match Skills Rule Violation").
Option B helps find valid slots, but it doesn’t explain why the current white space is invalid.
Option C addresses scoring (Objectives), not hard constraints (Rules). If there was space, the objectives would just give it a low score, not prevent scheduling entirely (unless the score was 0, but Rule Violations are the more common culprit for unscheduled work).
A
Explanation:
This is the standard troubleshooting procedure for "Why wasn’t this scheduled?".
Option A is correct. If there is white space, but the optimizer didn’t use it, there is likely a Rule Violation (Hard Constraint) preventing it (e.g., The resource is missing a Skill, the Territory doesn’t match, or the Travel Time is too long). Manually dragging the appointment to that specific spot on the Gantt triggers the rule validation logic, and the console will pop up a "Rule Violation" message telling you exactly which rule failed (e.g., "Match Skills Rule Violation").
Option B helps find valid slots, but it doesn’t explain why the current white space is invalid.
Option C addresses scoring (Objectives), not hard constraints (Rules). If there was space, the objectives would just give it a low score, not prevent scheduling entirely (unless the score was 0, but Rule Violations are the more common culprit for unscheduled work).
Question #12
A division of Green Energy Solutions has different work hours for each day, and the daily hours are inconsistent from one week to another (example: this Monday 9 am-4 pm, this Tuesday 8 am-6 pm,
next Monday 8 am-3 pm, next Tuesday 9 am-2 pm). This creates a lot of overhead.
What can an administrator configure to add efficiencies into their scheduling process and mitigate administrative overhead?
- A . Create Operating Hours for all combinations and build a workflow to change the Service Territory Operating Hours every week
- B . Create Operating Hours with no availability, and use Shifts to define the daily changing availability
- C . Create Operating Hours that encompasses all the hours, then create non availabilities for the hours that are off on a given day
- D . Create a Service Territory with Operating Hours that encompasses all the hours, then create jobs for the specific hours needed to be covered
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #13
What should a consultant recommend to help a customer with their initiative to reduce their carbon footprint?
- A . Remove the ‘ASAP’ Service Objective.
- B . Give ‘Minimize Travel’ Service Objective the highest weight.
- C . Add the ‘Maximum Travel from Home’ Work Rule.
- D . Remove the ‘Match Location’ Work Rule.
Correct Answer: B
B
Explanation:
Reducing a carbon footprint in field service is primarily achieved by reducing the fuel consumption and distance driven by the fleet.
Option B is correct. The Minimize Travel Service Objective calculates the travel distance/time for each potential appointment slot. By giving this objective the highest weight in the Scheduling Policy, the optimization engine will aggressively prioritize schedules that have the shortest routes, even if it means sacrificing other metrics (like "ASAP" or "Preferred Resource"). Shorter routes directly equate to less driving and lower emissions.
Option A (Remove ASAP) might help slightly by removing the urgency to book "now" (which can cause inefficient routing), but it doesn’t proactively optimize for low mileage like Option B does.
Option C (Maximum Travel Work Rule) is a hard limit (e.g., "Don’t travel more than 50 miles"). While it prevents extreme outliers, it doesn’t optimize the routes within that radius.
B
Explanation:
Reducing a carbon footprint in field service is primarily achieved by reducing the fuel consumption and distance driven by the fleet.
Option B is correct. The Minimize Travel Service Objective calculates the travel distance/time for each potential appointment slot. By giving this objective the highest weight in the Scheduling Policy, the optimization engine will aggressively prioritize schedules that have the shortest routes, even if it means sacrificing other metrics (like "ASAP" or "Preferred Resource"). Shorter routes directly equate to less driving and lower emissions.
Option A (Remove ASAP) might help slightly by removing the urgency to book "now" (which can cause inefficient routing), but it doesn’t proactively optimize for low mileage like Option B does.
Option C (Maximum Travel Work Rule) is a hard limit (e.g., "Don’t travel more than 50 miles"). While it prevents extreme outliers, it doesn’t optimize the routes within that radius.
Question #14
Green Energy Solutions employs a field workforce and must ensure they have coverage to respond to emergencies, which may occur at any given time. GES’ field service organization consists of several business units configured as Service Territories, of which a resource may support simultaneously.
Resources do not work in more than a single time zone at a given time, however, GES is looking for a solution to allow their resources to be available for emergency work in the off-hours, in all the territories that they may support.
Which solution should a consultant recommend?
- A . Service Resources cannot be assigned to more than one Service Territory
- B . Create a shift for each Service Territory the Service Resource may belong to, set the time slot type to ‘Designated’ to apply to emergencies only, and verify that the shift is contained in the Primary Territory membership dates
- C . Create a shift for the Service Resource without a specified Service Territory, use recordset filter criteria to apply to emergencies only, and verify that the shift is contained in the Primary Territory membership dates
- D . Create a shift for the Service Resource without a specified Service Territory, set the time slot type to ‘Designated’ and verify that the shift is contained in the Primary Territory membership dates
Correct Answer: D
D
Explanation:
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.
D
Explanation:
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.
1 2