Here is an example of a question with no explanation. Most questions are like this:
QID:AN587
Here is an example of an incorrect answer. There are a shocking number of these:
QID:AN404
(12-14-2023, 01:43 AM)rexhanemann Wrote: [ -> ]Here is an example of a question with no explanation. Most questions are like this:
QID:AN587
Here is an example of an incorrect answer. There are a shocking number of these:
QID:AN404
QID:AN123 is incorrect as well
If you find a definite incorrect answer and can provide a reason or reference to support your answer, we will correct our answer. Explanation is not always provided. It is added to some questions where necessary.
If you are doubtful about an answer and cannot provide reason/reference, please use our forum for open discussion with other users.
(12-14-2023, 06:01 PM)forumsupport Wrote: [ -> ]If you find a definite incorrect answer and can provide a reason or reference to support your answer, we will correct our answer. Explanation is not always provided. It is added to some questions where necessary.
If you are doubtful about an answer and cannot provide reason/reference, please use our forum for open discussion with other users.
I'll point out what questions are wrong. I'm not doing your work for you, however. You are supposed to understand these topics.
QID:AN470 is not only incorrect, there is no correct answer to choose.
QID:AN126 is incorrect. A hypervisors job is not solely to monitor SNMP traffic.
We have corrected answers for both indicated questions and added explanations as well.
Please feel free to indicate any other questions you find incorrect.
QID:AN624 has the answers from a different question listed under it.
QID:AN438 is missing the configuration
Thank you for your feedback. Both AN624 and AN438 have been corrected.
All previously indicated incorrect questions, including AN123, AN404 etc., have also been corrected and explained.
Thank you for correcting these question.
AN082 has a typo. The IP addresses in the answers don't correspond to VLAN 20 in the exhibit.
This is not a typo. You were caught by the trap set in this question. Examine the given ACL carefully:
deny tcp any host 10.30.0.100 eq 80
The IP address 10.30.0.100, in above deny statement is not a source address, rather it is the destination address (and belongs to the web server). So when this ACL is applied to interface VLAN 20 in the "in" direction, it blocks HTTP traffic (on port 80) originating from "any" host on VLAN 20, destined for the web server.
(12-22-2023, 05:47 PM)forumsupport Wrote: [ -> ]This is not a typo. You were caught by the trap set in this question. Examine the given ACL carefully:
deny tcp any host 10.30.0.100 eq 80
The IP address 10.30.0.100, in above deny statement is not a source address, rather it is the destination address (and belongs to the web server). So when this ACL is applied to interface VLAN 20 in the "in" direction, it blocks HTTP traffic (on port 80) originating from "any" host on VLAN 20, destined for the web server.
Correct, that was an oversight on my end.