Free Agentforce Field Service and Operations Consultant Practice Questions

The requirement is best implemented with Resource Availability, Scheduling Policy logic, and realistic travel-speed settings. Routing accuracy and appointment placement depend on the availability rule, the policy ' s Work Rules and Service Objectives, and the travel-time model. Default Travel Speed is used for aerial calculations when no resource-specific speed overrides it.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Auto Schedule is an execution setting rather than a routing factor, and street-level routing uses road-network information rather than simply computing a straight-line shortest route.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Routing; Resource Availability; Scheduling Policies; travel speed.

For this scenario, Salesforce Field Service should use Resource Preferences together with Required and Excluded Resource Work Rules. Customer feedback can be translated into Resource Preferences on Accounts or Work Orders. Required and Excluded preferences are then enforced by the corresponding Work Rules in the Scheduling Policy so unsuitable technicians are filtered and required technicians are honored.

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. Business objectives rank otherwise valid candidates; they are not substitutes for Required/Excluded filtering. Preferences also belong on customer/work records rather than on the Service Resource itself.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Resource Preferences; Required Resources; Excluded Resources.

For this scenario, Salesforce Field Service should use a custom Work Order Status plus a Validation Rule. The custom status provides a clear lifecycle state such as Awaiting Customer Signature, while the Validation Rule prevents transition to a final closed state until the signed Service Report condition is satisfied.

Reusable configuration should be preferred over duplicating records or custom objects. Work Types can standardize duration, required skills, required products, and Knowledge, while the Work Order hierarchy and Work Order Line Item hierarchy are available when genuinely separate but related work must be represented.

The alternatives address different parts of the Field Service model. An approval process is unnecessary for a deterministic signature prerequisite, and escalation rules do not govern whether a Work Order may be closed.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Order lifecycle; Validation Rules; Service Report signature.