What should the database specialist do to address this concern with the LEAST operational effort?
Add a new Aurora Replica so that the maintenance action occurs on the Aurora Replica first.
Defer the maintenance action in the AWS Management Console or by using the AWS CLI.
Delete the maintenance action in the AWS Management Console or by using the AWS CLI.
Add a new Aurora standby DB instance so that the maintenance action occurs on the standby DB instance first.
Explanations:
Adding an Aurora Replica would not prevent maintenance actions from affecting the primary instance during the sales event. The maintenance would still impact the performance of the primary DB cluster, as replicas do not shield the primary from maintenance activities.
Deferring the maintenance action is a straightforward solution that directly addresses the concern without requiring additional resources or changes to the database configuration. This ensures that maintenance does not interfere with the sales event.
Deleting the maintenance action is not a feasible option as it may not be possible to completely eliminate maintenance activities. Moreover, this approach could lead to potential issues if maintenance is necessary for database performance and security.
Adding an Aurora standby instance would not prevent maintenance actions on the primary instance. Standby instances are typically used for failover and do not act as a shield against maintenance operations, thus still risking impact on the sales event.
I believe the answer is:
Defer the maintenance action in the AWS Management Console or by using the AWS CLI.