Free Practice Questions for Salesforce AP-209 Exam

This scenario distinguishes between "External" contractors (buckets of work) and "Internal/Named" contractors (managed schedule).

Option C (Contractor A): Since they manage work outside Salesforce and work specific hours (9-10 am), they should be modeled as Capacity-Based Resources . This feature allows you to define a "bucket" of capacity (4 hours/day) without optimizing individual travel or start times. You simply dump work into their bucket until it is full.

Option A (Contractor B): Since they manage the schedule inside Salesforce (likely named users), they act like standard employees. To limit them to 4 hours of work within a 9-5 shift, you use a Work Rule (Count Rule) . You configure the rule to limit "Duration" to 240 minutes (4 hours) per day and use a Relevance Group to ensure this rule only applies to Contractor B (not internal employees or Contractor A).

To filter resources based on strict criteria (like security clearance), you use Work Rules (Hard Constraints).

Option B is correct (Match Boolean): This is a simple, effective method for binary requirements. You place a checkbox on the Service Appointment (e.g., "Requires Security Badge") and a corresponding checkbox on the Service Resource (e.g., "Has Security Badge"). The Match Boolean Work Rule enforces that if the Appointment is checked, the Resource must also be checked.

Option E is correct (Extended Match): If the requirement is more complex (e.g., matching a specific type or level of badge), the Extended Match Work Rule is best. It allows you to match a field on the Service Appointment (or Work Order) to a related list or field on the Service Resource. For example, matching the "Badge Type" required by the Government Account to the "Badge Type" held by the Resource.

Note: While Skills (Option C) are also commonly used for this, the question specifically points toward Work Rule configurations (Boolean/Extended) often used for strict compliance attributes.

Salesforce Field Service provides specific tools for capturing rich media in a structured way.

Option B is correct (Mobile Flow): This is the modern best practice. By using a Flow with the File Upload (or Image) screen component, you can guide the technician to take a photo at a specific step in the process (e.g., "Take a photo of the completed installation"). This ensures consistency.

Option A is correct (Quick Action): You can configure Quick Actions (specifically Global or Object-Specific actions for File Uploads) in the Field Service Mobile app extension settings. This provides a one-tap button for technicians to launch the camera and attach a file directly to the record.

Note: While Option D (Chatter Feed) is possible, it is unstructured data. Options A and B are the "Best Practice" recommendations for process adherence.

Priming is the process of caching data on the device so that the technician can work offline. Priming has limits, can be tuned, and must be combined with scoped list views to keep the device fast and accurate.

Option B is correct. Not every object and record is primed by default. The implementation team must map out which related records (Account, Contact, Asset, Knowledge, etc.) need to be available offline and configure priming or briefcase rules accordingly.

Option D is correct. A very low Schedule Update Frequency Time forces the device to sync constantly, draining battery and consuming bandwidth even when the technician is offline or on a poor connection. The frequency must be tuned to balance freshness against device and network impact.

Option E is correct. Scoping list views to the technician's own appointments (e.g., the next 7 days, my assignments) keeps the offline data set small and relevant, which improves performance and reduces sync time.

Option A is incorrect because the SFS Mobile App syncs automatically when connectivity is restored; the technician does not need to manually trigger a Data Sync.

Option C is incorrect because Product and Pricebook access offline is governed by priming and inventory configuration, not by whether the technician has reviewed them on the desktop.

This is a classic "Double-Booking" vs. "Complex Work" scenario.

Option B is correct. To book two distinct people for the same work at the same time, you create two Service Appointments . You link them using a Complex Work dependency of type Same Start 4 . This tells the optimization engine: "Find a time where Resource A (Appointment 1) and Resource B (Appointment 2) are BOTH free, and book them simultaneously."

Option A is incorrect because a single Service Appointment can typically only have one active Assigned Resource for scheduling purposes in the standard optimization model (unless using Crew Management, but Crews are for static teams, not ad-hoc pairs).

Option D is incorrect because the requirement states they need to be assigned to "individual jobs later that day" 5 . Service Crews are designed for resources who stay together all day. Breaking a crew apart for half a day is administratively difficult.

Option C is a hack (Resource Absence) that blocks the second tech's time but doesn't link them to the actual job details properly.

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.

When dealing with a Bring Your Own Device (BYOD) strategy (common with contractors), device compatibility is the biggest technical hurdle.

Option B is correct. Salesforce explicitly publishes a list of supported devices and operating systems (iOS and Android versions) 6 . Since the company does not own the phones, they cannot guarantee every contractor has a compatible device. The consultant must warn the client to check these specs against their contractors' hardware.

Option A is a policy decision, not a technical constraint. You can track contractor location if they agree to it.

Option C is false; Contractor licenses (Community Plus) do include access to the Field Service Mobile App.

The Service Territory Member (STM) address defines the Start Location and End Location for the resource's route calculation.

Option C is correct. The requirement states that travel from Home to the Center is "at the technician's expense" (i.e., off the clock). Therefore, the "Official Company Route" begins when they arrive at the Service Center.

By setting the STM Address to the Service Center , the optimization engine assumes the technician is at the Service Center at the start of their shift.

The engine will then calculate travel time for: Service Center - > Job 1 .

This matches the business requirement.

Option A (Home Address): If you set Home, the engine calculates: Home - > Job 1 (or Home - > Service Center). This would likely include the commute time in the daily schedule utilization, which contradicts the "at technician's expense" (off-clock) requirement.

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).