What should be enabled before any user views can be created during role-based CLI configuration?ORDuring role-based CLI configuration, what must be enabled before any user views can be created?

What should be enabled before any user views can be created during role-based CLI configuration?
OR
During role-based CLI configuration, what must be enabled before any user views can be created?

What should be enabled before any user views can be created during role-based CLI configuration?
OR
During role-based CLI configuration, what must be enabled before any user views can be created?

A.
usernames and passwords

B.
secret password for the root user

C.
aaa new-model command

D.
multiple privilege levels

Explanation:
Before role-based CLI views can be created, AAA must be enabled with the ” aaa
new-model” command. Step 2 is to enable the root view with the “enable view”
command. Step 3 creates the actual view with the “parser view view_name ” command,
and enters the View’s edit mode, evidenced by the ( config -view )# prompt. Creating a
password for the view with the “secret password ” command is Step 4. Finally, adding the
necessary commands to the view is the 5 th and final step, using the command syntax of
“commands exec include ping” and “commands exec include write”.
Interestingly, while you assign a local password in Step 4, role-based CLI configurations
are still an advanced scheme that requires enabling AAA.



Leave a Reply 0

Your email address will not be published. Required fields are marked *