2V0-620 · Question #68
An administrator is unable to login to vCenter Server when using the vSphere web client. The administrator successfully accessed vCenter Server using the client earlier the same day. What is the…
The correct answer is B. Verify the vCenter Single Sign-On service is running on the vCenter Server. When vCenter Server login suddenly fails, the SSO service is the first component to verify because all vSphere Web Client authentication is routed through it.
Question
An administrator is unable to login to vCenter Server when using the vSphere web client. The administrator successfully accessed vCenter Server using the client earlier the same day. What is the most appropriate first step the administrator should take to resolve this issue?
Options
- AVerify the web browser being used has Adobe Flash plugin version 11.5 or later
- BVerify the vCenter Single Sign-On service is running on the vCenter Server
- CVerify the vSphere Web Server service is running on the vCenter Server
- DVerify the administrator has permissions configured in vCenter Server
How the community answered
(36 responses)- A11% (4)
- B83% (30)
- C3% (1)
- D3% (1)
Why each option
When vCenter Server login suddenly fails, the SSO service is the first component to verify because all vSphere Web Client authentication is routed through it.
The administrator logged in successfully earlier the same day, proving the Flash plugin version was already sufficient and has not changed, so it is not a likely cause of a sudden authentication failure.
Every vSphere Web Client login attempt is authenticated by the vCenter Single Sign-On service; if SSO is stopped or faulted, no user can authenticate regardless of permissions or browser state, making it the highest-priority first check for a sudden login failure.
The web client server may still be serving the login page normally while only the SSO authentication backend has failed; verifying SSO is a more targeted first step than checking the web server process.
Because the administrator authenticated successfully to vCenter Server earlier the same day, their permissions have not changed and are not the most probable root cause of the new login failure.
Concept tested: vCenter Single Sign-On service authentication troubleshooting
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.authentication.doc/GUID-3B2C5B5A-CF15-4A5E-A13B-8C79B55E5F9C.html
Topics
Community Discussion
No community discussion yet for this question.