Earliest Start Permitted and Due Date is the appropriate Field Service design. These fields define the internal scheduling window that represents when the appointment may begin and the latest time by which it should be completed. They are the Service Appointment fields most directly aligned with SLA constraints.

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. Scheduled Start/End are scheduling outcomes, Actual Start/End record execution, and Arrival Windows are customer-facing arrival expectations rather than the core SLA boundaries.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Service Appointment constraints; Earliest Start Permitted; Due Date.

For this scenario, Salesforce Field Service should use a Maintenance Plan. Maintenance Plans are the native Field Service mechanism for recurring preventive work. They can associate Assets, Work Types, frequencies, generation timeframes, and Work Order/Service Appointment generation so service is created before predictable failures or at regular intervals.

For preventive maintenance, the objective is to create service before predictable failure while preserving accurate Asset-level history. Using the standard maintenance framework also allows recurring work to participate naturally in scheduling, inventory planning, service reporting, and SLA processes.

The alternatives address different parts of the Field Service model. Work Types describe how a job is performed but do not create a recurrence calendar; Path and custom process automation are not substitutes for the native maintenance framework.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Maintenance Plans — Maintenance Plans; recurring maintenance; Maintenance Assets.

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.

The requirement is best implemented with Case → Work Order → Service Appointment → Dispatch. The Case captures the inbound customer issue, the Work Order represents the onsite work, and the Service Appointment is the schedulable visit assigned and dispatched to a Service Resource. This is the standard service-to-field execution sequence.

The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.

The alternatives address different parts of the Field Service model. Dispatching a Work Order directly or creating an appointment before the underlying work reverses the Field Service data model and does not provide the intended parent-child structure.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Cases; Work Orders; Service Appointments; dispatch lifecycle.

The correct configuration is Work Order-specific Entitlement Processes and reusable Milestones. An Entitlement Process is created for one process type, such as Case or Work Order, and Work Order milestones can be configured in Setup. A Milestone definition can be reused in more than one entitlement process even though the processes themselves remain object-specific.

Good Work Order design also preserves the distinction between planned work and execution results. Products Required, requirements, and task structure should be established before service; Products Consumed, actual times, signatures, and completion statuses then record what actually happened in the field.

The alternatives address different parts of the Field Service model. A single process does not simultaneously apply to both Cases and Work Orders simply because the same Milestone is used.

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 SLAs; Entitlement Process Type; Milestones.

Knowledge Articles associated with Work Types, Work Orders, or Work Order Line Items is the appropriate Field Service design. Linking relevant Knowledge to the work context gives technicians job-specific procedures, specifications, and troubleshooting guidance. Work Types are especially useful because their associated articles can flow to recurring Work Orders and line items and be available in the Field Service mobile experience.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

The alternatives address different parts of the Field Service model. A generic Knowledge component or custom search action is less targeted, and deep linking between mobile apps does not solve offline contextual availability.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Knowledge in Field Service; Work Types; mobile/offline access.

The correct configuration is a new Service Appointment on the original Work Order or a new Work Order plus Service Appointment. Each physical return visit should be represented separately so the first visit remains part of the historical record. Continuing the same job can use another appointment on the existing Work Order; separately managed follow-up work can use a new Work Order and appointment.

The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.

The alternatives address different parts of the Field Service model. Rescheduling the original appointment would overwrite the timing representation of the first visit and reduce the accuracy of visit-history reporting.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Return visits; multiple Service Appointments; service history.

a Service Crew is the appropriate Field Service design. A Service Crew models multiple technicians who need to work as one coordinated schedulable unit. The crew can combine specialized skills and is represented in scheduling by a Crew-type Service Resource.

Salesforce favors reusable resource metadata over one-off record manipulation. When resource qualifications and availability are modeled correctly, the same information can support candidate selection, optimization, dispatching, reporting, and mobile execution without duplicating logic on individual jobs.

The alternatives address different parts of the Field Service model. Required Skills alone do not create a two-person team, and separate crews or separate independent appointments are unnecessary when the resources must perform the same job together.

This keeps the workforce model reusable across scheduling, dispatching, mobile execution, and reporting and avoids encoding resource logic in individual work records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Crews; Crew Members; multi-technician work.

For this scenario, Salesforce Field Service should use the required Salesforce Classic Publisher action placement. For the action type described, Field Service Mobile depends on the action being present in the appropriate publisher-action section of the assigned page layout. An action can therefore appear in Salesforce Mobile yet remain unavailable in Field Service Mobile if it is placed incorrectly.

Mobile configuration should reduce technician data entry and expose only the actions and information needed at the point of service. The strongest designs reuse the Work Order and Service Appointment data model, launch guided actions from the appropriate parent record, and keep customer-facing outputs such as signatures and Service Reports within the native Field Service workflow.

The alternatives address different parts of the Field Service model. Create-a-Record actions are supported, and App Extensions are a different extension mechanism rather than the cause of a standard page-layout quick action being absent.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Field Service Mobile actions; Classic Publisher Quick Actions.

The correct configuration is a Maintenance Plan. Maintenance Plans are the native Field Service mechanism for recurring preventive work. They can associate Assets, Work Types, frequencies, generation timeframes, and Work Order/Service Appointment generation so service is created before predictable failures or at regular intervals.

The consultant should distinguish recurrence from job definition. A Work Type describes how a recurring job is performed, while the Maintenance Plan determines when and how future work is generated. Work Order and Service Appointment generation methods then determine whether Assets are consolidated into one visit or separated into multiple jobs.

The alternatives address different parts of the Field Service model. Work Types describe how a job is performed but do not create a recurrence calendar; Path and custom process automation are not substitutes for the native maintenance framework.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Maintenance Plans — Maintenance Plans; recurring maintenance; Maintenance Assets.