Salesforce AP-209 Exam Dumps

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.

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.

During the 'Day 1' or Scoping phase of an implementation, the goal is to define the high-level architecture and business model.

A is correct: Defining Integration points (ERP, HR, Inventory) is a foundational requirement that dictates the project scope and data strategy.

D is correct: Defining the Work (Work Types, Skills, Durations) is the core of the Field Service data model. You cannot configure the system without knowing what services are being performed.

E is correct: Defining the Territory Structure (Business Units) sets up the security model, sharing settings, and resource organization.

Options B and C are incorrect for the first day because they are detailed configuration specifics (Refinement). You cannot define 'Service Objective Weights' or 'Gantt Features' until you understand the basic business goals, services, and territories.

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.

In Salesforce Field Service, the scheduling engine creates a list of 'Qualified Candidates' based on Work Rules (Hard Constraints). If a search returns too many candidates, it places a heavy load on the CPU and can degrade optimization performance.

Option D is correct because Work Rules are the mechanism used to filter candidates. Adding rules like Match Territory (ensuring the resource belongs to the territory), Maximum Travel from Home (filtering out distant resources), or Extended Match (matching custom criteria) effectively reduces the pool of eligible technicians before the system attempts to score them. This improves the speed and quality of the schedule.

Option A is incorrect because Service Objectives are 'Soft Constraints.' They rank candidates (giving them a score of 0-100) but do not remove them from the list.

Option B is a manual structural change that doesn't address the configuration issue.

Option C is incorrect because optimization performance is directly controlled by the efficiency of the configuration (Scheduling Policy).