A company runs its production workload on an Amazon Aurora MySQL DB cluster that includes six Aurora Replicas. The company wants near-real-time reporting queries from one of its departments to be…

Question

Options

• ACreate and use a custom endpoint for the workload.
• BCreate a three-node cluster clone and use the reader endpoint.
• CUse any of the instance endpoints for the selected three nodes.
• DUse the reader endpoint to automatically distribute the read-only workload.

• A
  73% (30)
• B
  7% (3)
• C
  5% (2)
• D
  15% (6)

Explanation

In Amazon Aurora, a custom endpoint is a feature that allows you to create a load-balanced endpoint that directs traffic to a specific set of instances in your Aurora DB cluster. This is particularly useful when you want to route traffic to a subset of instances that have different configurations or when you want to isolate specific workloads (e.g., reporting queries) to certain Custom Endpoint: The correct solution is to create a custom endpoint that includes the three Aurora Replicas that the department wants to use for near-real-time reporting. This custom endpoint will distribute the reporting queries only across the three selected replicas with the specified compute and memory configurations, ensuring that these queries do not affect the rest of the DB cluster. Option B (Create a three-node cluster clone): This would create a separate cluster with its own resources, but it is not necessary and could incur additional costs. Also, it doesn't leverage the existing replicas. Option C (Use any of the instance endpoints): This would involve manually managing connections to individual instances, which is not scalable or automatic. Option D (Use the reader endpoint): The reader endpoint would distribute the read queries across all replicas in the cluster, not just the selected three. This would not meet the requirement to limit the reporting queries to only three specific replicas.

No community discussion yet for this question.