Free Salesforce-Agentforce-Field-Service-and-Operations-Consultant Practice Test Questions (2026)

Explanation:
The correct object to specify a pre-defined set of parts for a recurring job like an annual service Work Order is the Work Type. A Work Type serves as a reusable template that captures standard job attributes, including the Required Products list. When a Work Order is created from a Work Type, the parts list is automatically copied over, ensuring technicians have a consistent manifest of parts for the job .

Correct Option:

D. Work Type:
This is correct because Work Types are designed to standardize recurring jobs. They hold the Required Products related list, which defines the parts needed for that type of work. When an annual service Work Order is generated from a Maintenance Plan or created manually with this Work Type, the required parts are inherited automatically .

Incorrect Option:

A. Product Request:
This is incorrect because Product Requests are used to request or transfer parts when stock is low, not to define a standard parts list for a job type .

B. Asset:
This is incorrect because Assets represent the customer's installed equipment being serviced, not the parts needed to complete the work .

C. Work Order Line Item:
This is incorrect because Work Order Line Items represent individual subtasks within a specific Work Order. While they can have their own required products, they are not the reusable template object for defining a standard parts set .

Reference:
Salesforce Field Service Documentation: Work Types capture "required products" that copy over automatically when a work order is created from the Work Type .

Explanation:
The core issue is accurately tracking that a job required multiple visits to complete. In Field Service, the Service Appointment is the schedulable unit representing a single visit by a technician. A Work Order represents the overall job to be done. To track multiple visits against the same job, you need to create additional Service Appointments on the original Work Order, rather than rescheduling or creating new Work Orders.

Correct Option:

B. Create a new Work Order and Service Appointment:
This is incorrect. A new Work Order should only be created for a new or separate job. Creating a new Work Order for a follow-up visit to the same issue fragments the service history and makes it harder to track the total effort for the original request.

D. Create a new Service Appointment on the original Work Order:
This is correct. The original Work Order represents the customer's request (e.g., "fix the oven"). Each technician visit is a Service Appointment under that Work Order. Creating a new appointment on the same Work Order allows you to track both the initial and return visits as part of the same job, providing a clear audit trail of the work performed.

Incorrect Option:

A. Reschedule the Work Order for the new date:
This is incorrect. Work Orders do not have scheduling fields; they are not the schedulable unit. Rescheduling is done at the Service Appointment level, which holds the scheduled time and resource assignment.

C. Reschedule the Service Appointment for the new date:
This is incorrect because it would overwrite the record of the first visit. Rescheduling changes the planned date of the same appointment. If the first visit already occurred and was unsuccessful, rescheduling it would erase the history of that attempt. A new Service Appointment is needed to represent the new visit while preserving the record of the first one.

Reference:
Salesforce Field Service Data Model: A Work Order represents the job, and Service Appointments are the scheduled visits required to complete it. Multiple Service Appointments can be associated with a single Work Order to handle scenarios requiring more than one visit

Explanation:
To ensure the same technician who performed the initial installation is assigned to subsequent service calls, the administrator must configure resource preferences that the scheduling engine can enforce. The two required actions are adding the Preferred Resource service objective to the scheduling policy and setting the technician as a preferred resource on the Account record.

Correct Option:

B. Add the preferred resource service objective to the scheduling policy:
This is correct because the Preferred Resource service objective is the optimization criterion that prioritizes assigning service appointments to resources marked as preferred for a given customer. Without this objective in the scheduling policy, the system will not consider resource preferences when ranking candidates .

D. Add the technician as a preferred resource on the account record:
This is correct because resource preferences are defined at the Account level to capture ongoing customer-provider relationships. When a Work Order is created for that Account, the system automatically copies the preferred resource preference to the Work Order, making the technician a candidate for prioritization .

Incorrect Option:

A. Create a child work order for maintenance on the original installation work order:
This is incorrect because creating a child Work Order does not automatically link the original technician to future service calls. Work Order hierarchy is for tracking related jobs, not for enforcing resource assignment preferences .

C. Add the technician as the required resource on the service appointment:
This is incorrect because "Required Resource" is a hard constraint, not a preference. If the technician is unavailable for a subsequent service call, the appointment cannot be scheduled to anyone else, which may cause scheduling failures. The requirement asks for the technician to be "assigned to subsequent service calls," not to make them the only option .

Reference:
Salesforce Help: Resource preferences are stored on the Account and automatically copied to Work Orders. The Preferred Resource service objective in the scheduling policy then prioritizes those resources during optimization .

Explanation:
In Salesforce Field Service, a Work Order has a single Price Book lookup field that determines which products and prices are available for its line items . Work Order Line Items inherit product selection from the parent Work Order's assigned Price Book . You cannot mix Price Book Entries from different Price Books under the same Work Order . Therefore, when components exist on separate Price Books, the only viable solution is to create separate Work Orders for each Price Book.

Correct Option:
A. Create one Work Order for each Price Book and add Work Order Line Items to the appropriate Work Order based on its Price Book.:
This is correct because each Work Order can only reference products from its assigned Price Book. By creating separate Work Orders, the agent ensures that line items for Preferred Price Book components are added to one Work Order, while U.S. Price Book components go to another. This preserves accurate pricing for all components while maintaining proper tracking.

Incorrect Option:

B. Create one Work Order and add Work Order Line Items based on the Price Book selected on the Work Type.:
This is incorrect because the Work Type does not dynamically assign different Price Books to individual line items. The parent Work Order's Price Book governs what products are available, and a single Work Order cannot reference multiple Price Books simultaneously.

C. Create one Work Order and override the price on Work Order Line Items for products on the Preferred Price Book.:
This is incorrect because overriding the Unit Price field does not solve the fundamental data integrity issue. The Product lookup on a Work Order Line Item only lists products from the parent Work Order's Price Book. Products on the Preferred Price Book would not even be selectable if the Work Order uses the U.S. Price Book .

D. Create one Work Order for each Price Book and use Work Types to assign the Price Book to each Work Order Line Item.:
This is incorrect because Work Types do not have the capability to assign different Price Books to individual line items. While Work Types can define default products and services, they cannot override the parent Work Order's Price Book assignment for line item pricing .

Reference:
Salesforce Help: "The Price Book associated with the work order. Adding a price book to the work order lets you link each work order line item to a product included in the price book." Work Order Line Item Product lookup only lists products from the parent Work Order's Price Book .

Explanation:
When a customer returns a defective product instead of scheduling a service visit, Salesforce Field Service tracks this through the Return Order object and its child Return Order Line Items. The Return Order represents the overall return transaction (customer, shipping, reason), while each Return Order Line Item represents an individual product being returned . This standard data model supports tracking, reporting, and inventory adjustments for customer returns .

Correct Option:

D. Create a Return Order and Return Order Line Item.:
This is correct because the Return Order serves as the parent record for the return transaction, and Return Order Line Items capture the specific products being returned . This enables proper tracking of defective products, return reasons, and inventory reconciliation.

Incorrect Option:

A. Create a Return Order and relate it to the Product.:
This is incorrect because while Return Orders can reference products, the proper child record for tracking individual returned items is the Return Order Line Item, not a direct relationship to the Product object .

B. Create a Work Order and Work Order Line Item.:
This is incorrect because Work Orders are for scheduling and tracking service work performed at a customer location. Returns without service visits should use Return Orders instead .

C. Create a Product Request and Product Request Line Item.:
This is incorrect because Product Requests track parts that need to be requested, transferred, or returned for a service appointment—they are not used for standalone customer returns without a scheduled visit .

Reference:
Salesforce Help: Track Customer Returns in Field Service — Use Return Orders to track and facilitate products returned for repair or reimbursement, with Return Order Line Items for each returned product .

Explanation:
The three objects associated with the Work Type are used to standardize job requirements so that work orders created from the template inherit the necessary skills, knowledge, and parts. These associations ensure consistency across field service operations and help the scheduling engine match the right resources and inventory to each job.

Correct Option:

B. Skill Requirements:
This is correct. Work Types include a Skill Requirements related list where you specify the skills and proficiency levels needed to perform the job. When a Work Order is created from the Work Type, these skill requirements are automatically copied to the Work Order, ensuring the scheduling engine can match qualified resources .

C. Articles:
This is correct. Knowledge articles can be attached to Work Types, providing technicians with relevant documentation, procedures, or specifications. When the Work Type is applied to a Work Order, the attached articles become available to the assigned technician .

E. Products Required:
This is correct. The Products Required related list on a Work Type specifies the parts or materials typically needed to complete the job. These required products are inherited by Work Orders created from the Work Type, helping ensure technicians have the correct parts on hand .

Incorrect Option:

A. Resources:
This is incorrect. While Work Types influence which resources are assigned through their Skill Requirements and other attributes, there is no direct "Resources" related list on the Work Type object. Resource assignment is determined by the scheduling engine based on skills, availability, and other criteria, not by a direct association on the Work Type .

D. Service Appointments:
This is incorrect. Service Appointments are schedulable records that represent a visit to perform work. While a Work Type can auto-create a Service Appointment, there is no direct related list associating Service Appointments to the Work Type itself. Service Appointments are associated with Work Orders or Work Order Line Items, not directly with Work Types .

Reference:
Salesforce Help: Work Types capture standard job attributes including required skills, products, and knowledge articles. When work orders are created from a Work Type, these associations copy over automatically to ensure consistency.

Explanation:
When the Service Appointment sharing model is set to Private, Service Resources need to be granted access to appointments assigned to them. The Service Territory Member object is the standard mechanism that connects a Service Resource to a Service Territory, and this membership drives the automatic sharing of Service Appointments within that territory. This ensures technicians can see the appointments dispatched to them without manual sharing configuration .

Correct Option:

C. Service Territory Member:
This is correct because Service Territory Member records associate Service Resources with specific territories. When a Service Appointment is assigned within a territory, the sharing rules based on territory membership grant the assigned resource access to the appointment. This is the standard Field Service sharing model for giving technicians visibility into their dispatched work .

Incorrect Option:

A. Service Territory:
This is incorrect because the Service Territory object defines the geographic area and operating hours, but it does not directly share Service Appointments with individual resources. Sharing flows through the membership relationship, not the territory itself .

B. Work Order:
This is incorrect because Work Orders represent the job to be done, not the sharing mechanism for Service Appointments. While Service Appointments relate to Work Orders, sharing is controlled at the appointment and territory membership level.

D. User Territory:
This is incorrect because User Territory is a separate feature used for restricting data visibility for mobile users in specific scenarios. It is not the standard object used to share Service Appointments with Service Resources for dispatch purposes .

Reference:
Salesforce Help: Service Appointment Sharing — "To let service resources view and modify service appointments assigned within a service territory, set up sharing rules with read/write or read/edit access for the Service Appointment object. Assign the sharing rules to users based on service territory membership."

Explanation:
The correct license assignment is based on the specific capabilities each contractor group requires. The 75 contractors need standard field service functionality (Work Orders, Assets, Mobile App, Chatter), which is covered by the Contractor license. The remaining 25 contractors need scheduling and optimization capabilities, which are only available with the Contractor Plus license. This maps directly to option A.

Correct Option:

A. 75 Contractor, 25 Contractor Plus:
This is correct because the Contractor license provides secure mobile app access, work order management, and asset tracking for the 75 contractors performing field work . The Contractor Plus license is required for the 25 contractors who need scheduling and optimization capabilities, as this feature is exclusively available in the Contractor Plus edition .

Incorrect Option:

B. 25 Contractor, 75 Contractor Plus:
This is incorrect because it reverses the quantities. The majority of contractors (75) only need standard field service access, not the advanced scheduling features of Contractor Plus. Assigning 75 Contractor Plus licenses would be unnecessary and cost-prohibitive.

C. 25 Contractor, 100 Contractor Plus:
This is incorrect because the total quantity (125) exceeds the number of contractors (100). Additionally, the 75 contractors who only need basic mobile access should not receive the more expensive Contractor Plus license.

D. 100 Contractor, 100 Contractor Plus:
This is incorrect because it doubles the license quantity (200 total for 100 contractors) and assigns the wrong license type to the majority. Only 25 contractors require the Contractor Plus license for scheduling capabilities.

Reference:
Salesforce Field Service Pricing: Contractor licenses provide "secure mobile app access," "view and manage assigned work orders," and "submit job updates and service reports" . Contractor Plus licenses add "scheduling and optimization" capabilities, which are listed as "Contractor Plus only" in the feature comparison .

Explanation:
The requirement is to associate different skills and parts to each of the three distinct installation steps (surface prep, panel installation, electronics). The best approach is to create a Work Type to represent the overall solar panel installation job and use Work Order Line Items to represent each individual step. Each line item can have its own Work Type, allowing you to define specific skill requirements and required products for that particular step, while the parent Work Order ties everything together.

Correct Option:

B. Create a different work type and work order line item for each step.
This is correct because Work Order Line Items are designed to represent "smaller tasks needed to complete the original request" . Each line item can have its own Work Type, and Work Types carry skill requirements and required products that copy over to the line item . By creating a distinct Work Type for each installation step, you ensure the appropriate skills and parts are associated with that specific task.

Incorrect Option:

A. Create a different work order and work type for each installation step.
This is incorrect because creating separate Work Orders fragments the job into three unrelated records. Work Order Line Items exist precisely to handle subtasks within a single parent Work Order, allowing consolidated tracking of the overall installation job.

C. Create a work type associated to the work order and create line items for each step.
This is incorrect because if you only create one Work Type for the entire job, all three steps would inherit the same skill and product requirements. You would not be able to differentiate the skills and parts needed for each distinct installation step.

D. Create a work order hierarchy with the same work type associated to each child work order.
This is incorrect because using the same Work Type on each child Work Order means every step would have identical skill and product requirements. This does not allow you to assign different technical skills and parts to each specific installation step.

Reference:
Salesforce Help: "Work order line items are smaller tasks needed to complete the original request... Each can have their own work type, and required skills and products." Work Types standardize job attributes by carrying required skills and required products that copy over to records created from them .

Explanation:
When a Work Order has multiple Work Order Line Items that can be completed independently by different resources based on their skills, each line item should have its own Service Appointment. This allows the scheduling engine to assign each task separately to the best-matched resource. Bulk Scheduling is the appropriate tool because it enables dispatchers to schedule multiple Service Appointments simultaneously, applying the scheduling policy efficiently across all the line item appointments.

Correct Option:

D. Create a service appointment for each line item and use bulk scheduling to schedule the appointments.
This is correct because each Work Order Line Item represents a distinct task (installation vs. network setup) that may require a different resource with specific skills. Creating a separate Service Appointment for each line item allows independent scheduling and assignment . Bulk Scheduling then lets the dispatcher schedule all related appointments in one action, respecting availability, skills, and scheduling policies .

Incorrect Option:

A. Relate both line items to a service appointment and use the candidate quick action to schedule.
This is incorrect because a single Service Appointment cannot be split between two resources. If both line items share one appointment, only one resource would be assigned, preventing different technicians from completing separate tasks.

B. Create a service appointment for the work order to ensure one resource handles the job and use autoschedule.
This is incorrect because a single Service Appointment for the entire Work Order forces one resource to handle both line items, contradicting the requirement that different resources may complete each task based on skills.

C. Create two service appointments with a dependency to ensure the same start of both.
This is incorrect because a dependency enforces a specific order or timing relationship between appointments (e.g., finish-to-start), not that both start at the same time. Dependencies are used for sequential work, not parallel tasks that can be done independently.

Reference:
Salesforce Help: Work Order Line Items can be scheduled individually with their own Service Appointments. Bulk Scheduling allows dispatchers to schedule multiple appointments at once using the scheduling policy.