Explanation
Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans[126]. Defining a generation horizon of 14 days would allow Universal Containers to automatically generate Work Orders 14 days before the next suggested maintenance date by creating work orders from maintenance plans within 14 days of their scheduled date[127]. Defining a generation timeframe of 14 days would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Timeframe is a setting that defines how often work orders should be generated from maintenance plans[128]. Configuring Auto-generate Work Orders to True would not automatically generate Work Orders 14 days before the next suggested maintenance date. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[129]. Defining a generation horizon of 20,160 minutes would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Horizon is measured in days, not minutes[130]. References:
https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_horizon.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_auto_generate_work_orders.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm&type=5

Explanation
Street Level Routing is a feature that calculates travel time between service appointments based on actual road distance and traffic conditions[131]. Default Travel Speed is a setting that defines the average speed of resources when traveling between service appointments[132]. Using Street Level Routing and Default Travel Speed would allow improving travel time accuracy by taking into account real-time road conditions and resource speed. Minimum Grade, Default Operating Hour would not affect travel time accuracy. Minimum Grade is a setting that defines the minimum skill level required for resources to be matched with service appointments[133]. Default Operating Hour is a record that defines the default working hours for resources[134]. Estimated Travel Time, Minimize Travel would not affect travel time accuracy. Estimated Travel Time is a field on the service appointment object that shows the expected travel time for the assigned resource[135]. Minimize Travel is an optimization criterion that prioritizes reducing travel time when scheduling service appointments[136]. Travel Speed Unit, Actual Travel Time would not affect travel time accuracy. Travel Speed Unit is a setting that defines the unit of measurement for travel speed such as miles per hour or kilometers per hour[137]. Actual Travel Time is a field on the service appointment object that shows the actual travel time recorded by the resource[138]. References:
https://help.salesforce.com/s/articleView?id=sf.fs_street_level_routing_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_default_travel_speed.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_minimum_grade.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_default_operating_hours_overview.htm&type=5
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_estimated
https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_travel_speed_unit.htm&type=5
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_actualtrav

Explanation
Products consumed are records that track the products used during a service appointment[32]. A custom installation date field on products consumed would allow reporting on the volume of products installed within a specific timeframe by filtering on the installation date field values[33]. A work order related list on asset would show the work orders associated with an asset, but not the products installed. Field history tracking on asset would track field changes on an asset, but not the products installed. The standard installation date field on asset would show when an asset was installed, but not the products installed. References:
https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.reports_filter_date_fields.htm&type=5

Explanation
To make custom actions visible in the Field Service mobile app, they need to be added to both the Classic Publisher Quick Actions section and the Mobile and Lightning Actions section on the page layout.
References: https://help.salesforce.com/s/articleView?id=sf.fsl_mobile_actions.htm&type=5

Creating a new Service Appointment on the original Work Order is the best option because it will allow Universal Containers to track the work that was done on the initial visit and the work that needs to be done on the return visit. Rescheduling the Service Appointment for the new date is also a good option because it will allow Universal Containers to track the date and time of the return visit.
The other two options are not as good because they will not allow Universal Containers to track the work that was done on the initial visit. Creating a new Work Order and Service Appointment would create a new record for the return visit, which would not be linked to the original Work Order. Rescheduling the Work Order for the new date would reschedule the entire Work Order, including the initial visit, which would not be accurate.