The existing configs in this sim don't appear to be existing on the R10 or R20 routers.

Should they already be there or do we have to configure this?

TIA

Terry

Hi,

So, QID:AR137 is confusing to me. At least the answer explanation compared to the question.

The question states the following: Which feature drops packets if the source address is not found in the snooping table?

• Binding table recovery
  
• IPv6 Destination Guard
  
• IPv6 Prefix Guard
  
• IPv6 Source Guard
  

• ipv6 address 
  
• mac address
  
• VLAN
  
• interface ID
  

Thanks, and my apologies for the long winded explanation. 

Verified that I answered question correctly and it scores it as wrong.

Please check the answers:
-R1 has destination 10.60.66.66 instead of 10.66.66.66
-Primary path is thought R4, however the access list should be modify on R4

Just passed the Exam Today! There are 6 Sims and 54 questions. One of the Sims asked to create a flow exporter and I failed that one as I got stuck with the syntax and the dash in between words that CLI was not accepting so after spending about 10 mins I decided to skip to next one...I still do not know what the issue was after getting home and searching.... I also got stuck on a VRF Sim that for some reason I could not ping from one router to the other using the tunnel...I was able to ping from one PC though.... Pretty much the others are very similar to the ones on how2. The questions I got around 70 percent similar to the ones here. Overall. it is quiet intense and covers lots of topics. I wanted to say Thank you to How2 for helping to prepare  for it. I think this will be my last time I try re-certify with Cisco as It is becoming more complex and irrelevant to what actually a Network Eng. daily work is...... Thanks for everything and good luck to the others!

Kind of tricky if you are not very familiar how this works...
 On task #2 it states that: 
The OSPF process ID on both R2 and R3 is 1.
All interfaces of R2 belong to 10.1.0.0/16 subnet.
All interfaces of R3 belong to 10.2.0.0/16 subnet

Not all interfaces on R2 are in 10.1.0.0/16....shouldn't it say "All Int of R2 in Area 10 belong to...

same goes for R3..?

thanks

I think this question's answers may be wrong, although not 100%.

I think the wording of the question isn't ideal as it's asking how traffic is treated however the implication is that the focus is on the ACL "NON-CISCO"


[*]"Packets are forwarded using normal route lookup."
Correct 
A deny In a route-map for PBR causes the matched traffic to bypass policy routing and be routed using the normal routing table (RIB/FIB) NOT DROPPED.

[*]"Packets are not evaluated by sequence 10."
Correct 
Once a route-map sequence matches (even a deny), no further sequences are evaluated. The logic stops at the first match.


The current correct answers:

"Packets are forwarded to the default gateway." 
There's literally no mention or evidence of a default gateway, and if we are referring to the traffic classified in ACL "NON-CISCO" this is definitely not the case as it already matches on seq 5.

"Packets are evaluated by sequence 10."
Again, are we referring the the ACL classified traffic? If we are then again definitely not, as it's already matched on seq 5.

Thanks

Hi forum support / admin

According to QID:AR143 explanation end paragraph:

"Manually configuring an ipv6 address on router 2 will it an address on the same subnet as router  1. This will allow router 2 to successfully telnet." Yet the answer correct answer is "permit ip any any on access-lit egress." I would add pictures if i could. Nonetheless, please fix.

Thanks,
GreaterZen

The answer has the interfaces grouped into po11, and configured as trunk interfaces

no interface po11
interface range e0/0 - 2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode active

However, don't we have to specifically configure int po11 as a trunk as well?

EX
Interface po11
switchport trunk encapsulation dot1q
switchport mode trunk
Switchport trunk allowed vlans x,x,x

?????

Hello,

I've experienced a problem with the sim-VRF. On R2 after enabling ip cef and placing the vrf (cu-red / cu-green) on the appreciate interfaces with the ip addresses nothing shows up in the respected routing tables. To my knowledge all that is needed for vrf to work:

1. enable ip cef
   
2. create the vrf with either ip vrf <vrf name> or vrf definition <vrf name>
   
3.  add the vrf to an interface