Important Salesforce AP-209 Exam Questions

Answer: B

Explanation:

The goal is to prevent low-priority 'Inspections' from being ignored indefinitely until they miss their deadline, without permanently ranking them above high-value 'New Installs.'

Option B is correct (based on the scenario's specific constraints). By using automation to elevate the Inspection's priority to '1' (High) only when it is due 'tomorrow,' the system treats it as urgent only when necessary to avoid the penalty. Since 'New Installs' are also Priority '1', the two will compete on equal footing on that final day, ensuring the Inspection has a fighting chance to be scheduled alongside high-value work.

Option C (Dynamic Priority) is a standard solution for 'aging' work. However, the option states it caps the value at '2'. In standard SFS priority (where 1 is highest), a '2' will never beat a '1'. Therefore, the inspection would still likely be bumped by a New Install (Priority 1) even on its due date, leading to a penalty.

Option D ('Schedule Over Lower Priority') is used for emergency reshuffling, but does not inherently solve the prioritization logic between these two specific task types.

Answer: 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.

Answer: A, C, D

Explanation:

During Scoping (the initial phase), the goal is to align on the 'What' and 'Why' before moving to the 'How.'

Option A is correct (Work Parameters): You must define what constitutes a 'Job' (Work Order), how long it takes, and what skills are needed. This is the foundation of the data model.

Option C is correct (Terminology): Mapping the customer's language to Salesforce terms (e.g., 'We have 'Truck Rolls' -> In Salesforce, that is a 'Service Appointment'') is crucial to avoid confusion throughout the project.

Option D is correct (Project Objectives): Defining what is 'Essential' (MVP) vs. 'Nice to Have' sets the project boundaries and success metrics.

Option B (Sprint Review) happens during the build phase (Agile methodology), not during initial scoping.

Option E (Solution Design) is the output of the scoping/analysis phase, not a topic you ask about during the initial discovery.

Answer: C

Explanation:

This scenario involves two distinct types of work (Installation vs. Training) with different durations and likely different skill requirements, but they are part of the same customer order.

Option C is correct.

Data Model: Using Work Order Line Items (WOLIs) is the best practice here. You create one WOLI for the 'Installation' (linked to a Work Type that allows Multi-Day) and a separate WOLI for 'Training' (linked to a different Work Type). This allows you to track the status and skills for each part separately.

Dependency: Using Complex Work (specifically a 'Start After Finish' dependency) ensures the Training appointment cannot be scheduled until the Installation is complete.

Option A puts both Appointments on the same Work Order parent. While possible, it makes it harder to report on 'Training' vs 'Install' costs separately and limits the ability to use different Work Types for each appointment automatically.

Option B relies on manual updates or custom automation ('When scheduled, update...'), whereas Complex Work (Option C) handles the logic natively during optimization.

Answer: B, D, E

Explanation:

Custom Actions (configured in Field Service Settings) allow dispatchers to trigger Apex classes or Visualforce pages/components from the console.

Option B is correct: You can add custom actions to the Resource List on the Gantt (e.g., right-click a technician's name to 'Send SMS' or 'Show on Map').

Option E is correct: You can add custom actions to individual Service Appointments (e.g., right-click an appointment bar or list item to 'Reschedule' or 'Print Label').

Option D is correct: You can add Mass Actions to the Appointment List (select multiple checkboxes -> Actions -> 'Bulk Dispatch').

Note: You generally cannot perform custom actions on the 'Service Territory' grouping headers (Option A) or multiple resources simultaneously (Option C) in the standard UI.