Exam 300-415 topic 1 question 216 discussion

Some tricks here - vbond default route nexthop .254 is not in 11.1.1.0/28, but all Controllers can reachable with connected switching. - hostname on vBond is incorrect but no impact - vBond 11.1.1.1 local ->> it will cause WAN Edge device could not found vBond, but for controllers, no need this commands to establish, (Designate the local vEdge router to be a vBond orchestrator in the vEdge overlay network domain.) - Duplicate system-ip vSmart and vManage. -> it cause connections could not be establishedd

system IP cannot be the same.

wrong: system IP = 10.11.11.1 on both vManage en vSmart ! So 11.1.1.x not a system IP.

Shouldn't it be 10.11.11.2 ? There is vM as 10.11.11.1, vB as 10.11.11.3

stoopid question - possable typo in answer d Reconfigure the system-ip parameter on vSmart to 11.1.1.2. should maybe be 10.11.11.2

D is correct answer

Multiple mistakes in this one. vBond has interface IP 11.1.1.3/28 with a route configured pointing towards 11.1.1.254. That's not even in the 11.1.1.0/28 subnet...

This question is horribly written with no good answer whatsoever. None of the answers fix the obvious problem of vbond having the wrong IP in the 'vbond x.x.x.x local' statement.

vSmart IP is incorrect. vBond ip 11.1.1.1 local should be vBond local

Couple errors in here. Not sure if question pasted correctly. vManage and vSmart have same system IP addresses. vBond address not correct.

A correct