Explanation:

This question tests your understanding of where to define planned inventory requirements (the bill of materials) for jobs in Field Service Lightning. The goal is to track and manage what parts are needed so they can be provided to technicians.

Analysis of Correct Answers:
A. Products Required for Work Orders: The "Products Required" related list on the Work Order object is the primary, high-level place to define the parts needed for the entire job. This list aggregates all parts required across the various tasks. It is used for inventory planning, creating Product Requests to move parts to the technician's van, and generating picklists. This ensures the overall job's material needs are tracked.

C. Products Required for Work Order Line Items: For more granular tracking, especially when a Work Order has multiple line items representing different tasks or assets, you can define "Products Required" on individual Work Order Line Items. This allows you to specify which specific parts are needed for each discrete task or for each specific asset being serviced. This provides precise tracking and is essential if different line items have different part requirements.
Both methods are valid and often used together for comprehensive inventory management. The Work Order-level list gives a summary, while the Work Order Line Item list provides detailed attribution.

Why the other options are incorrect:
B. Products Required for Service Appointments: There is no standard "Products Required" related list on the Service Appointment object. Service Appointments are for scheduling time slots, not for defining the scope of work or material requirements. Inventory planning is tied to the work definition (Work Order/WOLI), not the schedule slot.

D. Products Required for Service Resources: This is not a standard feature. Service Resources represent technicians, not inventory stock. While you can track what inventory is physically located with a resource (via Product Items at a mobile Location), you do not define what parts a job requires on the Resource record itself. Requirements are defined on the work to be performed, not on the technician.

Reference:
Salesforce Help: "Add Products to Work Orders and Work Order Line Items" – This article explains both methods: "You can add products to work orders or work order line items to indicate which products are needed to complete the work... Adding products to work order line items is useful if different line items require different products."
The core principle is that inventory requirements are defined as part of the work definition (Work Order and its child Work Order Line Items), enabling the system to generate Product Requests and manage Product Transfers to get the right parts to the right place.

Explanation:

Why A is correct
For multi-staged work where stage 2 can only start after stage 1 is completed, Salesforce Field Service supports scheduling dependencies (also referred to as Complex Work) between two Service Appointments. You model this by linking the appointments (related appointment) and defining a time dependency such as Start After Finish so the second appointment can’t be scheduled/started until the first is complete.
Under the hood, this is implemented via the Time Dependency relationship between two service appointments.

Why the other options are wrong
B. One Service Appointment with total duration and assign two Resources ❌
This doesn’t enforce “stage 2 only after stage 1 is complete.” It also implies simultaneous staffing rather than sequential dependency.
C. Two Service Appointments and schedule them to the same Resource ❌
Scheduling both to the same person might happen sequentially, but it doesn’t enforce the dependency rule (and fails if different resources are needed).
D. One Service Appointment and schedule it to two different Resources ❌
Same issue: it models concurrent work, not a gated second stage that can’t begin until the first finishes.

Exam memory hook:
Sequential stages = two Service Appointments + Time Dependency (Complex Work).

Explanation:

Each Asset record in Salesforce has a standard field called Installation Date, which captures when an asset (product) was installed. Reporting can be done by creating a report filtered on the Installation Date field—making it straightforward to analyze volumes over specific periods.

“Assets include an Installation Date field for tracking installation metrics.” (Salesforce Assets Data Model)

Why the Others are Incorrect:
A: Work order related list doesn’t capture installation date; it links service events.
B: Custom field on products consumed isn’t standard, requires custom development, and doesn’t link directly to reporting on installed products.
C: Field history tracking on asset tracks changes, not installation volume.

Explanation:

Technician certifications in Field Service are best represented as Skills assigned to a Service Resource (via Resource Skills). A key feature of Resource Skills is that you can control when a skill is valid by using dates. By setting an End Date on the Resource Skill, you can model the expiration/renewal cycle of a certification. Once the End Date is reached, the certification is effectively no longer valid for matching and scheduling (depending on how your org uses skill matching in policies/work rules), which helps ensure only currently certified technicians are considered for work requiring that certification.

Why the other options aren’t correct:

A. Track certification using reminders: Reminders aren’t a standard Field Service mechanism for enforcing certification validity during scheduling. It also doesn’t naturally prevent an expired-certified tech from being scheduled.

B. Create an Absence once expired: Absences are meant to represent time off / unavailability (vacation, sick time, etc.), not an expired credential. Expired certification doesn’t mean the technician is unavailable—just not qualified for certain work.

C. Remove from the Service Territory once expired: Territories represent where a technician can work geographically/organizationally. Certification expiry should not remove the tech from the territory; it should only affect eligibility for work that requires that certification.

Exam takeaway:
Use Resource Skills with Start/End dates to manage time-bound certifications; then use skill matching in scheduling to ensure only valid certifications qualify a technician for certain jobs.

Explanation:

In Salesforce Field Service, a Maintenance Plan is the specific tool designed to manage recurring service schedules. When a product requires regular maintenance (like a quarterly check-up), a Maintenance Plan allows you to define the frequency (every 3 months), the start date, and the generation window (how far in advance to create the work orders). It automatically generates the Work Orders and Service Appointments needed to fulfill the service contract.

Why the others are incorrect:
A. Define a repeating Work Type: Work Types act as templates for Work Orders (defining duration and required skills), but they do not have a native mechanism to "repeat" or auto-generate schedules on their own.

B. Implement Path for Work Orders: Path is a visualization tool used to track the stages of a Work Order (e.g., New -> In Progress -> Completed). It has nothing to do with recurring scheduling.

C. Build a Process for Service Appointments: While you could technically build a custom automation using Flow to create future appointments, it is not the recommended "Best Practice." Using the native Maintenance Plan feature is the standard, scalable way to handle this requirement.

References:
Salesforce Help: Create Maintenance Plans