An MVD, just like an FD, is a rule. It applies to your business case or not, you'll need to inspect the requirements and/or the specs in order to know.
You cannot know whether it applies from looking at sample data (that applies to FD's as well).
Looking at sample data can only tell you, "if the rule applies, then this data will be valid/invalid", or "if this data must be valid, then some particular MVD rule certainly won't apply".
Now what does such an MVD rule state exactly ?
First take a look at what an FD states exactly. An FD states that for a certain [set of] attribute[s] (the Left side of the FD), it cannot be the case that some particular [combination of] value[s] is associated with more than one [combination of] distinct value[s] of the attributes on the Right hand side of the FD.
A->B indeed means that for all attribute value pairs (a1,b1) and (a2,b2), it holds that a1=a2 ===> b1=b2.
An MVD is a generalization of an FD, in that it does not state that individual B values must be associated with/determined by A values, but instead it states that SETS of B values must be associated with/determined by A values.
(warning : switching from A/B to B/C here !)
In your example, b2 is "associated" with the set {c1}, and the value b1 is "associated" with the set {c2,c3}. Now if the MVD B->>C applies indeed, then it should be impossible for a row a4,b1,c2 to appear in your table unless the row a4,b1,c3 also appears, simultaneously. Likewise, if you have those two additional rows, and you add a1,b1,c4, this will "add" c4 to the set of values that are "multidetermined by" the value b1, and consequently, your MVD will be violated unless you also add a4,b1,c4.