フリー問題

問題文

A page writes a value and then reads it back and sees the old one, but a second refresh shows the new value. Which mechanism explains that?

選択肢

1. The write went to the primary and the read went to a gateway that is a little behind, so the application has to read its own writes from the budget for a short period or wait for an acknowledgment that includes the position of the copy it will read from next in the sequence of the deployment.
2. The write went to the primary and the read went to a gateway that is a little behind, so the application has to read its own writes from the budget for a short period or wait for an acknowledgment that includes the changelog of the copy it will read from next in the container of the deployment.
3. The write went to the primary and the read went to a replica that is a little behind, so the application has to read its own writes from the primary for a short period or wait for an acknowledgment that includes the position of the copy it will read from next in the sequence of the deployment.
4. The write went to the primary and the read went to a replica that is a little behind, so the application has to read its own writes from the primary for a short period or wait for an acknowledgment that includes the changelog of the copy it will read from next in the container of the deployment.