CAP is frequently misunderstood as if one has to choose to abandon one of the three guarantees at all times. In fact, the choice is really between consistency and availability only when a network partition or failure happens; at all other times, no trade-off has to be made.
So a better exercise would be understanding it from the following format.
In a cluster of X node, when Y nodes are failed/removed/disconnected/isolated from the cluster.
Does the system choose to ensure consistency (by crashing), or availability (by serving possibly incorrect data)
X and Y at times can be highly configurable in certain systems.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From the wiki itself.
So a better exercise would be understanding it from the following format.
In a cluster of X node, when Y nodes are failed/removed/disconnected/isolated from the cluster.
Does the system choose to ensure consistency (by crashing), or availability (by serving possibly incorrect data)
X and Y at times can be highly configurable in certain systems.