Pass the Salesforce Field Service Lightning program FS-Con-101 Questions and answers with ExamsMirror

the Reshuffle action is the appropriate Field Service design. Reshuffle is designed to insert important work into an already populated schedule by moving lower-priority appointments to other times, days, or resources as allowed by the Scheduling Policy.

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. A normal reschedule changes a selected appointment but does not provide the same schedule-wide rearrangement around the incoming high-priority work; custom Apex is unnecessary.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Reshuffle; appointment priority; in-day schedule adjustment.

For this scenario, Salesforce Field Service should use Time Sheet Entries related to Work Orders and Work Order Line Items. Time Sheets represent a resource ' s reporting period, while Time Sheet Entries capture individual blocks of labor. Standard associations let those entries be attributed to an overall Work Order or to a specific Work Order Line Item for task-level costing and reporting.

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. Assigned Resource belongs to the broader time-sheet/resource relationship, and Service Appointment is not one of the two standard work associations requested here.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Time Sheets; Time Sheet Entries; Work Orders; Work Order Line Items.

Work Types is the appropriate Field Service design. Work Types standardize recurring categories of field work by defining expected duration, skills, products, Knowledge, and other reusable settings. Applying them to Work Orders reduces repetitive data entry and improves scheduling consistency.

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. Cloning Work Orders or creating child Work Orders for repetitive visit types duplicates record-specific information and does not provide the same reusable template governance.

This structure preserves a clean audit trail from the original service requirement through individual tasks and visits, which improves downstream reporting, pricing, inventory, and service-history accuracy.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Types; standardized Work Order creation.

The correct configuration is Service Report Language on the Work Order. The Work Order-level language field controls the language used for the Service Report generated for that work and its related appointments or line items. This lets the technician produce customer-facing documentation in the appropriate language.

When comparing Salesforce Mobile with Field Service Mobile, the latter should be treated as an operational field-work client rather than a generic CRM client. Its offline capabilities, appointment-centric experience, signature/report functions, geolocation controls, and technician-specific actions are the features that should drive the configuration decision.

The alternatives address different parts of the Field Service model. Changing the organization or technician user language is too broad and does not scale to customers who require different report languages.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Report Language; Work Orders; multilingual reports.

The correct configuration is Products Required on the Work Type. A Work Type acts as a reusable template for recurring service. Adding standard parts to its Products Required related list lets those requirements flow to Work Orders or Work Order Line Items when the Work Type is applied.

Inventory design should also preserve pricing and traceability. Price Books and Price Book Entries supply commercial pricing, while serialized inventory gives unit-level identity when individual items must be tracked. Product Requests and Product Transfers manage replenishment and movement rather than the underlying job structure.

The alternatives address different parts of the Field Service model. Product Items show stock at a Location, and custom Flow or layout fields do not replace the standard reusable Products Required model.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Work Types; Products Required; inventory planning.

Root Work Order and Root Work Order Line Item for multilevel hierarchies is the appropriate Field Service design. Root fields are most valuable when both Work Orders and Work Order Line Items have more than one hierarchy level because they provide direct visibility to the top-level record without navigating through intermediate parents.

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. With only a single hierarchy level, the immediate Parent fields already provide most of the relationship context and the Root fields add less value.

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 hierarchies; Work Order Line Item hierarchies; Root fields.

For this scenario, Salesforce Field Service should use Territory and Resources filters. Filtering by Territory isolates the geographic operating area and its local scheduling context, while filtering by Resources narrows the Gantt to the technicians the dispatcher is actively managing.

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. Hours changes the visible time range but does not isolate the multi-time-zone workforce, and Skills filtering serves qualification searches rather than general console simplification.

The recommended choice also keeps the decision inside the native scheduling framework, so future optimization and dispatcher actions evaluate the same constraints consistently instead of relying on manual workarounds.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Dispatcher Console filters; Territory; Resources.

a Map Polygon to select affected appointments is the appropriate Field Service design. The outage is geographic, so drawing a polygon around the affected area lets the dispatcher identify appointments inside the boundary and perform bulk scheduling actions such as reschedule.

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. A new Scheduling Policy does not identify the impacted records, notifications do not actually change the schedule, and a report adds extra steps without the same direct geographic interaction.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Dispatcher Console map; polygons; bulk rescheduling.

Street Level Routing and Default Travel Speed is the appropriate Field Service design. Street Level Routing uses road-network information to produce more realistic point-to-point travel estimates. Default Travel Speed is also important for aerial routing and acts as the fallback when a resource-specific speed is not configured.

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. Actual Travel Time records what happened after travel, while Minimize Travel is an objective and does not correct an unrealistic underlying estimate.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Street Level Routing; Default Travel Speed; travel-time accuracy.

The requirement is best implemented with Cannot Complete plus a new Service Appointment on the same Work Order. The technician made the visit but could not perform the work because the customer was unavailable. Marking the original appointment Cannot Complete preserves the failed-visit history, and a new appointment records the follow-up visit under the same underlying Work Order.

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. In Progress would misstate the final outcome, Complete would imply successful service, and a new Work Order is unnecessary because the service requirement itself has not changed.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Service Appointment lifecycle; Cannot Complete; follow-up visits.