FS-Con-101 Salesforce Agentforce Field Service and Operations Consultant Free Practice Exam Questions (2026 Updated)

the Crew Management tool is the appropriate Field Service design. Crew Management lets the dispatcher add an appropriately skilled Service Resource to the existing crew for the required timeframe, correcting the crew ' s skill composition without replacing the appointment.

For resource design, the consultant should model the real operational constraint at the correct layer: skills for expertise, capacity for outsourced workload, crew membership for coordinated teams, Operating Hours and absences for availability, and permission sets for user capabilities. Mixing these concepts leads to inaccurate scheduling behavior and unnecessary customization.

The alternatives address different parts of the Field Service model. Creating another appointment or editing the appointment to add an independent resource bypasses the crew membership model; changing the Work Type changes requirements, not the active crew composition.

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

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 Quick Action that creates a Service Appointment. The unfinished work remains part of the existing Work Order; only a new visit is required. A mobile Quick Action can create another Service Appointment against that Work Order so the follow-up can be scheduled and tracked independently.

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. Creating a new Work Order would fragment the original service requirement, while Visualforce, custom buttons, or macros add unnecessary customization when a standard mobile action satisfies the requirement.

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 Quick Actions; follow-up Service Appointments.

For this scenario, Salesforce Field Service should use Page Layouts. Field Service Mobile uses assigned layouts to determine which Work Order and Service Appointment fields and related information technicians see. Appropriate profile/record-type layout assignments therefore provide the standard way to simplify the mobile record view.

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. Field Sets apply to specific configurable surfaces, Visualforce is custom development, and Mini-Page Layouts do not drive the normal Field Service Mobile record experience.

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; Page Layouts; technician record views.

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.

For this scenario, Salesforce Field Service should use Operating Hours on the Account. The time restriction belongs to the customer, so Account Operating Hours are the correct representation of when service can be performed at that customer site. Scheduling can then respect the customer-specific availability window.

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. Service Territory and Service Territory Member Operating Hours describe resource availability; placing the restriction there would incorrectly constrain other customers or technicians.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Account Operating Hours; customer availability; scheduling constraints.

The correct configuration is Territory Timezone in the Dispatcher Console. Displaying the Gantt in Territory Timezone lets dispatchers interpret appointments according to the local time where the work is being performed, which is essential when one dispatcher manages multiple time zones.

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. Changing the dispatcher ' s user time zone works for only one locale at a time, and a formula field does not change the time scale used by the scheduling interface.

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 timezone; Territory Timezone.

The correct configuration is Products Required on Work Orders and Work Order Line Items. Field Service lets planned inventory requirements be attached at the overall Work Order level or at the specific Work Order Line Item level. This supports both job-wide material needs and task-specific parts.

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. Service Resources hold inventory through Product Items at Locations, while Service Appointments are scheduling records rather than the standard parent for Products Required.

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

The correct configuration is Service Territories sized to fewer than about 50 resources. Scheduling and optimization quality improves when territories are kept within practical resource and appointment volumes. Splitting 140 resources into three territories yields roughly 46–47 resources per territory and approximately 800 appointments per day if demand is balanced.

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. Two territories would leave about 70 resources in each, while polygons inside one very large territory do not reduce the number of resources the scheduling engine must consider.

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 Territory design; optimization scalability; dispatcher performance.

The requirement is best implemented with Products Required and Skill Requirements. A first-time fix depends on sending a technician who has both the required expertise and the expected parts. Skill Requirements filter or rank qualified resources, while Products Required communicate the material expected for the job.

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. Products Consumed records what was actually used after execution; estimated duration and SLA information do not ensure that the technician has the required competence and inventory.

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; Products Required; Skill Requirements; first-time fix.

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 requirement is best implemented with Field Service Resource Permissions plus a Scheduling license. The Scheduling license lets the technician participate in scheduling and appear on the Gantt, while Resource Permissions provide the minimum operational rights needed to work with and update assigned appointments.

Field Service access combines Salesforce object permissions with Field Service permission-set licenses and managed sharing. The correct design applies least privilege: technicians, agents, dispatchers, contractors, and administrators should receive only the capabilities required for their operational persona.

The alternatives address different parts of the Field Service model. Mobile access alone does not satisfy the scheduling requirement, and Admin permissions grant far more configuration authority than a technician requires.

This approach follows least-privilege design and keeps access changes maintainable as resources, territories, assignments, or user responsibilities change.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Field Service Resource Permissions; Scheduling license; technician persona.

Customer First and Soft Boundaries is the appropriate Field Service design. Customer First emphasizes preferred resources and prompt service while still considering efficiency. Soft Boundaries applies similar customer-oriented objectives but permits appropriate resource sharing across territory boundaries, which can improve coverage.

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. High Intensity prioritizes throughput during heavy demand, and Emergency Policy is designed for urgent emergency work rather than normal preferred-resource commitments.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Standard Scheduling Policies; Customer First; Soft Boundaries.

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

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

Candidates/Get Candidates, Bulk Schedule, and Schedule is the appropriate Field Service design. These actions use the Scheduling Policy to evaluate resource eligibility and scheduling quality. Candidates exposes options, Bulk Schedule handles multiple selected appointments, and Schedule automatically places an individual appointment under policy logic.

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. Change Status to Dispatch does not perform policy-based scheduling, and manually editing a resource assignment bypasses the scheduling engine ' s candidate evaluation.

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 scheduling actions; Scheduling Policies.

The correct configuration is Customer First and Soft Boundaries. Customer First emphasizes preferred resources and prompt service while still considering efficiency. Soft Boundaries applies similar customer-oriented objectives but permits appropriate resource sharing across territory boundaries, which can improve coverage.

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. High Intensity prioritizes throughput during heavy demand, and Emergency Policy is designed for urgent emergency work rather than normal preferred-resource commitments.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Standard Scheduling Policies; Customer First; Soft Boundaries.

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.

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.