Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

VMware Exam 1V0-21.20PSE Topic 8 Question 41 Discussion

Actual exam question for VMware's 1V0-21.20PSE exam
Question #: 41
Topic #: 8
[All 1V0-21.20PSE Questions]

A vSphere administrator has migrated a virtual machine between two ESXi hosts using vSphere vMotion and notices that the VM can no longer be pinged.

What caused this situation?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Valene at Apr 25, 2024, 05:01 AM

Limited Time Offer

25%

Off

Get Premium 1V0-21.20PSE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Venita
2 months ago
Definitely not A or B. Those options don't really make sense in the context of a simple vMotion migration. I'm going with C, the MTU mismatch, as the correct answer here.
upvoted 0 times
...
Adelle
2 months ago
Ha! I bet the admin forgot to update their DNS records after the migration. No wonder the VM can't be pinged - it's probably still pointing to the old IP address!
upvoted 0 times
...
Billi
2 months ago
D seems like the most likely culprit to me. If the destination portgroup has an incorrect VLAN tag, that would definitely prevent the VM from being able to communicate on the network.
upvoted 0 times
Isabella
8 days ago
It's important to double check the VLAN settings on the portgroup after a vMotion.
upvoted 0 times
...
Britt
13 days ago
I've seen VLAN tag mismatches cause network communication problems before.
upvoted 0 times
...
Shawnda
17 days ago
I think you're right, D could be the issue here.
upvoted 0 times
...
...
Carlton
2 months ago
I think the answer is C. An MTU mismatch can definitely cause connectivity issues after a vMotion migration. The virtual machine's network settings may not have been properly updated on the destination host.
upvoted 0 times
Justine
15 days ago
The administrator should check and ensure that the MTU settings are consistent on both hosts.
upvoted 0 times
...
Janey
17 days ago
So, what should the administrator do to fix the issue?
upvoted 0 times
...
Sheridan
18 days ago
Yes, that's correct. The virtual machine's network settings may not have been properly updated on the destination host.
upvoted 0 times
...
Edelmira
27 days ago
I think the answer is C. An MTU mismatch can definitely cause connectivity issues after a vMotion migration.
upvoted 0 times
...
...
Brandee
2 months ago
I believe the problem could also be related to the VLAN tag on the destination portgroup.
upvoted 0 times
...
Gwenn
3 months ago
I agree with Cecily, a different MTU setting could cause the VM to not be pingable.
upvoted 0 times
...
Cecily
3 months ago
I think the issue might be due to an MTU mismatch.
upvoted 0 times
...

Save Cancel