Refer to the exhibit.
How do improperly set Telnet/SSH parameters effect the configuration of a controller with Cisco WCS?
A.
The CLI and GUI management of the controller both fail because Cisco WCS checks these credentials before opening a session.
B.
The Telnet/SSH username must have sufficient privileges to execute commands in CLI templates.
C.
The GUI management of the controller fails because the Cisco WCS uses the Telnet/SSH parameters to login to the controller.
D.
The controller remains configured in the Cisco WCS, but no management is possible through GUI from other client browsers.
Explanation:
Ummmm… someone show me where a “CLI Template” is in WCS? Never have seen one. I don’t think any of these is correct in the context of the illustration. Another expertly crafted question from clueless test writers.
0
0
The Telnet/SSH username must have sufficient privileges to execute commands in CLI templates.
https://supportforums.cisco.com/docs/DOC-30514
0
0
See page 54 Volume 3 official course material IUWNE
0
0