The question is " Which statement correctly describes what is allowed for traffic entering interface 1/1/3?"
I think that what is allowed to enter the interface 1/1/3 is
everything from:
ANY TO -> 10.X.11.X(this is allowed and counted) or 10.X.12.X(this allowed and loged), thats why i think the answer is B
Everything with other "destination" should be denny.
People seem to be confused by inverted mask/wildcard masks. They would be correct for Cisco switches, but AOS-CX does NOT use wildcard masks; "AOX-CX switches do not support wildcard masks - only prefixes or subnet masks - when created ACEs."
Cisco: 255.0.255.0 = xx.123.xx.123
AOS-CX: 255.0.255.0 = 123.xx.123.xx
My answer is B.
I think the answer is D.
Here is the simplified access list with X=any (0-255)
permit any -> X.0.X.0 count
permit any -> X.0.X.0 log
They are practically the same ACL with only different the top does count and bottom does log.
A. IP traffic from 10.1.11.0/24 is allowed to access 10.1.110.0/24
We dont care with source (10.1.11.0/24). The source can be any.
But the destination is 10.1.110.0/24 and it does not match. The second octet must be 0.
B. IP traffic from 10.0.11.0/24 is allowed to access 10.1.12.0/24
Same with A. 10.1.12.0 does not match because second octet is 1
C. Traffic from 10.0.12.0/24 will generate a log record when accessing 10.0.11.0/24
This actually match both ACEs but since ACL matches from top to bottom, so it will match the top ACE (count).
D. IP traffic from 10.1.12.0/24 is allowed to access 172.0.1.0/23
this would match the ACL. We dont care about source and destination 172.0.1.0 (match X.0.X.0)
Samw
My opinion: B
Only traffic destined TO the listed subs is allowed
This excluded A and D
Only traffic TO 10.1.12.0 is logged
This excludes C
This leaves B
.11.0 is part of ANY so it is allowed to access .12.0
This traffic will be logged but that isn't part of the answer.
I think it's C. ACL entries work with wildcard mask. The wildcard mask is 255.0.255.0. This is a wildcard mask and not a subnet mask also because it is not a valid subnet mask.
In a wildcard mask made in this way you have to match bits where wildcard is 0.
So, it matches packets where the DESTINATION IP ADDRESS is X.0.X.0. In a /24 network, you will never have a destination IP where the last octet is 0. So i think this ACL is not valid, by the way, the only answer that matches the ACL entries is the C BUT it matches the first entry, so it will never generate a log, but a counter increment. This is a bad question with no matching answers. The "best matching" answer is C even if it is wrong.
Got it backwards. 10.0.12.0/255.0.255.0 will match 10.1.12.0/24 .Therefore B should be correct. Right from the student guide. 1's match 0's ignore. Ch. 5 - Task 2 , or search book for 255.0.255.0 "In this example any destination IP address that has '10' in the first byte, and '12' in the third byte will match the rule.
It's possible that B is correct but look at the log and count entries in the commands. I think C is correct. A log entry will be generated for this subnet.
AOS-CX does not support Wildcard / Inverted Subnet Masks...
Study Guide states: "AOS-CX switches do not support wildcard masks - only prefixes or subnet masks - when creating ACEs". Therefore C is most probably the answer
This section is not available anymore. Please use the main Exam Page.HPE6-A73 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.
cloud29
Highly Voted 4 years agoBFDS
Most Recent 7 months agoSeidorBruno
1 year, 9 months agoalex711
2 years, 1 month agoBahadorkh
2 years, 5 months agoJo2241
2 years, 6 months agoNetExpert
2 years, 6 months agoJo2241
2 years, 8 months agoroot2022
2 years, 10 months agogondolf
3 years agojagoanneon
3 years, 2 months agopabx31
3 years, 6 months agoclupato2
3 years, 8 months agoOICU812
3 years, 7 months agowatermellonhead
3 years, 7 months agomaccchinguwo
3 years, 9 months agoWilliams926
3 years, 10 months agoEl3den
3 years, 10 months agoEl3den
3 years, 10 months agoSimba80
4 years agofasty
4 years agofasty
4 years agoLoneRaccoon
1 year, 6 months ago