Salesforce AP-209 Exam With Confidence Using Practice Dumps

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.

When running optimization (Global or In-Day), the engine is allowed to move any appointment that is not "Pinned."

Option C is correct. In Salesforce Field Service, you must explicitly define which statuses are considered Pinned (immovable) during optimization. This is configured in Field Service Settings > Optimization > Logic . If the 'In Progress' status is not selected in the "Pinned Statuses" list, the optimization engine sees that appointment as movable. To improve the schedule, it might unassign the current tech and assign a different one, even though the tech is already on-site.

Ensuring 'In Progress' is "excluded from optimization logic" (Pinned) forces the engine to schedule around that appointment rather than moving it.

Option B refers to "Status Transitions," which controls the lifecycle flow (e.g., New - > Scheduled - > In Progress) but does not control the scheduling engine's permission to move the job.

Operating Hours model the working schedule, while Skills model what kind of work a resource is qualified to perform. Combining the two correctly meets both the availability and the work-type filter.

Option B is correct. Separate Operating Hours definitions allow you to model the different working hours and time zones used by internal vs. third-party resources. Using Skills to restrict the contractor resources to maintenance work is the standard way to enforce the type of work they should perform, by tagging the relevant Work Types (or Work Orders) with a 'Maintenance' skill that only the contractors hold.

Option A is incorrect because 'Designated Work' Time Slots are normally used to reserve specific blocks of time for a specific category of work — they are not designed to restrict a resource exclusively to maintenance across all its working hours.

Option C is incorrect because using only Shifts on top of a single Operating Hours record adds unnecessary complexity when the schedules differ structurally; separate Operating Hours definitions are cleaner.

Option D is incorrect for the same reason, and because it does not include any mechanism to restrict the contractors to maintenance work only.