Any switch can be a vtp server but it is best practice generally to have your core switches serving this function.
What you want to avoid is someone plugging in a switch in vtp server mode with a higher configuration number which would then overwrite all your other vlans within your switch network (other than switches using vtp transparent).
Make you core switches vpt servers and set the other switches to be vtp clients. Or if you want very tight control make your switches vtp transparent.
If you are creating a VLANs on layer 2 switch, it will be layer 2 VLAN and you can assign IP address to only one VLAN in L2 switch which you can use for management purposes.
If you are creating a VLAN and associating IP with it which is generaly called as SVI (switched virtual interface), then it will be a Layer 3 VLAN and you can create it only in Layer 3 switch.
By default all switches operate in VTP server mode. Basically you can create, delete, modify VLAN in server mode and it will advertise it's VLAN information with all other switches in the same VTP domain configured in VTP server or client mode. There can be multiple VTP servers for redundancy.
Assuming they are in the same VTP domain, there is no difference. The VLAN being created will be propgated to all switches residing in the same VTP domain. Also assuming you want to make the VLAN routable, you will need to create an SVI (VLAN L3 interface) on the core switch, again assuming it is L3 capable.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...