A VMkernel port is labelled PROD01 and uses the default TCP/IP stack. Currently, this VMkernel port is configured for supporting live virtual machine (VM) migrations.
Which configuration change should the administrator make to isolate live VM migration traffic from other network traffic?
To isolate live VM migration traffic from other network traffic, you should create a new VMkernel port using the vSphere vMotion TCP/IP stack specifically designed for this purpose. Creating a new VMkernel port with a dedicated TCP/IP stack ensures that the live VM migration traffic does not interfere with other network traffic. The default TCP/IP stack is not suitable for isolating such specialized traffic.
Answer A
Answer is correct.
Tested this and the answer is A. You cannot change a vmkernel's TCP stack after creation.
I answered A on the test, passed with 428.
You cannot change a vmkernel's TCP stack after creation.
Correct answer should be A. B +C are about the provisioning stack, not related to this question. D is not possible, once you set a TCP/IP stack for the VMkernel adapter, you cannot change it later https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-AA3656B0-005A-40A0-A293-4309C5ACF682.html
You are wrong, I can edit the TCP/IP stack and select vMotion!!
Selected Answer: A https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-5211FD4B-256B-4D9F-B5A2-F697A814BF64.html Use the vMotion TCP/IP stack to isolate traffic for vMotion and to assign a dedicated default gateway, routing table, and DNS configuration for this traffic. To enable the vMotion TCP/IP stack, assign a new VMkernel adapter to it.
seems so
Select a TCP/IP stack from the list. Once you set a TCP/IP stack for the VMkernel adapter, you cannot change it later. If you select the vMotion or the Provisioning TCP/IP stack, you will be able to use only these stacks to handle vMotion or Provisioning traffic on the host. All VMkernel adapters for vMotion on the default TCP/IP stack are disabled for future vMotion sessions. If you set the Provisioning TCP/IP stack, VMkernel adapters on the default TCP/IP stack are disabled for operations that include Provisioning traffic, such as virtual machine cold migration, cloning, and snapshot migration.
Answer should be A: Once you set a TCP/IP stack for the VMkernel adapter, you cannot change it later. https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-AA3656B0-005A-40A0-A293-4309C5ACF682.html
Once you set a TCP/IP stack for the VMkernel adapter, you cannot change it later.
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-AA3656B0-005A-40A0-A293-4309C5ACF682.html#:~:text=Once%20you%20set%20a%20TCP/IP%20stack%20for%20the%20VMkernel%20adapter%2C%20you%20cannot%20change%20it%20later
Selected Answer: A It is not possible to edit TCP/IP stack after creation. remove the rest of my previous answers.
Selected Answer: A Provisioning carries the data transferred for VM cold migration, snapshot migration and cloning, not live migration!
Selected Answer: D I was wrong, why remove? I can edit and do what A says.
remove this answer plz!!! D is incorrect
The question states that you are using the Default TCP/IP stack and this by default is dedicated for host management. Therefore the answer should be A since you will need to create new vmkernel for vMotion. Default TCP/IP Stack. Manage the host-related traffic services. This stack shares a single default gateway between all configured network services. Ref: https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-network-design-guide/GUID-51E2022C-6F78-4CE0-B4C7-6ED1E90F2D95.html
Selected Answer: A
A is the correct answer, notice the key words "isolate"
Ans: D You can change the TCP/IP Stack https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-D4AF4F9F-F274-4ADE-98F4-1CB44ABCC505.html
That's not what it is asking. The answer is A. You cannot change the TCP/IP stack of a vmkernel port after it is created. You must delete and recreate the vmkernel.