Please discuss eventual consistency.
Interviewers will sometimes ask you about concepts related to the job for which you are interviewing but not exclusively. They expect you to answer in the context of the job and to limit your answer to this. If you respond to their question by defining the concept in a different context, it will raise a red flag and indicate that you may not be qualified for this position. This is one of the key reasons they ask this type of question.
When responding to an ambiguous question about a term that is not exclusive to the role of a web architect, be sure to limit your answer to how the concept or phrase is used in this job. The interviewer is only interested in your knowledge and experience related to the role for which you are interviewing. Expanding your answer to other uses of the concept will dilute your answer and prompt the interviewer to wonder if your understanding of the concept is not sufficient for this role.
"The concept of eventual consistency is an abstract assurance that all reads of an object within a website will eventually return the most recent value. An example of this is the Domain Name System (DNS) which directs users to the same website if they enter the same or closely similar request. Some of the variations to the eventual consistency model include causal consistency, read-your-writes consistency, session consistency, monotonic read consistency, and monotonic write consistency."
