Salesforce Certified Agentforce Field Service and Operations Consultant FS-Con-101 Exam Questions

Answer : C

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.

Answer : A

Emergency scheduling is the appropriate Field Service design. Emergency scheduling is designed to insert urgent work into an active day, identify an appropriate nearby technician, and dispatch the appointment even when normal schedules are already occupied.

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. Get Candidates is a general candidate-evaluation action, Appointment Booking is aimed at finding bookable slots, and Fill-In Schedule uses gaps for nonurgent work rather than interrupting the plan for an emergency.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization --- Emergency scheduling; Dispatcher Console; urgent dispatch.

Answer : A, B

The requirement is best implemented with 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.

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. 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.

Answer : A

two Service Appointments assigned to two different resources is the appropriate Field Service design. Because the technicians can arrive at different times, their work must be independently schedulable. Separate Service Appointments allow each technician to have independent timing, travel, and assignment while still supporting the same overall job.

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 single appointment with two resources is more appropriate for a crew-style simultaneous visit, and Required Resources on one appointment would not provide separate scheduling windows.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization --- Multiple Service Appointments; independent resource scheduling.

Answer : C

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.

Answer : C

For this scenario, Salesforce Field Service should use Field History Tracking on Assets. Field History Tracking records changes to selected Asset fields with timestamps, user information, and prior/new values where supported. Enabling it on lifecycle fields such as Status and location-related attributes gives managers an audit trail for a specific installed component.

Asset relationships and hierarchy fields provide different views of the installed base. Parent and Root Asset fields model structural hierarchy, while Asset Relationship records can model replacement, upgrade, or other lifecycle relationships. Field History Tracking complements those relationships by auditing changes to selected Asset fields over time.

The alternatives address different parts of the Field Service model. A Work Order related list shows service activity but not every field change, while custom tracking fields duplicate native auditing capability.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets --- Assets; Field History Tracking; lifecycle audit.

Answer : C

The correct configuration is Quantity Unit of Measure configured for meters. Field Service inventory supports units of measure on products and downstream inventory records. Adding or using Meters as the Quantity Unit of Measure lets technicians record cable requirements and consumption in the metric unit consistently.

Field Service inventory distinguishes the product catalog from stock at a location and from inventory movement or consumption. Products define what the item is, Product Items represent how much of that Product is at a specific Location, Products Required describe planned needs, and Products Consumed record what was actually used during execution.

The alternatives address different parts of the Field Service model. Price Book configuration governs commercial pricing and organization locale governs regional formatting; neither changes the physical inventory measurement unit.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory --- Quantity Unit of Measure; Products; Product Items; consumed quantities.