Pass the Salesforce Accredited Professional Certification AP-209 Questions and answers with ExamsMirror

The key here is that it is a Third-Party Contractor and a Temporary engagement.

Option C is correct.

Capacity Based: Contractors are typically modeled as "Capacity Based Resources" (buckets of work) rather than named individuals, as you usually don't track their specific travel or breaks—you just know they can take "X hours of work per day."

Giving Capacity: You would define the capacity only for the specific 3-week period. Once the capacity records end, the scheduling engine will naturally stop assigning work to them.

Options B and D (Deleting): It is never a best practice to delete a Service Resource record after use. You need the record to remain in the system to preserve the Audit Trail and historical data of the Work Orders they completed. You simply deactivate them or stop giving them capacity.

This question addresses the limits of Skills (Work Rules) vs. Extended Match (Custom Criteria).

Option B is correct. This offers the most efficient hybrid approach 9 .

Skills: Use standard Skills for the "Service Type" (e.g., "Repair," "Install"). This is simple and low-volume.

Extended Match: Use the Extended Match Work Rule to handle the "Product" matching. Instead of creating thousands of skills (e.g., "Repair-ModelX," "Repair-ModelY"), you create a custom object or field logic that matches the Asset's Product to a list of Products Supported on the Resource's record. Extended Match is designed exactly for this "Pattern Matching" without polluting the Skills table.

Option C is incorrect because creating a unique skill for every combination (100+ per resource) leads to "Skill Explosion." This bloats the data model and degrades optimization performance 10 .

Work Rules are hard constraints that filter candidates in or out, while Service Objectives are soft constraints that rank the remaining candidates. The 40-mile radius is a strict eligibility rule, while preferring contractors over internal employees is a preference.

Option D is correct. A Work Rule (such as Maximum Travel From Home with a Relevance Group for contractors) enforces the 40-mile radius as a hard filter — contractors beyond that distance are excluded from the candidate list. A Service Objective (such as a Resource Preference or Resource Priority objective) is the correct mechanism to rank contractors above internal employees while still allowing internal employees to be considered when no contractor is available.

Option A is incorrect because a Service Objective cannot enforce the maximum travel as a hard rule; it would only score it.

Option B is incorrect because using a Work Rule for the contractor preference would exclude internal employees, violating requirement #1.

Option C is incorrect because the roles of the rule types are reversed — travel limit needs to be a Work Rule and preference needs to be a Service Objective.

This scenario describes a structured process with validation (Checklist + Data + Images).

Option A is correct. Work Plans are the standard, modern feature for checklists in Salesforce Field Service. A Work Plan consists of "Work Steps." These steps can be linked to a Flow , which provides a user-friendly wizard to capture specific data inputs and upload images in a structured way.

Option B is the legacy method. Adding fields directly to the Service Appointment creates clutter and doesn't offer a step-by-step "Checklist" experience.

Option C is a security risk (too much access) and provides no process guidance.

Option D (Deep Linking) is used to jump out of the app to another app, which is not needed here since SFS can handle flows natively.

When Global Optimization fails, the issue is often related to data quality, scheduling configuration, or constraint validity rather than user permissions. Field Service provides a built-in diagnostic tool to surface such issues.

Option D is correct. The 'Health Check' tool, when run with 'Horizon Based Validations', evaluates the data, Scheduling Policy, Operating Hours, Service Resources and Service Appointments in scope of the optimization run. It surfaces issues such as missing geolocations, invalid time slots, missing skills, and inactive resources, which are common causes of optimization failures.

Option A is incorrect because logging a support ticket should be the last resort, not a first troubleshooting step. The admin should first attempt to identify the root cause using built-in diagnostics.

Option B is incorrect because Permission Sets are required for users who initiate optimization, but the question already confirms that the 'Optimization User' is active. Permission Sets would prevent the optimization from starting, not cause it to fail mid-run.

Option C is incorrect because if Optimization were not enabled, the dispatchers wouldn't be able to invoke it at all.

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.

Resource Efficiency is a multiplier that adjusts how long a particular resource needs to complete a job: duration = base duration / efficiency. An expert (efficiency > 1) takes less time, and a junior (efficiency < 1) takes more.

Option B is correct. Applying the formula to a base 60-minute job: X = 60 / 2.00 = 30 minutes, Y = 60 / 1.00 = 60 minutes, Z = 60 / 0.50 = 120 minutes.

Option A is incorrect because 90 minutes for Z does not match the formula; 60 / 0.5 = 120, not 90.

Option C is incorrect because it inverts the relationship — an expert takes less time, not more.

Option D is incorrect because it ignores efficiency entirely.

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.

This question tests the Maintenance Plan generation logic.

Option D is correct. The requirement is Single Visit (One Appointment) for Multiple Assets .

One Work Order Line Item per Asset: This groups all the assets under a single parent Work Order. Each asset gets its own line item (WOLI) for tracking purposes.

One Service Appointment per Work Order: This creates a single appointment for the parent Work Order. The technician arrives once and works through the list of line items (Assets).

Option B ("One Work Order per Asset") would create separate Work Orders (and likely separate Appointments) for every single asset, resulting in multiple visits or a cluttered schedule.

Option C ("One SA per WOLI") would explicitly create a separate appointment for every single asset line item, causing massive double-booking/overlap.

Optimization Insights is the dedicated Field Service feature that captures per-run metrics such as travel time saved, utilization, gap minimization, and unscheduled work, making it the standard way to evaluate Global Optimization quality.

Option B is correct. Enabling Optimization Insights records the before/after metrics for each optimization request — travel minutes, scheduled vs. unscheduled count, average gap, and other KPIs. The data is available on the Optimization Request object and can be reported on directly in Salesforce.

Option A is incorrect because the SFS Dashboard package is an older, less precise tool that does not capture per-run optimization data.

Option C is incorrect because the Dispatcher Console is an operational view, not an analytics surface.

Option D is incorrect because subscribing to an Analytics App is unnecessary overhead when a built-in feature exists.