A Database Specialist needs to speed up any failover that might occur on an Amazon Aurora PostgreSQL DB cluster. The Aurora DB cluster currently includes the primary instance and three Aurora…

Question

Options

• ASet the TCP keepalive parameters low
• BCall the AWS CLI failover-db-cluster command
• CEnable Enhanced Monitoring on the DB cluster
• DStart a database activity stream on the DB cluster

• A
  81% (26)
• B
  3% (1)
• C
  3% (1)
• D
  13% (4)

Explanation

Explanation

Setting TCP keepalive parameters low (Option A) ensures that the application's connection layer can detect a failed connection more quickly and reconnect to the new primary instance after a failover. By reducing the TCP keepalive idle time, interval, and retry count, the application avoids waiting for long connection timeout periods, minimizing perceived downtime during an Aurora failover event.

Why the distractors are wrong:

• Option B (failover-db-cluster): This triggers a manual failover rather than optimizing how quickly the application recovers from one - it doesn't reduce downtime for unexpected failures.
• Option C (Enhanced Monitoring): This provides OS-level metrics for performance visibility, but has no impact on failover speed or connection recovery.
• Option D (Database Activity Streams): This is an auditing/security feature that captures database activity for compliance purposes and does nothing to improve failover performance.

Memory Tip: Think of TCP keepalive like a "heartbeat check" - the more frequently your application checks whether the connection is still alive, the faster it notices when the connection drops and can reconnect to the new primary. Lower values = faster detection = less downtime. Remember: tune the client, not the cluster, when optimizing failover recovery time.

No community discussion yet for this question.