I don't think the question did, but that doesn't matter.
dhcpcd is fairly good at sniffing around if you invoke it with
, e.g. 'dhcpcd eth0'. It will find your dhcp server, and get you going.
It is only if that doesn't work that you need to start thinking. Subnets and vlans are separated networks over the same wire, typically to restrict access. dhcpcd can't guess those, so you have to treat it as stupid. These are typically in companies where groups like admin, R&D, and perhaps others want to have confidential traffic. But technical backup exists in companies also.
If you have a simple system, try it and record what goes wrong. If you have a complex system with subnets and/or vlans or several dhcp servers sharing the same wires, you may not be able to post externally the info required to get your query answered. We would need a fairly full description.