This is one of those nitpicky scenarios. If logging in as root fails and you can't enable SSH, it's almost always about the password itself, not just a disabled service. So A makes sense. Only exception would be if upgrade enforced a new policy blocking root, but question doesn't mention that. Pretty sure it's A. Disagree?
My vote is it's A since the root password is what actually controls SSH login, especially after upgrades. The vCenter console won't let you enable SSH if you can't authenticate as root anyway. Resetting that gets you back in-no need for rollback or remediation tools here. Could be missing something if there's a hidden policy step, but doubt it.
Why would you rollback (C) when you can just reset the root password and regain access? The question points out the root login issue, which usually means password got changed or reset during upgrade. Reboot or remediation tools wouldn't help if you can't authenticate in the first place. Does anyone think there's another scenario where C or D fits?