Replicas can support availability or serve suitable reads, while a primary or coordination mechanism manages writes. The architecture determines which node can answer a query with the required freshness.
Replication introduces tradeoffs involving lag, consistency and failure handling. A successful read from a replica does not always mean it includes the most recent accepted write.
ELI5
Think of several offices keeping copies of a shared register. They need a clear process for sending updates and knowing which copy is current enough.
For example, a catalogue may serve ordinary browsing reads from replicas while sending a read that must see a just-saved change to the primary.
Does replication mean every copy is always identical?
No. Some systems allow a delay before updates reach other nodes, depending on their consistency design.
Is replication the same as a backup?
No. Replication can copy unwanted changes as well, while backups preserve recoverable states under a separate retention process.

