Agentforce Field Service and Operations Consultant Practice Exam

Correct: C — a service crew with crew members, represented by a Crew-type service resource. Crews let the scheduler treat a team as a single schedulable resource; members are tracked as service crew members and the crew itself is assigned to the appointment.

Why not the others: required resource preferences (A) still schedule individuals and cannot guarantee both are booked together; skill requirements (B) describe competencies, not head count; a public group (D) is a sharing construct the scheduler ignores.

Correct: B — an end date on the service resource skill. Service resource skills carry start and end dates, so a skill can lapse automatically; once it expires, the resource no longer matches work that requires it.

Why not the others: removing territory membership (A) blocks all work, not just gas jobs; manually lowering the level (C) is the cleanup the scenario wants to avoid and depends on someone remembering; an open-ended absence (D) makes the technician unavailable for everything.

Correct: A — a work type. Work types are templates for recurring jobs: they hold estimated duration, skill requirements, products required, and the option to auto-create a service appointment, and work orders inherit them.

Why not the others: a service territory (B) defines where work happens and who can do it, not job templates; service resources (C) describe people and assets, not jobs; operating hours (D) set availability windows, not duration or skills.

Correct: D — one work order with three line items. Work order line items break a job into subtasks that each carry their own status, work type, and products, and can even have their own service appointments, while rolling up to the parent work order.

Why not the others: unrelated work orders (A) lose the single-job grouping; a description field (B) cannot track per-task status; cases (C) are the support record that may originate the work, not the field-execution structure.

Correct: B — a work rule for skills, a service objective for travel. Work rules are hard filters that remove ineligible candidates; service objectives are weighted preferences that rank the candidates that remain, such as minimizing travel.

Why not the others: objectives alone (A) only rank candidates, so an unqualified technician could still win; reversing the two (C) turns the must-have into a preference and the preference into a filter; validation rules (D) block saves but do not guide candidate selection.

Correct: C — complex work with an appointment dependency. Complex work links related appointments with dependencies, such as one starting only after another finishes, and the scheduler honors that sequence.

Why not the others: a multiday appointment (A) spreads one long job over several days rather than ordering two distinct jobs; a shared territory (B) says nothing about sequence; identical arrival windows (D) could let the install be booked first.

Correct: A — street-level routing. Aerial routing estimates travel as a straight line; street-level routing uses the road network, so river crossings and bridge detours are reflected in travel time.

Why not the others: weighting travel more heavily (B) still optimizes against the same wrong straight-line estimate; smaller territories (C) and extra resources (D) change capacity, not the accuracy of travel calculations.

Correct: D — a service report with a signature block in the Field Service mobile app. Customer sign-off is handled by generating a service report on the device and capturing signatures on it, producing a record of the work the customer approved.

Why not the others: an email reply (A) happens after the visit and is not an on-site sign-off; a list view (B) displays records but captures nothing; a checkbox (C) records no actual signature or summary of work.

Correct: C — product consumed, linked to the van’s product item. Product items hold stock at a location such as a van; recording product consumed against that product item decrements its quantity and ties usage to the work order.

Why not the others: a product request (A) asks for more stock; a product transfer (B) moves stock between locations rather than consuming it; a return order (D) sends parts back.

Correct: B — a user territory. User territories associate a dispatcher’s user with the service territories they manage, which drives what they can access and filter in the Dispatcher Console; service territories define where resources do the work.

Why not the others: territory membership (A) is for service resources who perform work there, not dispatchers; Modify All Data (C) grants access to everything, the opposite of the goal; operating hours (D) set availability, not access.