A company is deploying a critical application by using Amazon RDS for MySQL. The application must be highly available and must recover automatically. The company needs to support interactive users…

Question

Options

• AConfigure Amazon RDS for MySQL in a Multi-AZ DB instance deployment with one standby
• BConfigure Amazon RDS for MySQL in a Multi-AZ DB cluster deployment with two standby
• CConfigure Amazon RDS for MySQL to use multiple read replicas across multiple Availability
• DConfigure Amazon RDS for MySQL as the primary database for the transactional queries with

• A
  9% (3)
• B
  6% (2)
• C
  82% (28)
• D
  3% (1)

Explanation

Key Requirements: High availability and automatic recovery. Separate transactional and analytical queries with minimal performance impact. Allow up to a 4-hour lag for analytical queries. Analysis of Options: Multi-AZ deployments provide high availability but do not include read replicas for separating transactional and analytical queries. Analytical queries on the secondary DB instance would impact the transactional workload. Incorrect Approach: Does not meet the requirement of query separation. Multi-AZ DB clusters provide high availability and include a reader endpoint. However, these are better suited for Aurora and not RDS for MySQL. Incorrect Approach:Not applicable to standard RDS for MySQL. Multiple read replicas allow separation of transactional and analytical workloads. Queries can be pointed to a replica in a different AZ, ensuring no impact on transactional queries. Correct Approach: Meets all requirements with high availability and query separation. Creating nightly snapshots and read-only databases adds significant operational overhead and does not support the 4-hour lag requirement. Incorrect Approach: Not practical for dynamic query separation.

No community discussion yet for this question.