Explanation:

Why the Answer is Right:
Tracking service work on a customer’s installed products is best achieved by relating Work Orders to Assets. Each Work Order references one or more assets that represent the customer’s install base, ensuring maintenance history and operational visibility.

Why the Others are Incorrect:
A: This is the question itself, not an answer.
C: Work Orders to Products tracks generic product-related work, not installed, customer-specific assets.
D: Products to Accounts doesn’t show service events.
E: Assets to Products relates asset records to the base product type, not service work tracking.

References:
Work Orders and Assets
Data Model Reference

Explanation:

In 2026, Salesforce Field Service uses the Return Order object specifically for Reverse Logistics. If a customer wants to return a product instead of getting a repair, the standard process is to create a Return Order. This object tracks the "Return from" and "Return to" locations, the reason for the return, and the expected shipment details. Return Order Line Items are then used to specify the exact product(s) and quantities being sent back. This ensures that inventory levels are updated correctly once the item is received at the warehouse.

Why Others are Incorrect
A (Work Order): A Work Order implies "Work" (labor). If no technician is visiting, a Work Order is data clutter.
C (Product Request): This is for requesting parts to be delivered to a technician/site, not for a customer returning an item.
D (Return Order without Line Items): While technically a Return Order, the Salesforce data model requires Return Order Line Items to track the specific product records. B is the more complete "Field Service" answer.

Reference:
Salesforce Help: Manage Return Orders

Explanation:

Why the answers are right
To handle assets "independently," each asset needs its own Service Appointment so it can be scheduled, tracked, and closed separately.

Option A: This uses Work Order Line Items (WOLIs). One Work Order (the visit) contains three WOLIs (one for each container). By creating a Service Appointment for each WOLI, the technician can "Pass" one container and "Fail" another independently.

Option D: This is a more segregated approach where each container gets its own Work Order. Each Work Order has its own Service Appointment. This is useful if the containers might be serviced on different days or by different specialists.

Why the others are incorrect
B: If you create the appointment at the parent level, all three containers are lumped into one visit, making it impossible to manage their statuses independently on the Gantt.
C: Similar to B, creating only one appointment for the whole Work Order prevents independent scheduling/tracking of the individual containers.

Reference:
Salesforce Help: Work Order Line Items

Explanation:

In Salesforce Field Service, scheduling is based on Service Territories (the geographic or logical areas where service is delivered) and Service Territory Members (the technicians assigned to those territories).

Service Territory time zone: Defines the local time zone for scheduling work in that area.
Service Territory Member: Represents a technician who works in that territory, with their own Operating Hours (availability schedule).

In this scenario, the technician’s personal time zone is one hour behind the Service Territory’s time zone. This creates a scheduling problem: the system may think the technician is available when they’re not, or vice versa.

To fix this, you adjust the Operating Hours for that Service Territory Member by adding one hour to their start and end times. This ensures the technician’s availability matches the territory’s scheduling logic.

Why not the others?

A (Add one hour to Service Territory times): This would shift all technicians in the territory, not just the one member. Incorrect.

B (Change the time zone on the user record): The user’s time zone is for UI display, not scheduling optimization.

D (Subtract one hour from Service Territory times): Again, this affects the entire territory, not just one technician.

Real-world Example:
Service Territory is in New York (EST).
Technician lives in Chicago (CST), which is one hour behind.
If the territory’s operating hours are 9am–5pm EST, the technician’s availability must be set as 8am–4pm CST to align correctly. By adjusting the member’s operating hours in Salesforce, the scheduler sees accurate availability.

Reference:
Salesforce Help: Service Territory Members and Operating Hours

Explanation:

When two technicians are required for a job but can arrive at different times, the best practice is to create two separate Service Appointments. Each appointment can be scheduled independently, allowing flexibility in technician arrival times while still linking both appointments to the same Work Order. This ensures accurate tracking of technician time, resource allocation, and completion status.

This approach also supports reporting and optimization. Each technician’s appointment is visible in the Dispatcher Console, making it easier to manage workloads.

Why the Other Options Are Incorrect
B. One appointment with two required resources: This forces both technicians to be scheduled at the same time, which contradicts the requirement.

C. One appointment with two resources: Same issue — both resources must be onsite simultaneously.

D. Two appointments with Early Start: Overcomplicates scheduling; Early Start is not needed if separate appointments are created.

References
Salesforce Help: Service Appointments
Trailhead: Field Service Work Orders and Appointments