Which solution will meet these requirements?
Use tags to identify development instances and production instances. In Patch Manager, create two patch groups and one patch baseline. Add an auto-approval delay to each patch group. Create a single maintenance window.
Use tags to identify development instances and production instances. In Patch Manager, create two patch groups and two patch baselines. Specify an auto-approval delay in each of the patch baselines. Create a single maintenance window.
Use tags to identity development instances and production instances. In Patch Manager, create two patch groups and one patch baseline, Create two separate maintenance windows, each with an auto-approval delay.
Use tags to identify development instances. In Patch Manager, create one patch group and one patch baseline. Specify auto-approval delays in the patch baseline, Add development instances to the new patch group. Use predefined Patch Manager patch baselines for all remaining instances. Create a single maintenance window.
Explanations:
This option suggests using a single patch baseline for both development and production instances, which does not meet the requirement of different auto-approval delays (2 days for development, 5 days for production).
This option meets all the requirements: it uses two separate patch baselines (one for development and one for production), with different auto-approval delays, and a single maintenance window for both instance types.
This option proposes two maintenance windows, which is unnecessary since a single maintenance window can be used for both development and production instances, provided that the patch baselines are defined separately.
This option suggests using predefined patch baselines for production instances, but it does not meet the specific auto-approval delay requirement for production instances (5 days) and would require additional configuration for development instances.