D-ECS-DS-23 · Question #38
Load balancer routes read request to one of the sites available.
The question appears to be incomplete - the correct answer field is blank and only one choice (C) is shown. However, based on the context provided, here's an explanation of the concept: What's happening in this scenario: When a load balancer routes a read request to an…
Question
Load balancer routes read request to one of the sites available.
Options
- C
- Application retrieves secondary copy.
Explanation
The question appears to be incomplete - the correct answer field is blank and only one choice (C) is shown. However, based on the context provided, here's an explanation of the concept:
What's happening in this scenario: When a load balancer routes a read request to an available site in a distributed or replicated system, the application typically retrieves data from a secondary (replica) copy rather than the primary. This is the core principle of read replica architecture - writes go to the primary, while reads are distributed across secondary nodes to reduce load and improve performance.
Why Choice C ("Application retrieves secondary copy") fits: In a replication topology, sites other than the primary hold replica (secondary) data. Routing reads to these nodes means the application is, by definition, reading from a secondary copy - not the authoritative source.
Memory Tip: Think "Primary writes, Secondaries read" - load balancers direct read traffic to replica nodes (secondaries) to scale out read throughput, so any read routed away from the primary is a secondary copy retrieval.
Note: This question appears to be missing its full answer choices and the marked correct answer. If you can share the complete question with all options and the correct answer indicated, I can give you a more precise and accurate explanation.
Topics
Community Discussion
No community discussion yet for this question.