Free Agentforce Field Service and Operations Consultant Practice Questions

For this scenario, Salesforce Field Service should use Service Territory and Scheduling Policy. The Service Territory defines the population of resources and appointments being optimized, while the Scheduling Policy supplies the Work Rules and Service Objectives used to evaluate and rank scheduling alternatives.

Operationally, the goal is to preserve schedule integrity while minimizing manual intervention. Field Service should be allowed to use the standard scheduling engine wherever possible so that resource availability, travel, appointment constraints, priorities, and territory context remain consistent across manual and automated scheduling actions.

The alternatives address different parts of the Field Service model. Work Types affect job requirements but are not required optimization-job objects, and polygons help with geography but do not replace the optimization scope or policy.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Optimization jobs; Service Territories; Scheduling Policies.

The correct configuration is Customer First and Soft Boundaries. Customer First emphasizes preferred resources and prompt service while still considering efficiency. Soft Boundaries applies similar customer-oriented objectives but permits appropriate resource sharing across territory boundaries, which can improve coverage.

Salesforce Field Service treats the Service Appointment as the primary unit of scheduling. Scheduling Policies combine Work Rules, which determine whether a resource or time slot is valid, with Service Objectives, which score valid alternatives against business priorities. The selected configuration therefore has to operate at the scheduling layer rather than merely changing descriptive fields on the parent Work Order.

The alternatives address different parts of the Field Service model. High Intensity prioritizes throughput during heavy demand, and Emergency Policy is designed for urgent emergency work rather than normal preferred-resource commitments.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Standard Scheduling Policies; Customer First; Soft Boundaries.