How to build the ViewModel in MVVM not to violate the Single Responsibility Principle?

Question

Robert Martin says: \"There should never be more than one reason for a class to change\".

Let\'s consider the ViewModel class which is bound to a View. It is

Answer 1

Yes, but that doesn't mean poor design couldn't force you into it.