That same error still exists as the diagram shows G0/1 as the outgoing interface for the default route. No G0/0 interface exists.
There is also question about Etherchannel where both ends were marked as ACTIVE for LACP. According to the lesson, this link would come up fine and in my company network this setup also works successfully. However the answer from the test says it would not function since both ends are trying to actively create the EC and their efforts would be cancelled out. Please could you check this question?
Another question relates to OSPFv3 with IPv6 ACL. The actual correct answer uses the link local IP address - but this was marked as incorrect. The answer marked by the system as correct says OSPFv2 is being used to route packets to the 2001::2/128 network - this would not be possible as we are using IPv6 and even the explanation of the answer confirms only OSPFv3 info is shown.
One question asked about MPLS and enabling it on non customer facing interfaces. The mpls ip command is shown in interface mode and the question asks if additional config is required for ‘an MPLS network to function’. The question seems to be ambiguous as technically the interfaces would also require an IP address too (which isn’t shown in the interface output). The answer feedback also says no IP addresses are required. On it’s own, the mpls ip command only ‘activates MPLS on the interface’ but surely will not make an ‘MPLS network function’ without routing and IP addresses? How would it route the packets with just mpls ip command applied please?
Another question about SDN says the correct answer is that the switches are responsible for feeding the control plane of the SDN controller with info. However this doesn’t correlate with the answer explanation which mentions that the SDN controller is solely responsible for all the control plane and will feed the switch with info.
There was also a question about applying a standard ACL on R2 to either the Fa0/0 interface or the loopback interface to permit traffic to reach the loopback. I chose the Fa0/0 inbound on R2 but this was deemed wrong; the loopback was reported to be the correct place to apply the ACL. However from my understanding and I also checked this on a few routers - the only ACL type option on a loopback is the ‘access-expression’ command. Is this correct?
Please could you confirm and rectify where possible?