A Database Specialist modified an existing parameter group currently associated with a production Amazon RDS for SQL Server Multi-AZ DB instance. The change is associated with a static parameter…

Question

Options

• ASelect the option to apply the change immediately
• BAllow the preconfigured RDS maintenance window for the given DB instance to control when the
• CApply the change manually by rebooting the DB instance during the approved maintenance
• DReboot the secondary Multi-AZ DB instance

• A
  9% (2)
• B
  4% (1)
• C
  83% (19)
• D
  4% (1)

Explanation

Explanation

Option C is correct because static parameters in RDS require a manual reboot to take effect - unlike dynamic parameters, which apply immediately. Since the change has been approved for a specific maintenance window to minimize user impact, the Database Specialist must manually reboot the DB instance during that approved window to control exactly when the disruption occurs.

Why the distractors are wrong:

• Option A is incorrect because applying immediately would cause an unplanned reboot outside the approved window, impacting users without proper scheduling.
• Option B is incorrect because the preconfigured RDS maintenance window cannot automatically apply static parameter changes - only a manual reboot triggers them, regardless of the maintenance window setting.
• Option D is incorrect because rebooting only the secondary Multi-AZ instance will not apply the static parameter change to the primary instance where user connections are managed; additionally, after a failover the parameter would still be inconsistent.

Memory Tip

Think: "Static = Stuck until you reboot manually." Dynamic parameters flow in automatically, but static parameters are stuck and require a deliberate manual reboot - and you always want that reboot to happen on your schedule (the approved maintenance window), not RDS's schedule.

No community discussion yet for this question.