ViPR Strong Consistency ensures data returned is the latest version. Now how that works?  Basically there are two layers to the architecture.  1. Geo-protection this ensures just data protection 2. Multi-access and this ensures multi-access with strong consistency.  The multi-site access layer works in a way it senses where you are coming from. So let's say you write data to Site-A, and then immediately go do a read access from Site-B.  Under the hood ViPR would sense that and it would fetch the data from site-A to site-B.  In case the data is replicated to site-B the data is then read locally from site-B.  To ensure strong consistency whenever data is written to a site, it becomes owned by that site. That site is just responsible to update the index, but the data can be stored in any location. so we always have to get back to the owner to ensure strong consistency.  hope this answered your question.
I'm curious to understand how ViPR 2.0 Strong Consistency works in the context of the CAP Theorem, especially because ViPR object replication is asynchronous?
ViPR Strong Consistency/Asynchronous Replication