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

The requirement is best implemented with one Work Order Line Item per Asset and one Service Appointment per Work Order. This combination preserves an individual record for every installed Asset while consolidating the quarterly inspection into one field visit. Asset-specific line items provide compliance detail; the single parent appointment represents the one required onsite attendance.

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. One Work Order per Asset or one Service Appointment per line item would fragment the inspection into multiple jobs or visits and conflict with the requirement for a single visit.

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; Work Order generation; Service Appointment generation.

the appointment owner and members of the relevant User Territory is the appropriate Field Service design. With private sharing, Field Service uses managed sharing and territory public groups. Once a Service Appointment is canceled, assigned-resource access is no longer the primary path; the owner and users with the appropriate User Territory access retain visibility.

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. Service Territory membership and Assigned Resources serve different scheduling and access functions; the cancelled state changes which automatic sharing paths remain applicable.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Private OWD; User Territories; Service Appointment sharing.

The correct configuration is the correct Field Service Mobile action placement and supported action type. Actions can appear in Salesforce Mobile but not Field Service Mobile when they are not placed in the required publisher-action section or when an unsupported legacy Lightning Component action type is used. Field Service Mobile has its own supported action model.

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. Mobile navigation settings do not substitute for the page-layout action configuration, and the mobile client does not automatically surface every action that appears elsewhere in Salesforce.

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; page layouts; supported quick-action types.

The correct configuration is Work Order Line Items, each with its own Service Appointment. Each task must retain its own completion, inventory, pricing, and scheduling information. A Work Order Line Item provides the task record, and a child Service Appointment allows that task to be scheduled to the same or a different technician as required.

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. Custom objects are unnecessary, and using Service Appointments as the parent of task records reverses the standard Field Service data model.

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 Line Items; child Service Appointments; task scheduling.

The requirement is best implemented with the Match Boolean Work Rule for Active Resources. A Match Boolean rule can require the Service Resource Active flag to be true, filtering inactive resources out of candidate evaluation while preserving their historical records.

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. Preferred and Required Resources model preferences, while Match Fields compares data values but is not the standard Active-resource boolean control.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Match Boolean Work Rule; Active Resources; Scheduling Policies.

The correct configuration is separate Work Orders or separate Work Order Line Items with their own Service Appointments. Independent handling requires each Asset ' s work to have an independently schedulable Service Appointment. This can be achieved with separate Work Orders and appointments or with one Work Order containing Asset-specific line items, each with its own appointment.

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 parent-level appointment would combine the Assets into one scheduling unit and would not let each container ' s service be handled independently.

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

The requirement is best implemented with one Work Order and one Service Appointment assigned to the Crew-type Service Resource. The Service Crew is represented for scheduling by a Service Resource whose Resource Type is Crew. Assigning that resource to the appointment allows the two active crew members to participate together in the same visit.

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. Assigning directly to the Service Crew record or creating separate appointments for each member bypasses the standard crew scheduling model.

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-type Service Resource; Assigned Resources.

The requirement is best implemented with Product Item. A Product Item represents a specific Product at a specific inventory Location and records quantity on hand. It is therefore the correct object for understanding distribution of an expensive part across warehouses, technician vans, and other inventory locations as stock is reused and replenished.

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. Assets represent installed customer equipment, Maintenance Plans create recurring work, and Entitlements govern service eligibility rather than stock distribution.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Product Items; Locations; inventory quantities and transactions.

The requirement is best implemented with Resource Availability, Scheduling Policy logic, and realistic travel-speed settings. Routing accuracy and appointment placement depend on the availability rule, the policy ' s Work Rules and Service Objectives, and the travel-time model. Default Travel Speed is used for aerial calculations when no resource-specific speed overrides it.

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. Auto Schedule is an execution setting rather than a routing factor, and street-level routing uses road-network information rather than simply computing a straight-line shortest route.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Routing; Resource Availability; Scheduling Policies; travel speed.

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 requirement is best implemented with Arrival Window Start and Arrival Window End. Arrival windows are the customer-facing expectation for when a technician is expected to arrive. They provide a practical range while allowing dispatchers operational flexibility if travel or earlier appointments change during the day.

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 and Scheduled End are internal scheduling values and may move as the schedule is optimized, so sharing them as hard customer commitments is usually inappropriate.

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 arrival windows; customer communications.

The requirement is best implemented with Field Service automatic sharing for dispatched Service Appointments. With private OWD, enabling the Field Service setting to share dispatched appointments with assigned resources grants the technician access based on the Assigned Resource relationship and appointment lifecycle.

With private organization-wide defaults, Field Service can use automatic sharing, User Territories, territory public groups, and assignment relationships to expose the operational records needed by technicians and dispatchers. These sharing mechanisms are distinct from the permissions that control whether a user can configure Field Service or use a particular application capability.

The alternatives address different parts of the Field Service model. Changing ownership or maintaining custom sharing rules adds unnecessary automation, while User Territories are mainly used to give dispatchers and call-center users access to territory records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Private OWD; automatic sharing; Assigned Resources.

The requirement is best implemented with a monthly Maintenance Plan with a 12-month generation timeframe and automatic generation disabled. Frequency of one month models the twelve monthly checkups, while a 12-month generation timeframe represents the annual horizon. Because the customer calls to initiate each visit, automatic Work Order generation should remain disabled and work can be generated manually when appropriate.

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. Automatically generating each month would remove the intended customer-driven control, while a one-month generation timeframe would not represent the planned annual set as efficiently.

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; Frequency; Generation Timeframe; Auto-generate Work Orders.

The correct configuration is Service Territory Member. The Service Territory Member record links a Service Resource to the territory in which the resource works. That relationship is fundamental to territory-based scheduling and sharing calculations for appointments assigned to the resource.

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. User Territory links users such as dispatchers to territory access groups; it serves a different persona and sharing purpose than the resource-territory membership relationship.

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 — Service Territory Members; resource-territory sharing.

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.

The requirement is best implemented with a Work Order Quick Action that launches a Flow. A single Flow can collect the technician ' s required information once and update the Work Order, related Service Appointment, and Case in one guided mobile interaction.

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. Multiple actions would force duplicate entry, Process Builder is not the mobile interaction layer, and a custom component adds code where a standard Flow action is sufficient.

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; Flow; cross-record updates.

The requirement is best implemented with Drip Feed dispatch. Drip Feed controls how many future Service Appointments are released to each technician. Setting the quantity to the required number keeps the technician queue small and automatically dispatches the next eligible appointment as current work is completed, canceled, or cannot be completed.

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. Manual dispatch creates avoidable administrative work, while ordinary auto-dispatch does not by itself provide the same controlled queue depth and protection from frequent schedule changes.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Drip Feed; automated dispatch; mobile appointment visibility.

the standard Service Report is the appropriate Field Service design. Service Reports are designed to summarize completed field work, include customer-facing details, capture signatures, generate a PDF, and be sent electronically. They are integrated directly into Field Service Mobile and the Work Order/Service Appointment lifecycle.

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. A generic Work Order email template or analytical report does not provide the structured service-document and signature workflow, and custom automation is unnecessary.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Reports; Service Report Templates; signatures; electronic delivery.

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.