Refer to the exhibit. An engineer must restrict some subnets to have access to the WLC. When the CPU ACL function is enabled, no ACLs in the drop-down list are seen. What is the cause of the problem?
A.
The ACL does not have a rule that is specified to the Management interface.
B.
No ACLs have been created under the Access Control List tab.
C.
When the ACL is created, it must be specified that it is a CPU ACL.
D.
This configuration must be performed through the CLI and not though the web GUI.
B is correct. Tested on AireOS. If you dont have any ACLs created, then none will appear when enabling CPU ACL. Dont involve management interfaces and access to the WLC itself.
When the CPU ACL function is enabled on the WLC, only the ACLs that have a rule specified for the Management interface will appear in the drop-down list. The Management interface is used for WLC management traffic, and if an ACL is not associated with it, it will not be available to be used as a CPU ACL. Therefore, the engineer needs to ensure that the ACL has a rule specified for the Management interface in order to be able to select it as a CPU ACL.
This section is not available anymore. Please use the main Exam Page.300-430 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
largestyle
7 months, 3 weeks agoraphim
8 months agoZanjit500
1 year agoTJR72
1 year, 1 month agorph02533
1 year, 6 months ago