Yeah, I agree with that. It makes far more sense to keep those methods connected to the member list class in my opinion. The reason I stuck with the OperationsOnMembers class is because they specifically list it and I'm nervous of deviating too far from what they ask for since I'm deviating in other areas.
For example, the user selects the member they want to delete from a list instead of entering a member id at the moment. It made more sense from a user perspective.
Plus the whole part about validating passwords. I understand that they want us to use regex, but if there are clear defined restrictions on usernames and passwords then why allow the user to enter them at all anyway. So for that part I'm setting the values programatically, but still running them through a validator just so that I can tick that requirement off the list.