READ Free Dumps For Cisco- 300-135
| Question ID 15431 | Scenario:
The OSPF neighbour relationship has been lost between R1 and R3. What is causing this |
| Option A | The serial interface in R1 should be taken out of the shutdown state. |
| Option B | A neighbor statement needs to be configured in R1 and R3 pointing at each other. |
| Option C | The R1 network type should be changed to point-to-multipoint non-broadcast. |
| Option D | The hello, dead and wait timers on R1 need to be reconfigured to match the values on R3. |
| Option F | Answer : C Explanation: In order for two OSPF routers to become neighbors, they must have matching network types across the links. In this case, we see that R1 has been configured as non-broadcast and R3 is using point to point non-broadcast.
|
| Correct Answer | F |
| Question ID 15432 | Scenario:
The 6.6.0.0 subnets are not reachable from R4. how should the problem be resolved? |
| Option A | Edit access-list 46 in R6 to permit all the 6.6.0.0 subnets |
| Option B | Apply access-list 46 in R6 to a different interface |
| Option C | Apply access-list 1 as a distribute-list out under router ospf 100 in R4 |
| Option D | Remove distribute-list 64 out on R6 |
| Option E | Remove distribute-list 1 in ethernet 0/1 in R4 |
| Option F | Answer : D Explanation: Here we see from the running configuration of R6 that distribute list 64 is being used in the outbound direction to all OSPF neighbors.
[8] However, no packets will match the 6.6.0.0 in this access list because the first line blocks all 6.0.0.0 networks, and since the 6.6.0.0 networks will also match the first line of this ACL, these OSPF networks will not be advertised because they are first denied in the first line of the ACL. |
| Correct Answer | F |
