Free Cisco 300-430 Actual Exam Questions - Question 11 Discussion
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?
Maybe C makes the most sense since normal ACLs don’t appear unless they’re created specifically as CPU ACLs. Just creating an ACL isn’t enough here.
Could it be that the ACLs exist but aren’t linked to the correct interface or context? If they aren’t tagged as CPU ACLs, they might not appear, so maybe both A and C have some merit depending on how the device handles ACL types.
Maybe A? If the ACL isn’t tied to the management interface, it might not show up where it’s needed for CPU ACLs. B seems too obvious—if there were no ACLs at all, the dropdown probably wouldn’t exist or be clickable. C might be true, but I think the main issue is the ACL’s scope or where it’s applied. D seems unlikely since most GUI functions work for this stuff.
Maybe B? If no ACLs show up in the dropdown, it's likely none were actually created under the Access Control List tab yet.
This question feels a bit unclear. I’m not sure if the problem is missing ACLs or a config step. I went with C because it makes sense the ACL must be marked for CPU use first. What did others pick?