Explanation
Work Orders are records that track customer requests for service such as repairs or maintenance[47]. Work Order Line Items are records that track specific tasks or products related to a work order[48]. Service Appointments are records that track the date, time, duration, and assigned resource for a work order or work order line item[49]. Adding each Asset to a separate Work Order Line Item or a separate Work Order would allow handling the service associated with each container independently by creating different records for different containers. Creating a Service Appointment for each Line Item or each Work Order would allow scheduling and dispatching the service associated with each container independently by assigning different resources and time slots for different containers. Adding each Asset to a separate child Work Order would create an unnecessary hierarchy of Work Orders that could complicate reporting and scheduling. Creating a Service Appointment for the parent Work Order would not allow handling the service associated with each container independently by assigning one resource and time slot for all containers. References:
https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5

Explanation
Enabling the sharing features in the Field Service settings in the Setup menu allows sharing dispatched service appointments with assigned resources regardless of the private record access model in sales, support, and field service organizations[50]. Creating a user territory for the technicians' primary and secondary territories would not ensure that they have access to the service appointments dispatched to them. Creating a process to change the owner of the service appointment to the assigned technician would not work if multiple resources are assigned to the same service appointment. Configuring a sharing rule to share dispatched service appointments with the assigned resource would not work if multiple resources are assigned to different crews or teams. References: https://help.salesforce.com/s/articleView?id=sf.fs_sharing_overview.htm&type=5

Explanation
The book appointment action is used to schedule a service appointment based on service objectives and resource availability. The action displays a list of potential time slots with service objective scores for each slot. The higher the score, the better the slot meets the service objectives.
References: https://help.salesforce.com/s/articleView?id=sf.fsl_book_appointment.htm&type=5

Explanation
Service Reports are documents that summarize the details and outcomes of a service appointment such as work performed, products consumed, customer feedback, etc.[72]. Using the standard Service Report would allow Field Service Technicians to capture details and customer approval on completed work and send them to the customer electronically by generating and emailing service reports from the Field Service Mobile App or the web browser[73]. Creating a Process Builder to generate a report would not allow Field Service Technicians to capture details and customer approval on completed work. Process Builder is a tool that allows users to automate workflows based on specified criteria and actions[74]. Creating a custom report would not allow Field Service Technicians to capture details and customer approval on completed work. Custom reports are reports that allow users to view data based on specific criteria such as objects, fields, filters, or charts[75].
Using the standard Work Order email template would not allow Field Service Technicians to capture details and customer approval on completed work. Email templates are templates that allow users to send predefined emails with merge fields[76]. References:
https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_generate.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.process_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.email_templates_overview.htm&type=5

Explanation
This option allows reporting on assets and their attributes, including hierarchical relationships, by using the standard asset reports and fields. References:
https://help.salesforce.com/s/articleView?id=sf.fs_asset_hierarchy.htm&type=5