Exam 2V0-41.20 All QuestionsBrowse all questions from this exam
Question 67

An NSX Administrator has created a segment named WEB-LS from the NSX UI and noticed the segment is not realized on the KVM Transport node.

What are two possible causes for this issue? (Choose two.)

    Correct Answer: B, E

    If the Compute Manager is disconnected in NSX UI, the WEB-LS segment will not be realized on the KVM Transport Node as the necessary management link is severed. Additionally, if the virtual machines running on the KVM Transport Node are not connected to the WEB-LS Segment, the segment will not be realized because there are no active dependencies requiring its creation and maintenance.

Discussion
NSXTOptions: CE

C & E should be the suitable answer

jabac21

C & E definitely * Hardare defects are always a possible cause, but there are better answer options. - disqualifies A * KVM hosts are standalone, not managed by Compute Manager - disqualifies B * VTEPs from ALL transport nodes are only participating in segments if needed, e.g. by running VMs. No active VMs means no segment is realized/implemented to run. - check C * KVM hosts do not use VDS, the use N-VDS (or OVS, specfically) - disqualifies D * Virtual machines on KVM hosts need to be attached MANUALLY to the segment, by grepping the interface uuid and assigning a segment port. Without this step, the new segment ist not realized as no VM needs it - check E

mtaaOptions: AB

C,E are not good because segment works for VMs communication but they are realized even if there are no VMs. D is not good since KVM host works only with N-VDS A seems right if NIC is damaged B seems right because if vcenter (compute manager) is disconnected, then Segment or other elements won't be realized in hosts.

dadoo3678

make sense this one

notyou

They are talking about KVM TNs.. they don't care if there is a Compute Manager or not, as they are standalone. NSX Manager is not dependent of vCenter being connected to send information to standalone hosts.

[Removed]Options: AB

CDE are wrong. You need to realize the Segment first before you even try to connect the VMs. THe problem here is that the segment is not being created in the KVM host. You cannot connect VMs to something that doesn't exist. Also KVM uses OVS no VDS

asorinOptions: CE

C/E are correct

WOP_TOOptions: AB

For me A & B

borracho13Options: CE

C & E are correct

Virtual_ITTechOptions: CE

if Segment is not realized on TN, then either there are no VMs using the segment or the VMsusing it are Down.

DUsooOptions: CE

C/E are correct