Salesforce Agentforce Field Service and Operations Consultant FS-Con-101 Exam Dumps: Updated Questions & Answers (September 2026)

The correct configuration is an Excluded Resource preference on the Account. An Account-level Excluded Resource preference records that the customer should not receive that technician on future work. The Scheduling Policy ' s Excluded Resources rule can then prevent the technician from being considered.

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. Simply removing Preferred status would stop favoring the technician but would not prohibit assignment, and moving territories would affect unrelated customers.

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 — Resource Preferences; Excluded Resources; Account-level preferences.

The correct configuration is a customer-specific Price Book containing all relevant products. A Work Order uses one Price Book, so the customer-specific book should contain both negotiated-price products and ordinary products that may appear on the same Work Order. This preserves standard Product selection and pricing on Work Order Line Items.

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. A book containing only discounted items would make other required products unavailable through the normal pricing model, and a global book would not represent customer-specific negotiated prices.

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 pricing; customer Price Books; Price Book Entries.

For this scenario, Salesforce Field Service should use Products and Price Books. The consumed part is a Product, and pricing is supplied through Price Book Entries so the Product Consumed record can carry list price, unit price, discounts, and billing context.

Using the standard inventory objects keeps quantity, location, serial number, price, and service history aligned. Custom fields or improvised notes may capture text, but they do not participate in the native stock, fulfillment, consumption, and reporting processes that Field Service provides.

The alternatives address different parts of the Field Service model. Assets identify installed customer equipment, while Opportunity Line Items belong to the sales process and custom objects are unnecessary for standard Field Service part pricing.

The standard inventory model also keeps planned demand, stock position, movement, actual consumption, and pricing available for reporting without duplicating the same information in custom records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Products Consumed; Products; Price Books; pricing.

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.

The correct configuration is Gantt Palettes. Palettes color-code Service Appointments according to selected field values, including numeric and currency values. A revenue field can therefore be mapped to a palette so dispatchers immediately see high-value appointments on the Gantt.

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. Field Sets control which data is displayed, Map Report Layers add geographic overlays, and Gantt Actions perform operations rather than continuously color-coding appointment value.

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; Gantt Palettes; appointment visualization.

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.

Maintenance Plans are the native Field Service framework for recurring preventive service. They combine Assets, Work Types, recurrence, generation timeframes, and Work Order or Service Appointment generation so that future work can be created in a controlled and repeatable way.

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.

The correct configuration is Multi-Day Service Appointments. Use them when one body of work exceeds a resource ' s available working hours in a day or must continue across consecutive days, including nonworking periods such as weekends. The scheduler distributes the duration across eligible working periods.

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. Jobs requiring separate stages by different resources are better represented as separate appointments with dependencies, while a recurring same-day pattern is not a multi-day appointment.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Multi-Day Service Appointments; resource availability; complex work.

The correct configuration is a Work Order creation action from the Entitlement. The agent has already established service eligibility through the Entitlement. Creating the Work Order from that context preserves the entitlement relationship and allows Work Order SLA and milestone processing to use the appropriate support agreement.

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. A Case can also relate to a Work Order, but the decisive process point in this scenario is the validated Entitlement rather than a generic Contact or Opportunity.

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

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.

a parent Work Order with Asset-specific Work Order Line Items is the appropriate Field Service design. Work Order Line Items are the standard way to represent individual components, Assets, or tasks under one service engagement. Each line item can carry its own Asset, status, Work Type, products, skills, pricing, and appointment when needed.

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. Separate parent Work Orders are only necessary when the work must have independent job lifecycles; Products Consumed records materials used, not the component-level work structure.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Orders; Work Order Line Items; Asset-level service tracking.