The user at 192.168.150.10 can reach the physical router but CANNOT reach edge-2 or any virtual machines.
What routing change would resolve the issue?
A.
Enable Default Originate on edge-2 for OSPF.
B.
Configure static routes on the physical router.
C.
Enable route redistribution on edge-2 between both routing protocols.
D.
Enable Default Originate on edge-2 for BGP
I Guess Option B is correct.
0
2
Should be C
need redistribution to enable 2-way communication
1
2
I agree with Matz, should be B.
The user is unable to reach EDGE-2 which is on the same subnet as the phy router’s 192.168.100.1 interface. This is before BGP routing tables comes into play – hence a missing static route on the phy router is the likely cause.
0
1
Between Physical Router and ESG exist BGP protocol, so static routes are not needed.
Should be C.
2
1
What’s more, part of new 313Q VMWare 2V0-642 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpbVl3X1hXbUdteHc
Best Regards!
0
0
I think the correct answer is D.
1
0
Clue is “you can’t reach edge-2”. This means ping can reach the physical router, which has a directly connected route so it forwards the packet to edge-2, edge-2 knows a lot of things for BGP and OSPF, but if it cannot reply is because it doesn’t have the route to 192.168.150.x network. This means BGP is only enabled for that link, not the rest of the links on the physical router.
If you enable route redistribution, OSPF routes will be injected at the physical router, which is good, but that won’t change the fact that edge-2 doesn’t know how to reach the 192.168.150.x network. Creating a static route on the physical router won’t fix the issue because edge-2 is the one that doesn’t know how to get there, hence default originate on edge-2 seems to be the right answer.
3
0
D is the correct answer, because I love Dormamu.
1
4