Examtopics

コメント(17)

• Option C is the correct answer since enabling the Multi-AZ option on the Aurora cluster provides a highly available environment that can automatically failover in the event of an availability zone failure, making it a good choice to maintain high availability during maintenance windows. Additionally, the application can continue to use the same endpoint for both read and write operations, simplifying the configuration process.

  👍 3

  jqso2342023/04/14

• Option C is the correct solution to meet the company's requirements with the least possible interruption. By turning on the Multi-AZ option on the Aurora cluster, a standby replica of the primary instance is created in a different availability zone (AZ). During the maintenance window, the update is first applied to the standby replica. After the update is applied and the replica is promoted to become the new primary instance, the old primary instance is updated. This ensures that the Aurora cluster remains available throughout the maintenance window, with minimal interruption.

  Adding a reader instance to the Aurora cluster (Options A and B) is not necessary and will not provide any additional benefits in terms of availability during the maintenance window.

  Creating a custom ANY endpoint for the Aurora cluster (Options B and D) is also not necessary and does not provide any additional benefits in terms of availability during the maintenance window

  👍 3

  alce20202023/04/14
• 正解だと思う選択肢: C

  The answer is C.

  Enabling Multi-AZ would provide high availability by automatically replicating data to a standby instance in a different availability zone. During the maintenance window, Amazon RDS would automatically failover to the standby instance with minimal downtime. Updating the application to use the Aurora cluster endpoint for write operations and the Aurora cluster's reader endpoint for reads would ensure that the application continues to function properly during the maintenance window.

  👍 2

  5aga2023/04/23