Explanation:
Adding Neptune read replicas and using the reader endpoint load-balances read traffic across replicas while the writer handles moderate writes. This supports read-heavy spiky workloads with low-latency traversals. Scaling up writer does not provide horizontal scaling. Global Database is for cross-Region. Partitioning breaks traversals and is unsupported for cross-cluster queries.
Ultimate access to all questions.
How should a Neptune cluster be scaled to support low-latency, read-heavy graph queries spiking to about 25,000 requests per second while writes remain moderate?
A
Scale up the writer instance size
B
Configure Amazon Neptune Global Database
C
Add Neptune read replicas and use the reader endpoint
D
Partition the graph across multiple Neptune clusters by key
No comments yet.