Example of query execution plan where the cardinality estimation makes a difference
At 180 rows, you're not likely to see any difference whatsoever. 

In order to see different plans get chosen at different predicate distributions, you'd need quite  bit more data, and likely competing data sources (indexes) to aid them.

Let's say you had 1.8mm rows in the table. If you've got 


A clustered index on a column unrelated to price or country (Like Id or something)
A nonclustered index on price and country
A single column nonclustered index on country


You may start to see a difference in the method of aggregation, serial vs. parallel plans chosen, and index choice, depending on which country you search for and its selectivity.

For an example of a recent Q&amp;A:


Large variances between two similar queries when doing WHERE EXISTS on related table


For a more complex reasons:


Why is my query suddenly slower than it was yesterday?